All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Christoffer Dall <cdall@cs.columbia.edu>
Cc: KVM General <kvm@vger.kernel.org>
Subject: Re: vmexit cycle cost
Date: Sun, 18 Nov 2012 16:16:37 +0200	[thread overview]
Message-ID: <50A8EDC5.7010709@redhat.com> (raw)
In-Reply-To: <CAEDV+gKNOXx-5E-U_dCdem=VrkK-gE8j4nt-RScg0Rxq1K-6qw@mail.gmail.com>

On 11/16/2012 06:56 PM, Christoffer Dall wrote:
> Hi all,
> 
> just a quick question: using the kvm-unittest vmexit test, it seems
> using a VMCALL for exit, a round-trip to the host takes roughly 1000
> cycles on a modern processor. This number sounds quite low to me. Can
> anyone verify if it's reasonable or have more data on this number has
> developed over time given newer processors?

It's reasonable, not low (this number can never be low enough).


-- 
error compiling committee.c: too many arguments to function

      reply	other threads:[~2012-11-18 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 16:56 vmexit cycle cost Christoffer Dall
2012-11-18 14:16 ` Avi Kivity [this message]

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=50A8EDC5.7010709@redhat.com \
    --to=avi@redhat.com \
    --cc=cdall@cs.columbia.edu \
    --cc=kvm@vger.kernel.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.