From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Sheng Yang <sheng@linux.intel.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH 2/2][RFC] KVM: Emulate MSI-X table and PBA in kernel
Date: Sun, 2 Jan 2011 12:39:28 +0200 [thread overview]
Message-ID: <20110102103928.GA32272@redhat.com> (raw)
In-Reply-To: <4D2052C3.3020901@redhat.com>
On Sun, Jan 02, 2011 at 12:26:11PM +0200, Avi Kivity wrote:
> On 12/31/2010 05:05 AM, Sheng Yang wrote:
> >>
> >> Existing code does not support PBA in assigned devices, so at least it's
> >> not a regression there, and the virtio spec says nothing about this so
> >> we should be fine.
> >
> >I agree. At least it's not a regression. And in fact we haven't seen any device
> >driver use this. I've checked Linux kernel code, found no one used PCI_MSIX_PBA or
> >msix_pba_offset_reg().
> >
> >I guess it's fine to get MSI-X mask part in first, then deal with PBA part if
> >necessary - though we haven't seen any driver use it so far. It won't be worse
> >with this patch anyway...
>
> In a way it is worse because before, the fix would belong in user
> space, which is easier to test and distribute. Now we have to fix
> it in the kernel.
>
> However I recognize that drivers which rely on the pending bit are
> rare/nonexistent (likely on in preboot environments where interrupts
> are hard), so even if we do code it, it will likely be incorrect
> (certainly without a test).
>
> So I'll accept the patch without PBA. Michael, what about
> supporting virtio? Can we base something on this patch?
I don't see how userspace can send interrupts with this
interface unfortunately. We also need irqfd support ...
> --
> error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-01-02 10:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 8:44 [PATCH 0/2 v6] MSI-X mask bit support for KVM Sheng Yang
2010-12-22 8:44 ` [PATCH 1/2] KVM: Move struct kvm_io_device to kvm_host.h Sheng Yang
2010-12-22 8:44 ` [PATCH 2/2][RFC] KVM: Emulate MSI-X table and PBA in kernel Sheng Yang
2010-12-28 12:26 ` Avi Kivity
2010-12-29 7:18 ` Sheng Yang
2010-12-29 8:31 ` Michael S. Tsirkin
2010-12-29 8:55 ` Sheng Yang
2010-12-29 9:28 ` Michael S. Tsirkin
2010-12-30 7:32 ` Sheng Yang
2010-12-30 7:47 ` Michael S. Tsirkin
2010-12-30 7:55 ` Sheng Yang
2010-12-30 8:15 ` Michael S. Tsirkin
2010-12-30 8:24 ` Sheng Yang
2010-12-30 8:52 ` Michael S. Tsirkin
2010-12-30 9:13 ` Sheng Yang
2010-12-30 9:30 ` Avi Kivity
2010-12-30 10:32 ` Michael S. Tsirkin
2010-12-30 10:37 ` Avi Kivity
2010-12-30 11:07 ` Michael S. Tsirkin
2010-12-30 11:27 ` Avi Kivity
2010-12-30 12:17 ` Michael S. Tsirkin
2010-12-31 3:05 ` Sheng Yang
2011-01-02 9:26 ` Michael S. Tsirkin
2011-01-02 10:26 ` Avi Kivity
2011-01-02 10:39 ` Michael S. Tsirkin [this message]
2011-01-02 10:58 ` Avi Kivity
2011-01-02 11:51 ` Michael S. Tsirkin
2011-01-02 13:34 ` Avi Kivity
2011-01-02 13:57 ` Michael S. Tsirkin
2010-12-30 9:28 ` Avi Kivity
2010-12-30 10:03 ` Michael S. Tsirkin
2010-12-28 4:05 ` [PATCH 0/2 v6] MSI-X mask bit support for KVM Sheng Yang
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=20110102103928.GA32272@redhat.com \
--to=mst@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.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