|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
RE: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen
 
> > So I'd vote for:
> > 
> > xen arch code in            arch/$(ARCH)/xen/
> 
> that's effectively sub-arch
The difference is admittedly very subtle (though probably
not to some Linux kernel developer purists).  The question
is whether xen is subsidiary architecture (which uses
the mach- prefix) or whether it is functionality that can
be turned on or off (no mach- prefix).
And since this will appear hard-coded in include lines
in source files, we do need to decide one way or the
other.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 |   
 
| <Prev in Thread] | 
Current Thread | 
[Next in Thread>
 |  
- Re: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen, (continued)
 
 
RE: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen, Magenheimer, Dan (HP Labs Fort Collins)
RE: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen, Magenheimer, Dan (HP Labs Fort Collins)
RE: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen,
Magenheimer, Dan (HP Labs Fort Collins) <=
RE: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen, Magenheimer, Dan (HP Labs Fort Collins)
RE: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen, Magenheimer, Dan (HP Labs Fort Collins)
 |  
  
 | 
    | 
  
  
    |   | 
    |