From: Tom Lyon <pugs@cisco.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
kvm@vger.kernel.org, avi@redhat.com, chrisw@redhat.com,
mst@redhat.com
Subject: Re: [PATCH 0/5] Fixes, non-PCI-2.3 support, EOI enhancements
Date: Mon, 1 Nov 2010 14:22:00 -0700 [thread overview]
Message-ID: <201011011422.01165.pugs@cisco.com> (raw)
In-Reply-To: <20101030164626.885.89216.stgit@s20.home>
I've applied all your patches. Thanks!
On Saturday, October 30, 2010 09:58:55 am Alex Williamson wrote:
> Hi Tom,
>
> I've updated some patches I've been working on to v5 and wanted to
> see what you think. I also found a couple minor bugs, fixed in this
> series.
>
> The main idea is that since the VFIO interface defines that the INTx
> interrupt is disabled when it fires, we should provide an interface
> to re-enable it. We currently have to do a read-modify-write to PCI
> config space, requring two ioctls. I introduce an ioctl to do this
> for us. An important aspect of this is that now we can support
> non-PCI-2.3 devices since re-enabling the interrupt is abstracted
> (with the same caveat as current KVM device assignment, that they
> must get an exclusive interrupt). The real trick though is that we
> can then also create an irqfd-like mechanism to trigger re-enabling
> interrupts from and eventfd. This allows qemu to do all the setup
> for connecting interrupts from VFIO into KVM and EOIs from KVM to
> VFIO, then lets userspace get completely out of the way.
>
> Hope you like it. Thanks,
>
> Alex
> ---
>
> Alex Williamson (5):
> vfio: Add a new ioctl to support EOI via eventfd
> vfio: Add support for non-PCI 2.3 compliant devices
> vfio: Add ioctl to re-enable interrupts
> vfio: Fix requested regions
> vfio: Fix the ROM mask
>
>
> drivers/vfio/vfio_intrs.c | 254
> +++++++++++++++++++++++++++++++++++++--- drivers/vfio/vfio_main.c |
> 37 +++++-
> drivers/vfio/vfio_pci_config.c | 2
> drivers/vfio/vfio_rdwr.c | 4 -
> include/linux/vfio.h | 14 ++
> 5 files changed, 279 insertions(+), 32 deletions(-)
prev parent reply other threads:[~2010-11-01 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 16:58 [PATCH 0/5] Fixes, non-PCI-2.3 support, EOI enhancements Alex Williamson
2010-10-30 16:59 ` [PATCH 1/5] vfio: Fix the ROM mask Alex Williamson
2010-10-30 16:59 ` [PATCH 2/5] vfio: Fix requested regions Alex Williamson
2010-10-30 16:59 ` [PATCH 3/5] vfio: Add ioctl to re-enable interrupts Alex Williamson
2010-10-30 16:59 ` [PATCH 4/5] vfio: Add support for non-PCI 2.3 compliant devices Alex Williamson
2010-10-30 16:59 ` [PATCH 5/5] vfio: Add a new ioctl to support EOI via eventfd Alex Williamson
2010-11-01 21:22 ` Tom Lyon [this message]
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=201011011422.01165.pugs@cisco.com \
--to=pugs@cisco.com \
--cc=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@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