RE: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen

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

> Will include/xen/ work for you?

OK with me, but will that be as hard to get by the Linux community
as linux/xen for the generic C code?  If so, maybe
include/asm-generic/xen/file.h?

> That's part of sub-arch (this just needs to get include order right).

So for example include/asm-ia64/xen/file.h?

Also, what about arch-specific C code?  Hopefully this
will be minimized in drivers (by handling arch-specific
features with macros) but for most of the other xen-specific
files (e.g. setup.c) there will almost certainly need to
be arch-specific subdirectories...

So drivers/xen/arch/ia64/file.c or
drivers/xen/ia64/file.c or ??

Thanks,
Dan

> -----Original Message-----
> From: Chris Wright [mailto:chrisw@xxxxxxxx] 
> Sent: Tuesday, May 17, 2005 11:58 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: Chris Wright; Mark Williamson; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen
> 
> * Magenheimer, Dan (HP Labs Fort Collins) 
> (dan.magenheimer@xxxxxx) wrote:
> > Where are xen-generic header files going to go?
> 
> Will include/xen/ work for you?
> 
> > Where are arch-specific header files going to go?
> 
> That's part of sub-arch (this just needs to get include order right).
> 
> > Ar you going to try to get the structure right for
> > multiple arch's rather than just invert the structure?
> 
> The structure should be similar for multiple arch's, but it won't
> fallout from doing one arch.  Already I was doing i386 separate from
> x86_64.  
> 
> thanks,
> -chris
> 

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