All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 07 Mar 2007 16:55:40 -0800	[thread overview]
Message-ID: <45EF5F0C.5070102@goop.org> (raw)
In-Reply-To: <1173312124.8383.35.camel@localhost.localdomain>

Tim Chen wrote:
> 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.

Thanks for identifying this.  We'll be posting a more general fix for
COMPAT_VDSO soon which will address this.

    J

WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: tim.c.chen@linux.intel.com
Cc: zach@vmware.com, linux-kernel@vger.kernel.org,
	Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: system call time increase when turning on CONFIG_PARAVIRT
Date: Wed, 07 Mar 2007 16:55:40 -0800	[thread overview]
Message-ID: <45EF5F0C.5070102@goop.org> (raw)
In-Reply-To: <1173312124.8383.35.camel@localhost.localdomain>

Tim Chen wrote:
> 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.

Thanks for identifying this.  We'll be posting a more general fix for
COMPAT_VDSO soon which will address this.

    J

  reply	other threads:[~2007-03-08  0:55 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
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 [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=45EF5F0C.5070102@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 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.