virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	virtualization
	<virtualization-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [PATCH 0/5] KVM paravirt_ops backend (v3)
Date: Thu, 21 Jun 2007 08:19:31 -0500	[thread overview]
Message-ID: <467A7AE3.505@codemonkey.ws> (raw)
In-Reply-To: <467A4280.9060503-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Avi Kivity wrote:
> Anthony Liguori wrote:
>> Hi,
>>
>> This is an update to the paravirt_ops KVM backend series.  I've made 
>> a number of changes and attempted to incorporate all the feedback 
>> from the last review.  Some highlights:
>>
>> 1) Clean up the paravirt time source patch to use a more Xen-like model
>> 2) Change the hypercall queueing to pass a PA on the flush hypercall
>> 3) Add MMU support for release_{pt,pd} and TLB flush
>> 4) Use KVM specific errno values
>> 5) Switch from per_cpu to more appropriate functions
>>
>> As for performance, I've got a few interesting results.  kbuild with 
>> a guest using 2G of memory goes from 19 minutes to 12 minutes with 
>> the full series applied.  Using 512mb, the build time goes from 10.75 
>> minutes to 9 minutes.  For 512mb, native is around 7 minutes so 
>> that's pretty close to what Avi had seen.  The more dramatic 
>> improvement with large memory guests is probably because of the 
>> increased shadow page table activity due to high mem.
>
> Ah, that explains why we were getting such different results.  My 
> tests were on x86-64.
>
>>
>> virtbench shows major improvements but I'm not 100% confident yet in 
>> the results as they are not very stable.  I don't yet have a 
>> benchmark that shows the benefit of the CR caching so if I don't find 
>> one, I'll drop that from the queue.
>>
>
> The only barrier to merging is that we're introducing yet another 
> stable ABI.  Since we can turn off things that turn out not so good 
> later, and expect the guest to survive, I'm not to worried, so I'm 
> inclined to merge this.

Some unsigned longs are in kvm_para.h so x86_64 won't work ATM as a 
host.  I'll fix that and do proper testing on a 64 bit host for the next 
posting (along with save/restore support).

Regards,

Anthony Liguori


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

  parent reply	other threads:[~2007-06-21 13:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21  3:04 [PATCH 0/5] KVM paravirt_ops backend (v3) Anthony Liguori
     [not found] ` <4679EAAF.2060103-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-06-21  3:05   ` [PATCH 1/5] KVM paravirt_ops core infrastructure Anthony Liguori
2007-06-21  3:06   ` [PATCH 2/5] KVM: paravirt time source Anthony Liguori
2007-06-21  3:07   ` [PATCH 3/5] KVM: Implement CR read caching for KVM paravirt_ops Anthony Liguori
2007-06-21  3:08   ` [PATCH 4/5] KVM: Add paravirt MMU write support Anthony Liguori
2007-06-21  3:09   ` [PATCH 5/5] KVM: Add hypercall queue for paravirt_ops implementation Anthony Liguori
2007-06-21  3:16   ` [PATCH 0/5] KVM paravirt_ops backend (v3) Anthony Liguori
2007-06-21  9:18   ` Avi Kivity
     [not found]     ` <467A4280.9060503-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-21 13:19       ` Anthony Liguori [this message]
2007-06-21  9:26   ` Li, Xin B

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=467A7AE3.505@codemonkey.ws \
    --to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=virtualization-qjLDD68F18O7TbgM5vRIOg@public.gmane.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).