All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org,
	Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: system call time increase when turning on CONFIG_PARAVIRT
Date: Fri, 02 Mar 2007 15:11:51 -0800	[thread overview]
Message-ID: <1172877111.8383.4.camel@localhost.localdomain> (raw)
In-Reply-To: <45E89CFB.4090905@goop.org>

On Fri, 2007-03-02 at 13:54 -0800, Jeremy Fitzhardinge wrote:

> [ I assume you're talking about running on native hardware. ]
> 
That's correct.

> I haven't done any detailed measurements on what effect this will have,
> but it does bring the actual executed instruction stream much closer to
> the !CONFIG_PARAVIRT case, and so I would hope it would recover most or
> all of the performance loss you've noticed.
> 
I also hope that the performance can be recovered as this option could
enabled in distributions' kernels in future.

Tim

  reply	other threads:[~2007-03-02 23:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02 20:11 system call time increase when turning on CONFIG_PARAVIRT Tim Chen
2007-03-02 21:54 ` Jeremy Fitzhardinge
2007-03-02 21:54   ` Jeremy Fitzhardinge
2007-03-02 23:11   ` Tim Chen [this message]
2007-03-03  0:16     ` Jeremy Fitzhardinge
2007-03-03  0:16       ` Jeremy Fitzhardinge
2007-03-03  7:00       ` Zachary Amsden
2007-03-08  0:02       ` Tim Chen
2007-03-08  0:02         ` Tim Chen
2007-03-08  0:55         ` Jeremy Fitzhardinge
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=1172877111.8383.4.camel@localhost.localdomain \
    --to=tim.c.chen@linux.intel.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.