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

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 06.01.16 at 11:31, <ian.campbell@xxxxxxxxxx> wrote:
> On Wed, 2016-01-06 at 02:22 -0700, Jan Beulich wrote:
>> > > > On 05.01.16 at 17:53, <cardoe@xxxxxxxxxx> wrote:
>> > On 12/22/15 10:09 AM, Jan Beulich wrote:
>> > > > > > On 22.12.15 at 17:02, <cardoe@xxxxxxxxxx> wrote:
>> > > > How does it not make sense in this case? That's what Andrew and I
>> > > > are
>> > > > asking you to explain.
>> > > 
>> > > But I already explained it: The file isn't needed for booting.
>> > 
>> > One use of it in /boot would be to check the file in 20_linux_xen like
>> > we check the kernel config for different options to add different
>> > parameters.
>> 
>> Which, if you search for it, is a very controversial thing: I agree
>> with the side demanding for grub to not inspect the kernel's
>> .config.
> 
> 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.)

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel