From: Arjan van de Ven <arjan@infradead.org>
To: david@lang.hm
Cc: devzero@web.de, Jeremy Fitzhardinge <jeremy@goop.org>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: Where do we stand with the Xen patches?
Date: Sun, 17 May 2009 12:33:24 -0700 [thread overview]
Message-ID: <20090517123324.2e57bc55@infradead.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0905171223250.26653@asgard>
On Sun, 17 May 2009 12:25:38 -0700 (PDT)
david@lang.hm wrote:
> On Sun, 17 May 2009, devzero@web.de wrote:
> > maybe this is iust a stupid comment (please forgive, i?m no
> > advanced kernel hacker), but can?t the code inserted by the patches
> > and which changes the fastpath just #IFDEF`ed at the critical
> > offsets ? (as building a dom0 kernel is just another build target,
> > isn`t it ?)
>
> no, if dom0 is going to be widely deployed, it will be because the
> distros turn on dom0 support by default. as a result any penalties
> due to xen support will be felt by all users of those distros (even
> if they don't use xen)
>
at minimum we need to split CONFIG_PARAVIRT up into
"want to be nice to hypervisors" and "I want to be Xen Dom0";
they look to largely not overlap.... so lets not make the costs overlap
either.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-05-17 19:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 18:37 Where do we stand with the Xen patches? devzero
2009-05-17 19:25 ` david
2009-05-17 19:33 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-17 19:46 devzero
2009-05-18 1:54 ` Jeremy Fitzhardinge
2009-05-19 13:10 ` Chris Mason
2009-05-14 19:54 Jeremy Fitzhardinge
2009-05-15 18:35 ` Ingo Molnar
2009-05-15 19:59 ` Jeremy Fitzhardinge
2009-05-18 1:36 ` FUJITA Tomonori
2009-05-18 1:42 ` Jeremy Fitzhardinge
2009-05-18 8:40 ` Ingo Molnar
2009-05-19 5:27 ` FUJITA Tomonori
2009-05-19 13:03 ` Ingo Molnar
2009-05-19 15:30 ` FUJITA Tomonori
2009-05-19 15:56 ` Ian Campbell
2009-05-20 17:06 ` Jeremy Fitzhardinge
2009-05-21 8:54 ` FUJITA Tomonori
2009-05-21 10:27 ` Ian Campbell
2009-05-21 10:28 ` Ian Campbell
2009-05-21 10:39 ` FUJITA Tomonori
2009-05-21 10:48 ` Ian Campbell
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=20090517123324.2e57bc55@infradead.org \
--to=arjan@infradead.org \
--cc=david@lang.hm \
--cc=devzero@web.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).