This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] Pre-OLS attempt for (xen)linux directory structure conve

To: "Chris Wright" <chrisw@xxxxxxxx>
Subject: RE: [Xen-devel] Pre-OLS attempt for (xen)linux directory structure convergence
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Mon, 4 Jul 2005 19:20:31 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 05 Jul 2005 02:19:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWBBqR+PkTLXPOQSpeTEg6DrXQkeQAAGmhA
Thread-topic: [Xen-devel] Pre-OLS attempt for (xen)linux directory structure convergence
> > linux/include/xen/ - contains all xen includes that
> >     are common (not archdep)
> > linux/include/asm-*/xen/ - contains all xen includes
> >     required for a specific architecture[1]
> except s/xen/mach-xen/
> > linux/arch/*/xen/ - contains xen code that is archdep
> and s/xen/mach-xen/

Doesn't mach-xen imply (to a Linux kernel developer) that
xen is disjoint with and cannot co-exist with the other
mach-*?  Whereas leaving off the mach- implies that xen
more of a configurable option that may apply to multiple
mach- types?  (Or perhaps I am just thinking of "machvec"
on ia64?)

I guess I don't care whether there is a mach- prefix or
not but want to ensure Linux conventions are kept where
> Also, since this means those headers are a snapshot, binary 
> compatibility
> needs to be (more) carefully considered.

Good point.  Perhaps we should specify VERSION macros like
Linux has (for both Linux and gcc)?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>