* Dan Magenheimer (dan.magenheimer@xxxxxx) wrote:
> > 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/
No, I think you misread. Only the *.h are moved. Those are not machine
specific, rather core xen headers. The actual machine specific bits are
left behind in this patch, because that's the actual meat of doing the
subarch split. Basically, moving all this stuff about while both sides
(xen and linux) are moving is a pain, so I'm looking for simple bits
that could go into xen w/out requiring the full subarch patch. I've
currently dropped this, and now the subarch is using the core headers in
the old (current) location, and only moving the asm-xen/asm-$ARCH/ bits.
It means I have to maintain some copies of headers, but it too can be
automated, so maybe that's the better approach.
> 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.
Yes, but Xen also needs to override some of the defaults. There may be
same issue with conflicting with subarch changes as there is with xen vs
base arch. I don't know the best solution yet.
thanks,
-chris
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home