From: Alex Williamson <alex.williamson@redhat.com>
To: "Liu, Yi L" <yi.l.liu@linux.intel.com>
Cc: qemu-devel@nongnu.org, aik@ozlabs.ru, eric.auger@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.11] vfio: Fix vfio-kvm group registration
Date: Tue, 5 Dec 2017 20:12:58 -0700 [thread overview]
Message-ID: <20171205201258.6111c71c@t450s.home> (raw)
In-Reply-To: <20171206024443.GA1164@sky-dev>
On Wed, 6 Dec 2017 10:44:43 +0800
"Liu, Yi L" <yi.l.liu@linux.intel.com> wrote:
> On Tue, Dec 05, 2017 at 02:09:07PM -0700, Alex Williamson wrote:
> > Commit 8c37faa475f3 ("vfio-pci, ppc64/spapr: Reorder group-to-container
> > attaching") moved registration of groups with the vfio-kvm device from
> > vfio_get_group() to vfio_connect_container(), but it missed the case
> > where a group is attached to an existing container and takes an early
> > exit. Perhaps this is a less common case on ppc64/spapr, but on x86
> > (without viommu) all groups are connected to the same container and
> > thus only the first group gets registered with the vfio-kvm device.
> > This becomes a problem if we then hot-unplug the devices associated
> > with that first group and we end up with KVM being misinformed about
> > any vfio connections that might remain. Fix by including the call to
> > vfio_kvm_device_add_group() in this early exit path.
> >
> > Fixes: 8c37faa475f3 ("vfio-pci, ppc64/spapr: Reorder group-to-container attaching")
> > Cc: qemu-stable@nongnu.org # qemu-2.10+
> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> > ---
> >
> > This bug also existed in QEMU 2.10, but I think the fix is sufficiently
> > obvious (famous last words) to propose for 2.11 at this late date. If
> > the first group is hot unplugged then KVM may revert to code emulation
> > that assumes no non-coherent DMA is present on some systems. Also for
> > KVMGT, if the vGPU is not the first device registered, then the
> > notifier to enable linkages to KVM would not be called. Please review.
> > Thanks,
>
> Alex, for x86, I suppose it doesn't exist in the case which viommu is exposed
> to guest?
With viommu, I believe each group would be in its own AddressSpace and
therefore get a separate container, so I don't think it'd be an issue.
It's only subsequent groups added to the same container which are
missed. Thanks,
Alex
> > hw/vfio/common.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> > index 7b2924c0ef19..7007878e345e 100644
> > --- a/hw/vfio/common.c
> > +++ b/hw/vfio/common.c
> > @@ -968,6 +968,7 @@ static int vfio_connect_container(VFIOGroup *group, AddressSpace *as,
> > if (!ioctl(group->fd, VFIO_GROUP_SET_CONTAINER, &container->fd)) {
> > group->container = container;
> > QLIST_INSERT_HEAD(&container->group_list, group, container_next);
> > + vfio_kvm_device_add_group(group);
> > return 0;
> > }
> > }
> >
> >
next prev parent reply other threads:[~2017-12-06 3:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 21:09 [Qemu-devel] [PATCH for-2.11] vfio: Fix vfio-kvm group registration Alex Williamson
2017-12-06 1:02 ` Alexey Kardashevskiy
2017-12-06 1:30 ` Alex Williamson
2017-12-06 7:20 ` Peter Xu
2017-12-07 0:16 ` Alexey Kardashevskiy
2018-01-18 9:29 ` Alexey Kardashevskiy
2018-01-18 22:15 ` Alex Williamson
2018-01-19 0:35 ` Alexey Kardashevskiy
2017-12-06 2:44 ` Liu, Yi L
2017-12-06 3:12 ` Alex Williamson [this message]
2017-12-06 4:31 ` Liu, Yi L
2017-12-06 8:14 ` Auger Eric
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=20171205201258.6111c71c@t450s.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=eric.auger@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yi.l.liu@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;
as well as URLs for NNTP newsgroup(s).