From: Jeremy Fitzhardinge <jeremy@goop.org>
To: tim.c.chen@linux.intel.com
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: system call time increase when turning on CONFIG_PARAVIRT
Date: Fri, 02 Mar 2007 16:16:57 -0800 [thread overview]
Message-ID: <45E8BE79.40200@goop.org> (raw)
In-Reply-To: <1172877111.8383.4.camel@localhost.localdomain>
Tim Chen wrote:
> I also hope that the performance can be recovered as this option could
> enabled in distributions' kernels in future.
Yes, the intent is that running a CONFIG_PARAVIRT kernel on native
hardware will have negligible performance hit compared to running a
non-paravirt kernel.
J
next prev parent reply other threads:[~2007-03-03 0:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1172866274.4898.14.camel@localhost.localdomain>
2007-03-02 21:54 ` system call time increase when turning on CONFIG_PARAVIRT Jeremy Fitzhardinge
2007-03-02 23:11 ` Tim Chen
2007-03-03 0:16 ` Jeremy Fitzhardinge [this message]
2007-03-03 7:00 ` Zachary Amsden
2007-03-08 0:02 ` Tim Chen
2007-03-08 0:55 ` Jeremy Fitzhardinge
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=45E8BE79.40200@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@linux.intel.com \
--cc=virtualization@lists.osdl.org \
/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).