>>> On 09.07.13 at 02:26, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote: > Could you explain to me please why the check in the scripts is superfluous? This is not really the question - _any_ such check can only be wrong. The boot loader has absolutely no business caring about kernel internals, and the kernel shouldn't be limited by it in how it renames/adds/deletes Kconfig options and anything else. > Especially as the grand plan is to get rid of CONFIG_XEN_DOM0 and more or > less have a backend and fronted config option (since that makes more sense > nowadays). And that would make the XEN_DOM0 be obsolete and the XEN_PRIV > would be the one that turns a lot of the options needed to compile a kernel > that can provide backend driver support. (I am hand waving here). That's pretty odd a plan, considering that Dom0 is more than just an environment to provide backends. In fact, Dom0 may not be providing any backends at all, and instead just serve the "controlling hardware" and/or "control domain" purpose that it really is meant to be. But of course, if none of _that_ functionality depends on this config option, then it indeed could go away. Jan _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
