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


[Xen-devel] Re: [RFC] move Xen linux header files

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: [RFC] move Xen linux header files
From: Dan Magenheimer <dan.magenheimer@xxxxxx>
Date: Mon, 8 Aug 2005 17:56:51 +0000 (UTC)
Delivery-date: Mon, 08 Aug 2005 18:05:01 +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>
References: <20050805193615.GT7762@xxxxxxxxxxxxxxxxxxx> <loom.20050806T015614-229@xxxxxxxxxxxxxx> <20050806000924.GD7901@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Loom/3.14 (http://gmane.org/)
> > Where do any arch-dep headers go?  In the patch I'm
> > floating to linux-ia64, they are in, e.g.,
> > include/asm-ia64/xen/*.h
> include/asm-$ARCH/mach-xen/*.h is where I've put them for i386.
> I use a script which may be the most succinct way to see the change.
> Here's the core of the script:
> mv linux-2.6-xen-sparse/include/asm-xen/*.h linux-2.6-xen-sparse/include/xen/

I'm still confused... There are currently two subdirectories
of sparse/include/asm-xen/ that contain the arch-dep headers.
But the above mv command has moved them to include/xen/asm-$ARCH
not include include/asm-$ARCH/mach-xen/

Or is that just a future patch that's not part of this

Also, just one more attempt, then I'll shut up (on
this point anyway)...  xen is not a mach as it is
orthogonal to mach (e.g. could be combined with other
mach's).  E.g. arch-dep includes for ia64 should be
in include/asm-ia64/xen because they may, for example,
run on SGI's sn subarch.


Xen-devel mailing list