From: Avi Kivity <avi@qumranet.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>, kvm-devel <kvm@vger.kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [patch 4/4] KVM: allow direct access to PMTimer port
Date: Sun, 25 May 2008 15:31:03 +0300 [thread overview]
Message-ID: <48395C07.1050005@qumranet.com> (raw)
In-Reply-To: <20080525000036.710955693@localhost.localdomain>
Marcelo Tosatti wrote:
> There's not much point in exiting for pmtimer reads, since it runs at a
> fixed clock rate and its start value is undefined.
>
On a migration farm with lots of different hardware, eventually all
guests will have migrated and none of them will be able to use the
passthrough port.
What about emulating pmtimer in the host kernel instead of userspace?
It increases the hit from 1 exit to 3 exits, but they're much faster exits.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-05-25 12:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-24 23:43 [patch 0/4] C2 "emulation" Marcelo Tosatti
2008-05-24 23:43 ` [patch 1/4] QEMU/KVM: self-disabling C2 emulation Marcelo Tosatti
2008-05-24 23:43 ` [patch 2/4] libkvm: KVM_GET_PMTIMER ioctl support Marcelo Tosatti
2008-05-24 23:43 ` [patch 3/4] QEMU/KVM: non-virtualized ACPI PMTimer support Marcelo Tosatti
2008-05-25 10:18 ` Avi Kivity
2008-05-25 16:32 ` Marcelo Tosatti
2008-05-26 8:16 ` Avi Kivity
2008-05-29 17:56 ` Marcelo Tosatti
2008-05-31 7:52 ` Avi Kivity
2008-05-25 10:19 ` Avi Kivity
2008-05-25 17:39 ` Marcelo Tosatti
2008-05-26 8:23 ` Avi Kivity
2008-05-24 23:43 ` [patch 4/4] KVM: allow direct access to PMTimer port Marcelo Tosatti
2008-05-25 10:04 ` Avi Kivity
2008-05-25 16:09 ` Marcelo Tosatti
2008-05-25 12:31 ` Avi Kivity [this message]
2008-05-25 16:12 ` Marcelo Tosatti
2008-05-26 8:03 ` Avi Kivity
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=48395C07.1050005@qumranet.com \
--to=avi@qumranet.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=mtosatti@redhat.com \
/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