From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
Alex Williamson <alex.williamson@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v4] KVM: Allow host IRQ sharing for assigned PCI 2.3 devices
Date: Tue, 06 Mar 2012 17:34:01 +0200 [thread overview]
Message-ID: <4F562E69.4040907@redhat.com> (raw)
In-Reply-To: <4F4CD47A.3080708@siemens.com>
On 02/28/2012 03:19 PM, Jan Kiszka wrote:
> PCI 2.3 allows to generically disable IRQ sources at device level. This
> enables us to share legacy IRQs of such devices with other host devices
> when passing them to a guest.
>
> The new IRQ sharing feature introduced here is optional, user space has
> to request it explicitly. Moreover, user space can inform us about its
> view of PCI_COMMAND_INTX_DISABLE so that we can avoid unmasking the
> interrupt and signaling it if the guest masked it via the virtualized
> PCI config space.
Long delay, sorry.
I'm sure we discussed this before, so a URL would be sufficient: why
cannot this be transparent to userspace?
As for the actual patch, I am so unfamiliar with the device assignment
code now that I'll have to rely on Alex's review.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-03-06 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 13:19 [PATCH v4] KVM: Allow host IRQ sharing for assigned PCI 2.3 devices Jan Kiszka
2012-02-29 15:22 ` Alex Williamson
2012-02-29 15:38 ` Jan Kiszka
2012-02-29 16:27 ` Alex Williamson
2012-03-06 15:34 ` Avi Kivity [this message]
2012-03-06 15:41 ` Jan Kiszka
2012-03-06 15:53 ` Avi Kivity
2012-03-06 16:06 ` Michael S. Tsirkin
2012-03-07 10:23 ` 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=4F562E69.4040907@redhat.com \
--to=avi@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).