From: Keir Fraser <keir@xensource.com>
To: pradeep singh rautela <rautelap@gmail.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [Q]Which part of Xen is in slated for 2.6.23 kernel release?
Date: Sat, 21 Jul 2007 12:14:44 +0100 [thread overview]
Message-ID: <C2C7A934.B332%keir@xensource.com> (raw)
In-Reply-To: <6bc632150707210250w1972e369he0e6c5678fc84ae2@mail.gmail.com>
On 21/7/07 10:50, "pradeep singh rautela" <rautelap@gmail.com> 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.
> 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.
-- Keir
> The gitweb does shows Jeremy as comitter but it looks to me as its
> just the hypervisor part.
next prev parent reply other threads:[~2007-07-21 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 9:50 [Q]Which part of Xen is in slated for 2.6.23 kernel release? pradeep singh rautela
2007-07-21 11:14 ` Keir Fraser [this message]
2007-07-21 11:21 ` pradeep singh rautela
[not found] ` <6bc632150707210421q1397d529n5945ed943304b815@mail.gmail.co m>
2007-07-21 11:49 ` Mats Petersson
2007-07-25 5:16 ` Jeremy Fitzhardinge
2007-07-25 15:14 ` Luiz Vitor Martinez Cardoso
2007-07-25 6:22 ` Jeremy Fitzhardinge
2007-07-21 12:42 ` Keir Fraser
2007-07-21 18:24 ` Daniel P. Berrange
2007-07-21 18:27 ` Mats Petersson
2007-07-24 16:59 ` Mark Williamson
2007-07-21 18:38 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C2C7A934.B332%keir@xensource.com \
--to=keir@xensource.com \
--cc=rautelap@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.