From: Avi Kivity <avi@redhat.com>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [RFC] Moving the kvm ioapic, pic, and pit back to userspace
Date: Thu, 10 Jun 2010 05:59:03 +0300 [thread overview]
Message-ID: <4C1054F7.4030904@redhat.com> (raw)
In-Reply-To: <1A42CE6F5F474C41B63392A5F80372B21F26E3A1@shsmsx501.ccr.corp.intel.com>
On 06/10/2010 05:37 AM, Dong, Eddie wrote:
> Avi Kivity wrote:
>
>> On 06/09/2010 06:59 PM, Dong, Eddie wrote:
>>
>>> Besides VF IO interrupt and timer interrupt introduced performance
>>> overhead risk,
>>>
>> VF usually uses MSI
>>
> Typo, I mean PV IO.
>
That also uses MSI these days.
> A VF interrupt usually happens in 4-8KHZ. How about the virtio?
> I assume virtio will be widely used together w/ leagcy guest with INTx mode.
>
True, but in time it will be replaced by MSI.
Note without vhost virtio is also in userspace, so there are lots of
exits anyway for the status register.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-06-10 2:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 15:26 [Qemu-devel] [RFC] Moving the kvm ioapic, pic, and pit back to userspace Avi Kivity
2010-06-07 16:31 ` [Qemu-devel] " David S. Ahern
2010-06-07 18:46 ` Avi Kivity
2010-06-07 18:54 ` David S. Ahern
2010-06-07 19:16 ` Avi Kivity
2010-06-07 17:04 ` Anthony Liguori
2010-06-07 18:42 ` Avi Kivity
2010-06-07 22:23 ` Anthony Liguori
2010-06-08 5:48 ` Avi Kivity
2010-06-09 15:59 ` [Qemu-devel] " Dong, Eddie
2010-06-09 16:05 ` [Qemu-devel] " Avi Kivity
2010-06-10 2:37 ` [Qemu-devel] " Dong, Eddie
2010-06-10 2:59 ` Avi Kivity [this message]
2010-06-10 14:42 ` Dong, Eddie
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=4C1054F7.4030904@redhat.com \
--to=avi@redhat.com \
--cc=eddie.dong@intel.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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).