From: Alex Williamson <alex.williamson@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
kvm@vger.kernel.org, aik@ozlabs.ru,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>,
Andreas Hartmann <andihartmann@01019freenet.de>
Subject: Re: [Qemu-devel] [PATCH 0/3] VFIO-based PCI device assignment for QEMU 1.2
Date: Mon, 13 Aug 2012 14:56:53 -0600 [thread overview]
Message-ID: <1344891413.4683.127.camel@ul30vt.home> (raw)
In-Reply-To: <CAAu8pHsCHVtZz72Kho6DERW8JY+aOzbEpsF=6gKYes2Vqd-XYw@mail.gmail.com>
On Mon, 2012-08-13 at 20:48 +0000, Blue Swirl wrote:
> On Mon, Aug 13, 2012 at 7:33 PM, Anthony Liguori <aliguori@us.ibm.com> wrote:
> > Alex Williamson <alex.williamson@redhat.com> writes:
> >
> >> On Mon, 2012-08-13 at 08:27 -0500, Anthony Liguori wrote:
> >>> Alex Williamson <alex.williamson@redhat.com> writes:
> >>>
> >>> > VFIO kernel support was just merged into Linux, so I'd like to
> >>> > formally propose inclusion of the QEMU vfio-pci driver for
> >>> > QEMU 1.2. Included here is support for x86 PCI device assignment.
> >>> > PCI INTx is not yet enabled, but devices making use of either MSI
> >>> > or MSI-X work. The level irqfd and eoifd support I've proposed
> >>> > for KVM enable an accelerated patch for this through KVM. I'd
> >>> > like to get this base driver in first and enable the remaining
> >>> > support in-tree.
> >>> >
> >>> > I've split this version up a little from the RFC to make it a bit
> >>> > easier to review. Review comments from Blue Swirl and Avi are
> >>> > already incorporated, including Avi's requests to simplify both
> >>> > the PCI BAR mapping and unmapping paths.
> >>>
> >>> Hi Alex,
> >>>
> >>> Thanks for pushing this forward! Hopefully this will finally kill off
> >>> qemu-kvm.git for good.
> >>>
> >>> I think this series is going to have to wait for 1.3 to open up. We
> >>> have a very short release window for this release and I'd feel a lot
> >>> more comfortable having such a significant feature spend some time in
> >>> the development cycle getting testing/review.
> >>>
> >>> I'd like to see a few Reviewed-by's too for this series before it goes
> >>> in. I expect they won't be hard to get but I also expect it will take a
> >>> few more revisions of this series to get there.
> >>
> >> That's disappointing, but I can understand your reluctance. Blue Swirl
> >> reviewed the RFC and could perhaps add a Reviewed-by. Alexey has been
> >> working on the POWER port and I'm sure could provide a Reviewed-by. We
> >> also have a few early adopters that are already making use of this code.
> >> Towards accepting it, the driver is entirely self contained, there's
> >> really no risk to the rest of qemu. The only missing functionality is
> >> legacy interrupt support. Perhaps there's a compromise where this
> >> driver could be considered a tech preview in 1.2 (x-vfio-pci?).
> >> Thanks,
> >
> > Yeah, if a few people were willing to at least give an Acked-by by
> > Wednesday, I'd be okay taking this in a "preview" or something like
> > that.
>
> Acked-by: Blue Swirl <blauwirbel@gmail.com>
Thank you! :)
next prev parent reply other threads:[~2012-08-13 20:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 5:18 [Qemu-devel] [PATCH 0/3] VFIO-based PCI device assignment for QEMU 1.2 Alex Williamson
2012-08-01 5:18 ` [Qemu-devel] [PATCH 1/3] vfio: Import vfio kernel header Alex Williamson
2012-08-01 7:13 ` Jan Kiszka
2012-08-01 18:09 ` Alex Williamson
2012-08-02 9:02 ` Jan Kiszka
2012-08-02 16:37 ` Alex Williamson
2012-08-02 16:45 ` Jan Kiszka
2012-08-01 5:18 ` [Qemu-devel] [PATCH 2/3] vfio: vfio-pci device assignment driver Alex Williamson
2012-08-13 22:18 ` Anthony Liguori
2012-08-14 5:25 ` Alex Williamson
2012-08-14 7:12 ` Stefan Hajnoczi
2012-08-14 13:51 ` Alex Williamson
2012-08-14 15:53 ` Avi Kivity
2012-08-14 17:23 ` Alex Williamson
2012-08-15 8:56 ` Avi Kivity
2012-08-01 5:18 ` [Qemu-devel] [PATCH 3/3] vfio: Enable vfio-pci and mark supported Alex Williamson
2012-08-01 7:15 ` Jan Kiszka
2012-08-01 18:14 ` Alex Williamson
2012-08-01 19:40 ` Alex Williamson
2012-08-02 9:03 ` Jan Kiszka
2012-08-13 22:19 ` Anthony Liguori
2012-08-14 5:27 ` Alex Williamson
2012-08-14 14:35 ` Avi Kivity
2012-08-13 13:27 ` [Qemu-devel] [PATCH 0/3] VFIO-based PCI device assignment for QEMU 1.2 Anthony Liguori
2012-08-13 13:58 ` Avi Kivity
2012-08-13 14:04 ` Jan Kiszka
2012-08-13 19:31 ` Anthony Liguori
2012-08-14 7:19 ` Jan Kiszka
2012-08-14 14:42 ` Avi Kivity
2012-08-14 14:53 ` Cole Robinson
2012-08-14 15:04 ` Jan Kiszka
2012-08-14 15:28 ` Cole Robinson
2012-08-13 14:23 ` Alex Williamson
2012-08-13 15:48 ` Andreas Hartmann
2012-08-13 16:14 ` Alex Williamson
2012-08-13 16:36 ` Andreas Hartmann
2012-08-13 16:57 ` Alex Williamson
2012-08-13 18:32 ` Andreas Hartmann
2012-08-13 19:33 ` Anthony Liguori
2012-08-13 20:48 ` Blue Swirl
2012-08-13 20:56 ` Alex Williamson [this message]
2012-08-13 20:55 ` [Qemu-devel] VFIO: Call for reviewers (was Re: [PATCH 0/3] VFIO-based PCI device assignment for QEMU 1.2) 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=1344891413.4683.127.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=aliguori@us.ibm.com \
--cc=andihartmann@01019freenet.de \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--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).