Re: [Xen-devel] [Q]Which part of Xen is in slated for 2.6.23 kernel release?

[Luiz Vitor Martinez Cardoso <grabber@xxxxxxxxx>]

Hi,

Congratulations for the work! But i have a question. When xen gets stable at 
kernel.org how we can configure xen options? Today i can edit Config.mk before 
build my own kernel, how it will be done?

Regards,
Luiz Vitor Martinez Cardoso aka Grabber



Em Tue, 24 Jul 2007 22:16:16 -0700
Jeremy Fitzhardinge <jeremy@xxxxxxxx> escreveu:

> Mats Petersson wrote:
> > At 12:21 21/07/2007, pradeep singh rautela wrote:
> >> Hi Keir,
> >> On 7/21/07, Keir Fraser <keir@xxxxxxxxxxxxx> wrote:
> >>> On 21/7/07 10:50, "pradeep singh rautela" <rautelap@xxxxxxxxx> wrote:
> >>>
> >>> > Is Xen really a part of official 2.6.23 kernel now?
> >>>
> >>> Yes, assuming the patches are not dropped again from Linus's tree
> >>> before
> >>> 2.6.23 is released. But that is unlikely. They've had lots of
> >>> testing and
> >>> review.
> >>
> >> great news!!!
> >>>
> >>> > If yes i would like to ask
> >>> >  - what is accepted by Linus in the mainline kernel?
> >>> >  - Is it just the hypervisor code?
> >>> >  - What about dom0?
> >>>
> >>> The scope of the patches is domU guest support. Vanilla linux 2.6.23
> >>> will
> >>> not support running as dom0 (Jeremy is working on this for a future
> >>> Linux
> >>> release). Nor does it contain the hypervisor code itself -- you have to
> >>> obtain the Xen hypervisor separately from the kernel sources.
> >>
> >> Great!!!
> >> So this means 2.6.23 vanilla kernel can be compiled as a domU
> >> natively, right?
> >
> >
> > I think for now, only modules can be shared, kernel itself needs to be
> > compiled for DomU or Native use, but ultimately, the idea is to have
> > one kernel that does both DomU and Native in the same kernel.
> 
> To clarify, you build the kernel once, and two build products are
> vmlinux and bzImage.  If you have a bootloader which can handle it, you
> can boot vmlinux natively, or under Xen.  Xen doesn't currently support
> booting bzImage, so its really only usable for native execution.  But
> it's just a matter of packaging; the kernel code and data is bit-for-bit
> the same in both kernel images.
> 
>     J
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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