On Thu, 2013-07-11 at 10:57 -0700, H. Peter Anvin wrote: > On 07/11/2013 03:08 AM, Paul Bolle wrote: > > But the Kconfig entry for XEN_PRIVILEGED_GUEST reads: > > # Dummy symbol since people have come to rely on the PRIVILEGED_GUEST > > # name in tools. > > config XEN_PRIVILEGED_GUEST > > def_bool XEN_DOM0 > > > > In other words: CONFIG_XEN_PRIVILEGED_GUEST should always be equal to > > CONFIG_XEN_DOM0. So the two grep commands should always both evaluate to > > true or both evaluate to false. One of these two commands can safely be > > dropped. > > Not necessarily true across kernel versions.
Correct. But it has actually been true ever since this Kconfig entry was introduced in v2.6.37 (commit 6b0661a5e6fbfb159b78a39c0476905aa9b575fe, "xen: introduce XEN_DOM0 as a silent option"). So people need not worry about breaking grub2 by dropping XEN_PRIVILEGED_GUEST. Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
