From: Avi Kivity <avi@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
KVM mailing list <kvm@vger.kernel.org>
Subject: Re: performance of virtual functions compared to virtio
Date: Tue, 26 Apr 2011 11:20:14 +0300 [thread overview]
Message-ID: <4DB6803E.5000603@redhat.com> (raw)
In-Reply-To: <4DB5B35B.5070703@gmail.com>
On 04/25/2011 08:46 PM, David Ahern wrote:
> >
> > Note I think in both cases we can make significant improvements:
> > - for VFs, steer device interrupts to the cpus which run the vcpus that
> > will receive the interrupts eventually (ISTR some work about this, but
> > not sure)
>
> I don't understand your point here. I thought interrupts for the VF were
> only delivered to the guest, not the host.
>
Interrupts are delivered to the host, which the forwards them to the
guest. Virtualization hardware on x86 does not allow direct-to-guest
interrupt delivery.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-04-26 8:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 1:57 performance of virtual functions compared to virtio David Ahern
2011-04-21 2:35 ` Alex Williamson
2011-04-21 8:07 ` Avi Kivity
2011-04-21 12:31 ` Stefan Hajnoczi
2011-04-21 13:09 ` Avi Kivity
2011-04-25 17:49 ` David Ahern
2011-04-26 8:19 ` Avi Kivity
2011-04-27 21:13 ` David Ahern
2011-04-28 8:07 ` Avi Kivity
2011-04-25 17:46 ` David Ahern
2011-04-26 8:20 ` Avi Kivity [this message]
2011-04-25 17:39 ` David Ahern
2011-04-25 18:13 ` Alex Williamson
2011-04-25 19:07 ` David Ahern
2011-04-25 19:29 ` Alex Williamson
2011-04-25 19:49 ` David Ahern
2011-04-25 20:27 ` Alex Williamson
2011-04-25 20:40 ` David Ahern
2011-04-25 21:02 ` Alex Williamson
2011-04-25 21:14 ` David Ahern
2011-04-25 21:18 ` Alex Williamson
2011-04-25 20:49 ` Andrew Theurer
2011-05-02 18:58 ` David Ahern
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=4DB6803E.5000603@redhat.com \
--to=avi@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=dsahern@gmail.com \
--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.