All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omar Khan <okhan-e94Sedi4moU@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: paravirtualization structure
Date: Mon, 19 Feb 2007 20:29:34 +0000 (UTC)	[thread overview]
Message-ID: <loom.20070219T211655-267@post.gmane.org> (raw)
In-Reply-To: 45D9C127.9050201@qumranet.com

Avi Kivity <avi@...> writes:


> The hypercall sequence does not avoid a vmexit.  The guest issues a 
> vmcall instruction, which is trapped and processed by the host.
> 

Thanks for replying Avi. In your response
 (http://article.gmane.org/gmane.linux.kernel/481457) to the announcement of the
 KVM paravirtualization patch you said about the cr3 related hypercall that:

"The gain probably comes not only from avoiding the vmentry/vmexit, but also
from avoiding the flushing of the global page tlb entries."

Is the vmexit caused by the vmcall more efficient/different than the vmexit that
is caused by writing to the cr3 register say. 

Thanks

Omar Khan





-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2007-02-19 20:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19 15:17 paravirtualization structure Omar Khan
     [not found] ` <loom.20070219T155153-393-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-02-19 15:24   ` Avi Kivity
2007-02-19 20:29     ` Omar Khan [this message]
     [not found]       ` <loom.20070219T211655-267-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-02-19 21:18         ` Dor Laor
2007-02-20  0:47           ` Omar Khan
     [not found]             ` <loom.20070220T011441-39-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-02-20  7:14               ` Avi Kivity
2007-02-20  8:18               ` Arjan van de Ven

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=loom.20070219T211655-267@post.gmane.org \
    --to=okhan-e94sedi4mou@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 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.