From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: "xen-devel@lists.xensource.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: Tue, 11 Dec 2007 08:57:47 -0800 [thread overview]
Message-ID: <475EC18B.3090500@goop.org> (raw)
In-Reply-To: <1197374909.8541.3.camel@sisko.scot.redhat.com>
Stephen C. Tweedie wrote:
> Hi,
>
> On Mon, 2007-12-10 at 16:36 -0800, Jeremy Fitzhardinge wrote:
>
>
>> I just had a quick look through this, and it looks good to me. One
>> thing though: I'm wondering if we shouldn't have CONFIG_XEN_DOM0 protect
>> this stuff, so that its possible to build a domU-only kernel.
>>
>
> Yep, I did wonder about that.
>
> But... there's actually quite a lot that isn't really dom0-specific.
> Rather, it's IO-domain-specific. Configure a PV guest with PCI
> passthrough and you'd want much of the same functionality in it.
>
> Also, adding CONFIG entries just increases the size of the source right
> now. I certainly think it's worth having eventually, but for now I'm
> aiming for minimal invasiveness, so I haven't bothered with domU-only
> configs.
>
> If people think it's important I can add them sooner rather than later,
> of course.
I think they're useful as documentation, so you can tell whether a piece
of code is dom0/io-specific vs generic. On the other hand, #ifdefs are
undesirable, and more config options just means more combinatorial build
testing.
So put me down as uselessly indecisive on this one.
J
next prev parent reply other threads:[~2007-12-11 16:57 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
2007-12-11 1:46 ` Tian, Kevin
2007-12-11 12:08 ` Stephen C. Tweedie
2007-12-11 16:57 ` Jeremy Fitzhardinge [this message]
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=475EC18B.3090500@goop.org \
--to=jeremy@goop.org \
--cc=berrange@redhat.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.