From: Keir Fraser <keir@xensource.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: 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 19:38:40 +0100 [thread overview]
Message-ID: <C2C81140.B352%keir@xensource.com> (raw)
In-Reply-To: <20070721182440.GA27107@redhat.com>
On 21/7/07 19:24, "Daniel P. Berrange" <berrange@redhat.com> wrote:
>> Yes. In fact the paravirt_ops framework means that you can build a single
>> kernel that will work natively or on Xen (or on VMware or lguest or ...).
>
> I thought that with this initial merge, we stll had to build separate
> images for bare metal vs Xen paravirt because of the way Linux uses
> the bzImage, while Xen is in ELF format ? Or has this bootup difference
> already been resolved ?
Actually yes, it's still in progress. So currently it is true that you can
target native or Xen from a single *build*, but you then take different
image files (vmlinux vs bzImage).
-- Keir
prev parent reply other threads:[~2007-07-21 18:38 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
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 [this message]
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=C2C81140.B352%keir@xensource.com \
--to=keir@xensource.com \
--cc=berrange@redhat.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.