public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: State of current pv_ops backend for KVM?
Date: Wed, 30 May 2007 16:04:28 +1000	[thread overview]
Message-ID: <1180505068.30202.88.camel@localhost.localdomain> (raw)
In-Reply-To: <465D051F.20706-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

On Wed, 2007-05-30 at 08:01 +0300, Avi Kivity wrote:
> Rusty Russell wrote:
> > but it's not clear to me that verifying PTEs is that
> > much faster than shadowing them if you're prepared to be that invasive
> > in the guest anyway.
> >   
> This can probably be measured on Xen which can switch from direct to
> shadow mode on runtime.

Sorry, I was a little oblique here.  The Xen shadow mode code is aimed
at supporting full virtualization, so it's not really a fair
comparison.  

Their direct page access code hooks deep into the guest; the outstanding
question is how efficient would a shadow implementation which made
similar guest changes be?

Unfortunately, there's a lot of coding between here and the answer 8)

Rusty.


-------------------------------------------------------------------------
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-05-30  6:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29  1:54 State of current pv_ops backend for KVM? Anthony Liguori
     [not found] ` <465B87CE.6030801-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-05-29  6:11   ` Ingo Molnar
     [not found]     ` <20070529061128.GA27037-X9Un+BFzKDI@public.gmane.org>
2007-05-29  6:11       ` Ingo Molnar
2007-05-29 11:47   ` Avi Kivity
     [not found]     ` <465C12C0.9030906-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-29 13:49       ` Anthony Liguori
     [not found]         ` <465C2F75.3080603-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-05-29 14:00           ` Avi Kivity
     [not found]             ` <465C31F2.8080007-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-29 14:19               ` Anthony Liguori
     [not found]                 ` <465C3671.9000404-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-05-29 14:28                   ` Avi Kivity
2007-05-30  2:35               ` Rusty Russell
     [not found]                 ` <1180492544.30202.72.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-05-30  5:01                   ` Avi Kivity
     [not found]                     ` <465D051F.20706-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-05-30  6:04                       ` Rusty Russell [this message]
2007-05-30  2:24   ` Rusty Russell
     [not found]     ` <1180491861.30202.61.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-05-30  2:51       ` Anthony Liguori
     [not found]         ` <465CE6AD.7000206-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-05-30 18:02           ` Zachary Amsden
     [not found]             ` <465DBC39.7090308-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2007-05-30 18:20               ` Anthony Liguori

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=1180505068.30202.88.camel@localhost.localdomain \
    --to=rusty-8n+1lvoiyb80n/f98k4iww@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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