Mailing List Archive

On Fri, Aug 12, 2005 at 09:07:13AM -0700, Magenheimer, Dan (HP Labs Fort Collins) wrote:
> Is the top level CONFIG option planned to be CONFIG_XEN?
> Will CONFIG_XEN turn on any changes in Linux common code
> that may not be necessary changes for non-x86?
>
> I'm submitting some patches to Linux/ia64 as a foundation
> for Xen/ia64 support... I'm hoping that just enabling
> CONFIG_XEN via the top level Kconfig will do the right
> thing regardless of architecture.

Hi Dan,

CONFIG_XEN is suppose to be ARCH-agnostic
CONFIG_X86_XEN is for i386-xen

--
Vincent Hanquez

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

> CONFIG_XEN is suppose to be ARCH-agnostic
> CONFIG_X86_XEN is for i386-xen

Perfect! Thanks!

Perhaps the CONFIG_X86_XEN designation should start appearing
in the -sparse trees?. I'm hoping to start merging Xen/ia64
changes into the -sparse trees at some point and it
doesn't require any patches outside of arch/ia64, asm-ia64,
and of course the xen common directories (drivers/xen, etc).

If the Xen/x86-required changes to linux common files
(include/linux/highmem.h for example) are ifdef'd,
then other architectures can use the same mkbuildtree.

Dan

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

* Magenheimer, Dan (HP Labs Fort Collins) (dan.magenheimer@hp.com) wrote:
> Is the top level CONFIG option planned to be CONFIG_XEN?
> Will CONFIG_XEN turn on any changes in Linux common code
> that may not be necessary changes for non-x86?

For the moment, yes. That's what we're using on x86_32/64 side too.
I don't know how long those will last w/out becoming more general.
Certainly for the purpose of patch submission/discussion with Linux/ia64
it's reasonable. But perhaps it should become something that's more
feature specific it that's possible, so x86 Xen and ia64 Xen configs can
enable/disable as needed?

> I'm submitting some patches to Linux/ia64 as a foundation
> for Xen/ia64 support... I'm hoping that just enabling
> CONFIG_XEN via the top level Kconfig will do the right
> thing regardless of architecture.

What do the patches look like? Maybe there's overlap with what we're
already working on...

thanks,
-chris

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

> > I'm submitting some patches to Linux/ia64 as a foundation
> > for Xen/ia64 support... I'm hoping that just enabling
> > CONFIG_XEN via the top level Kconfig will do the right
> > thing regardless of architecture.
>
> What do the patches look like? Maybe there's overlap with what we're
> already working on...

All required changes for Xenlinux/ia64 are in linux/arch/ia64 or
include/asm-ia64 (which is why I want to avoid picking up
any changes for Xen/x86 in common code). Oh, except of course
the drivers/xen stuff which will hopefully soon be archdep.

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

On 12 Aug 2005, at 17:56, Magenheimer, Dan (HP Labs Fort Collins) wrote:

> Perhaps the CONFIG_X86_XEN designation should start appearing
> in the -sparse trees?. I'm hoping to start merging Xen/ia64
> changes into the -sparse trees at some point and it
> doesn't require any patches outside of arch/ia64, asm-ia64,
> and of course the xen common directories (drivers/xen, etc).
>
> If the Xen/x86-required changes to linux common files
> (include/linux/highmem.h for example) are ifdef'd,
> then other architectures can use the same mkbuildtree.

None of the common code changes are CONFIG_XEN'ed, and they are
designed not to break compilation of any other architecture. So
xen/ia64 should integrate with them just fine with no modification
required.

There is no CONFIG_X86_XEN, because there has not so far been any need
for it.

-- Keir


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

* Magenheimer, Dan (HP Labs Fort Collins) (dan.magenheimer@hp.com) wrote:
> > > I'm submitting some patches to Linux/ia64 as a foundation
> > > for Xen/ia64 support... I'm hoping that just enabling
> > > CONFIG_XEN via the top level Kconfig will do the right
> > > thing regardless of architecture.
> >
> > What do the patches look like? Maybe there's overlap with what we're
> > already working on...
>
> All required changes for Xenlinux/ia64 are in linux/arch/ia64 or
> include/asm-ia64 (which is why I want to avoid picking up
> any changes for Xen/x86 in common code). Oh, except of course
> the drivers/xen stuff which will hopefully soon be archdep.

Ah, x86 won't pick up anything but the drivers/xen stuff. For some
reason I thought you meant core kernel.

thanks,
-chris

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