virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>, zach@vmware.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: Wed, 07 Mar 2007 16:02:04 -0800	[thread overview]
Message-ID: <1173312124.8383.35.camel@localhost.localdomain> (raw)
In-Reply-To: <45E8BE79.40200@goop.org>

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

> 
> 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

It turned out that VDSO was turned off by CONFIG_PARAVIRT option,
causing the system call to use inefficient int 0x80 which led to the
increase system_call time I was seeing.  I noted that Ingo has caught
this problem and proposed a patch to correct this issue in another mail
thread.

Tim

  parent reply	other threads:[~2007-03-08  0:02 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
2007-03-03  7:00       ` Zachary Amsden
2007-03-08  0:02       ` Tim Chen [this message]
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=1173312124.8383.35.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 \
    --cc=zach@vmware.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 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).