From: Alex Williamson <alex.williamson@redhat.com>
To: mst@redhat.com
Cc: jan.kiszka@siemens.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] Misc PCI cleanups
Date: Mon, 08 Oct 2012 09:58:32 -0600 [thread overview]
Message-ID: <1349711912.2759.96.camel@ul30vt.home> (raw)
In-Reply-To: <20121002191609.31100.77382.stgit@bling.home>
Michael, Jan,
Any comments on these? I'd like to make the PCI changes before I update
vfio-pci to make use of the new resampling irqfd in kvm. We don't have
anyone officially listed as maintainer of pci-assign since it's been
moved to qemu. I could include the pci-assign patches in my tree if you
prefer. Thanks,
Alex
On Tue, 2012-10-02 at 13:21 -0600, Alex Williamson wrote:
> A few cleanups that I'll also apply to vfio-pci. First make intx
> route checking non-fatal. vfio-pci has a fallback INTx mechanism
> that doesn't rely on this, so we can already run on q35, but not if
> we can't even probe for intx routing w/o blowing up. Next, both
> vfio-pci and pci-assign test whether INTx routing has changed using
> similar functions. Make this common. Finally, expose a way to
> get the MSI message for an MSI vector. Again, both pci-assign and
> vfio-pci need to do this to program the vector for KVM injection.
> Thanks,
>
> Alex
>
> ---
>
> Alex Williamson (6):
> pci-assign: Use msi_get_message()
> msi: Add msi_get_message()
> pci-assign: Use pci_intx_route_changed()
> pci: Helper function for testing if an INTx route changed
> pci-assign: Add support for no-route
> pci: Add INTx no-route option
>
>
> hw/kvm/pci-assign.c | 14 ++++++++------
> hw/msi.c | 45 +++++++++++++++++++++++++++++----------------
> hw/msi.h | 1 +
> hw/pci.c | 13 +++++++++++--
> hw/pci.h | 2 ++
> 5 files changed, 51 insertions(+), 24 deletions(-)
next prev parent reply other threads:[~2012-10-08 15:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 19:21 [Qemu-devel] [PATCH 0/6] Misc PCI cleanups Alex Williamson
2012-10-02 19:21 ` [Qemu-devel] [PATCH 1/6] pci: Add INTx no-route option Alex Williamson
2012-10-02 19:21 ` [Qemu-devel] [PATCH 2/6] pci-assign: Add support for no-route Alex Williamson
2012-10-02 19:55 ` Anthony Liguori
2012-10-02 20:12 ` Alex Williamson
2012-10-03 9:52 ` Paolo Bonzini
2012-10-03 12:32 ` Anthony Liguori
2012-10-02 19:21 ` [Qemu-devel] [PATCH 3/6] pci: Helper function for testing if an INTx route changed Alex Williamson
2012-10-02 19:22 ` [Qemu-devel] [PATCH 4/6] pci-assign: Use pci_intx_route_changed() Alex Williamson
2012-10-02 19:22 ` [Qemu-devel] [PATCH 5/6] msi: Add msi_get_message() Alex Williamson
2012-10-02 19:22 ` [Qemu-devel] [PATCH 6/6] pci-assign: Use msi_get_message() Alex Williamson
2012-10-08 15:58 ` Alex Williamson [this message]
2012-10-08 16:01 ` [Qemu-devel] [PATCH 0/6] Misc PCI cleanups Jan Kiszka
2012-10-08 20:15 ` Michael S. Tsirkin
2012-10-08 19:27 ` Alex Williamson
2012-10-08 21:40 ` Michael S. Tsirkin
2012-10-08 21:11 ` Alex Williamson
2012-10-08 21:50 ` Michael S. Tsirkin
2012-10-08 22:09 ` Alex Williamson
2012-10-08 22:44 ` Michael S. Tsirkin
2012-10-08 23:54 ` Alex Williamson
2012-10-11 14:11 ` Michael S. Tsirkin
2012-10-09 7:09 ` Jan Kiszka
2012-10-10 19:31 ` Alex Williamson
2012-10-11 10:37 ` Michael S. Tsirkin
2012-10-11 13:38 ` Alex Williamson
2012-10-11 13:49 ` Michael S. Tsirkin
2012-10-11 14:10 ` Alex Williamson
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=1349711912.2759.96.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--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).