public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo@kvack.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm-devel@lists.sourceforge.net, Avi Kivity <avi@qumranet.com>
Subject: Re: [patch 0/5] KVM paravirt MMU updates and cr3 caching
Date: Sat, 16 Feb 2008 23:24:30 -0300	[thread overview]
Message-ID: <20080217022430.GA2454@dmt> (raw)
In-Reply-To: <47B7739C.8090806@codemonkey.ws>

On Sat, Feb 16, 2008 at 05:37:00PM -0600, Anthony Liguori wrote:
> Marcelo Tosatti wrote:
> >The following patchset, based on earlier work by Anthony and Ingo, adds
> >paravirt_ops support for KVM guests enabling hypercall based pte updates,
> >hypercall batching and cr3 caching.
> >  
> 
> Could you post performance results for each optimization?  I'm 
> particularly curious if the hypercall batching is very useful.

Batched hypercall pte updates give 8.5% performance improvement on
kernel compile:

http://www.mail-archive.com/kvm-devel@lists.sourceforge.net/msg12395.html

I can get separate results tomorrow or Monday, but I'm sure batching
plays a significant role. For the kernel compile test, there is an
average of 5 pte updates per batched hypercall.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-02-17  2:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080216220924.733723618@redhat.com>
2008-02-16 22:09 ` [patch 1/5] KVM: add basic paravirt support Marcelo Tosatti
2008-02-16 22:09 ` [patch 2/5] KVM: hypercall based pte updates and TLB flushes Marcelo Tosatti
2008-02-16 22:09 ` [patch 3/5] KVM: hypercall batching Marcelo Tosatti
2008-02-16 22:09 ` [patch 4/5] KVM: ignore zapped root pagetables Marcelo Tosatti
2008-02-16 22:09 ` [patch 5/5] KVM: VMX cr3 cache support Marcelo Tosatti
2008-02-16 23:37 ` [patch 0/5] KVM paravirt MMU updates and cr3 caching Anthony Liguori
2008-02-17  2:24   ` Marcelo Tosatti [this message]
     [not found] ` <20080216221220.843135254@redhat.com>
2008-02-17  8:28   ` [patch 2/5] KVM: hypercall based pte updates and TLB flushes Avi Kivity
2008-02-17 13:13     ` Avi Kivity
2008-02-17 14:51       ` Marcelo Tosatti
2008-02-17 14:57         ` Avi Kivity
2008-02-18  5:00           ` Marcelo Tosatti
2008-02-17  8:32   ` Avi Kivity
     [not found] ` <20080216221220.924823582@redhat.com>
2008-02-17  8:40   ` [patch 3/5] KVM: hypercall batching Avi Kivity
2008-02-18 16:47     ` Marcelo Tosatti
2008-02-17 18:40   ` Hollis Blanchard
2008-02-18  8:06     ` Avi Kivity
2008-02-18  8:43       ` Christian Borntraeger
2008-02-18  8:47         ` Avi Kivity
     [not found]       ` <1203361276.3428.6.camel@basalt>
2008-02-19  8:30         ` Avi Kivity
     [not found] ` <20080216221221.002948712@redhat.com>
2008-02-17  8:52   ` [patch 4/5] KVM: ignore zapped root pagetables Avi Kivity
2008-02-16 22:09 [patch 0/5] KVM paravirt MMU updates and cr3 caching Marcelo Tosatti

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=20080217022430.GA2454@dmt \
    --to=marcelo@kvack.org \
    --cc=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    /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