RE: [Xen-ia64-devel] config files and dom0/domU

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

That's a temporary hack. We need a similar file as 
linux-2.6-xen-sparse/arch/xen/Kconfig.drivers to list which driver Kconfig 
required to be included upon XEN_PHYSDEV_ACCESS. When a specific Kconfig is 
included, the default option is used when make oldconfig as long as you didn't 
specify 'k' or 'm' for that item.

Thanks,
Kevin

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Alex 
>Williamson
>Sent: 2005年11月16日 3:43
>To: Magenheimer, Dan (HP Labs Fort Collins)
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-ia64-devel] config files and dom0/domU
>
>On Tue, 2005-11-15 at 10:11 -0800, Magenheimer, Dan (HP Labs Fort
>Collins) wrote:
>> I just spent an hour playing with arch/ia64/Kconfig,
>> drivers/char/Kconfig and .config and I have not found
>> a way to enable CONFIG_VT if dom0 is being compiled
>> and disable CONFIG_VT if domU is being compiled.
>>
>> Just removing CONFIG_VT (or setting it =n) does not work
>> and various tries of adding other configs (e.g.
>> CONFIG_XEN_DOMAIN0, CONFIG_XEN_DOMAINU) with dependencies
>> does not work either... make oldconfig always seems
>> to revert back to a different state than I want.
>>
>> Clearly I do not understand the Kconfig syntax well enough.
>> Does anybody else on this list understand it?
>
>   I won't claim to be an expert either, but does something like this
>work?
>
>--- a/linux-2.6-xen-sparse/arch/ia64/Kconfig    Thu Nov 10 21:24:29 2005
>+++ b/linux-2.6-xen-sparse/arch/ia64/Kconfig    Tue Nov 15 12:39:56 2005
>@@ -79,6 +79,11 @@
>        depends on XEN
>        bool
>        default y
>+
>+config VT
>+       bool
>+       default y if XEN && XEN_PRIVILEGED_GUEST
>+       default n if XEN && !XEN_PRIVILEGED_GUEST
>
> config SCHED_NO_NO_OMIT_FRAME_POINTER
>        bool
>
>I don't know if XEN_PRIVILEGED_GUEST is what you want to use for the
>test, but I think something along those lines will work.  Thanks,
>
>       Alex
>
>--
>Alex Williamson                             HP Linux & Open Source Lab
>
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel