RE: [Xen-merge] CONFIG_XEN vs. CONFIG_X86{,_64}_XEN

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

CONFIG_XEN should be used whenever the change applies
to Xen for all architectures.  CONFIG_X86_XEN should be used
in generic code when a change applies only to x86.
(There was a recent example of this... I can dig it up
if you wish.)  If the code is clearly x86-specific
(e.g. in arch/i386 or include/asm-x86), I agree the
_X86_ part is superfluous.

> -----Original Message-----
> From: xen-merge-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-merge-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Jan Beulich
> Sent: Wednesday, December 21, 2005 9:15 AM
> To: xen-merge@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-merge] CONFIG_XEN vs. CONFIG_X86{,_64}_XEN
> 
> What was the reason to split these? Why can't we just have a 
> consistent
> CONFIG_XEN (provided in arch/*/Kconfig), and derive all
> architecture-specific information from other CONFIG_* values? Main
> reason for the question is the (apparently) inconsistent use of one or
> the other in various places.
> 
> Thanks, Jan
> 
> _______________________________________________
> Xen-merge mailing list
> Xen-merge@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-merge
> 

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