From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
xen-devel@lists.xensource.com,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [FW: FYI: The plan for Xen kernels in Fedora 9]
Date: Mon, 10 Dec 2007 17:36:05 -0800 [thread overview]
Message-ID: <475DE985.9040603@goop.org> (raw)
In-Reply-To: <D470B4E54465E3469E2ABBC5AFAC390F024D8D10@pdsmsx412.ccr.corp.intel.com>
Tian, Kevin wrote:
> Or take a neutral one like CONFIG_XEN_PRIV?
Why is that an improvement? I could see a finer grain config to do
driver domains, perhaps, but it doesn't seem worthwhile at this point.
But it might be useful to have some marker of which code is necessary
for Dom0 functionality, and which is core Xen support.
J
next prev parent reply other threads:[~2007-12-11 1:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 15:20 [FW: FYI: The plan for Xen kernels in Fedora 9] Daniel P. Berrange
2007-12-10 15:32 ` Keir Fraser
2007-12-10 17:06 ` Stephen C. Tweedie
2007-12-10 17:38 ` Stephen C. Tweedie
2007-12-11 0:31 ` Chuck Short
2007-12-11 17:41 ` Stephen C. Tweedie
2007-12-11 0:36 ` Jeremy Fitzhardinge
2007-12-11 1:30 ` Tian, Kevin
2007-12-11 1:36 ` Jeremy Fitzhardinge [this message]
2007-12-11 1:46 ` Tian, Kevin
2007-12-11 12:08 ` Stephen C. Tweedie
2007-12-11 16:57 ` Jeremy Fitzhardinge
2007-12-11 17:39 ` Stephen C. Tweedie
2007-12-10 17:47 ` Stephen C. Tweedie
2007-12-10 19:12 ` Jeremy Fitzhardinge
2007-12-10 21:38 ` Mark Williamson
2007-12-10 21:48 ` Jeremy Fitzhardinge
2007-12-11 17:32 ` Stephen C. Tweedie
2007-12-11 19:24 ` Jeremy Fitzhardinge
2007-12-10 21:55 ` Daniel P. Berrange
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=475DE985.9040603@goop.org \
--to=jeremy@goop.org \
--cc=berrange@redhat.com \
--cc=kevin.tian@intel.com \
--cc=sct@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.