[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1382658288.20130710003458@eikelenboom.it>
Date: Wed, 10 Jul 2013 00:34:58 +0200
From: Sander Eikelenboom <linux@...elenboom.it>
To: Borislav Petkov <bp@...en8.de>
CC: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>, jeremy@...p.org,
<xen-devel@...ts.xensource.com>, Jan Beulich <JBeulich@...e.com>,
Michael Opdenacker <michael.opdenacker@...e-electrons.com>,
<x86@...nel.org>, Paul Bolle <pebolle@...cali.nl>,
<virtualization@...ts.linux-foundation.org>, <mingo@...hat.com>,
Matt Wilson <msw@...zon.com>, "H. Peter Anvin" <hpa@...or.com>,
<tglx@...utronix.de>, <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen: remove unused Kconfig parameter
Tuesday, July 9, 2013, 5:05:54 PM, you wrote:
> On Tue, Jul 09, 2013 at 10:48:40AM -0400, Konrad Rzeszutek Wilk wrote:
>> Then that should be discussed on grub2 to remove said check and modify
>> the code so that it can properly work without regression.
> Actually, the kernel patch removing that symbol should be applied so
> that grub2 breaks faster. One can't possibly rely on kernel internals
> for anything, as it is insanely insane (yep, the tautology is on purpose
> :-)).
How insanely insane is it to be able to determine whether a certain compiled kernel binary supports a certain function ?
Grub does this in it's update script to prevent adding a xen + kernel combination that has no chance of booting when dom0 support has not been configured in the kernel.
That doesn't seem to be a unreasonable thought.
Grepping the accompanied config file in /boot for the xen dom0 Kconfig parameter seems the best possible effort grub can do at the moment.
Especially since the Kconfig parameter naming doesn't change that often.
If you know a better way for grub to determine if a certain function for a kernel binary is supported then please elaborate ..
--
Sander
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists