[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] build: save generated config in /boot

>>> On 06.01.16 at 12:58, <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> Jan Beulich writes ("Re: [Xen-devel] [PATCH] build: save generated config in 
> /boot"):
>> On 06.01.16 at 11:31, <ian.campbell@xxxxxxxxxx> wrote:
>> > What is the preferred mechanism for determining from the contents of /boot
>> > whether an XSM entry should be produced or not?
>> I don't think this can be inferred - iirc even an XSM-enabled build
>> can be booted without unless in some kind of strict mode? IOW
>> this needs to be configured on the host, not guessed by
>> inspecting .config. (And as a side note, inspecting .config doesn't
>> truly require .config to be on the boot partition, unless such
>> inspection would happen at boot time, which I don't think is the
>> case.)
> Well, actually, it _can_ be inferred.  Therefore it should be.

You mean from the presence of the policy file (which ends up
being a container of garbage for a non-XSM-Xen)? If not -
what else do you think the need for an XSM entry can be
derived from?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.