From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Eric Auger <eric.auger@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Alexander Witte <alexander.witte@baicanada.com>,
Jintack Lim <jintack@cs.columbia.edu>
Subject: Re: [Qemu-devel] [PATCH] intel-iommu: send PSI always when notify_unmap set
Date: Wed, 18 Apr 2018 13:28:22 +0800 [thread overview]
Message-ID: <20180418052822.GA14841@xz-mi> (raw)
In-Reply-To: <20180418045121.14233-1-peterx@redhat.com>
On Wed, Apr 18, 2018 at 12:51:21PM +0800, Peter Xu wrote:
> During IOVA page table walk, there is a special case when:
>
> - notify_unmap is set, meanwhile
> - entry is invalid
>
> In the past, we skip the entry always. This is not correct. We should
> send UNMAP notification to registered notifiers in this case. Otherwise
> some stall pages will still be mapped in the host even if L1 guest
> unmapped them already.
>
> Without this patch, nested device assignment to L2 guests might dump
> some errors like:
>
> qemu-system-x86_64: VFIO_MAP_DMA: -17
> qemu-system-x86_64: vfio_dma_map(0x557305420c30, 0xad000, 0x1000,
> 0x7f89a920d000) = -17 (File exists)
>
> To fix this, we need to apply this patch to L1 QEMU (L2 QEMU is not
> affected by this problem).
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
This should really be 2.12 material, it fixes a real bug, but not sure
whether it's too late already. Michael, what do you think?
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2018-04-18 5:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 4:51 [Qemu-devel] [PATCH] intel-iommu: send PSI always when notify_unmap set Peter Xu
2018-04-18 5:28 ` Peter Xu [this message]
2018-04-18 5:29 ` Liu, Yi L
2018-04-18 6:26 ` Peter Xu
2018-04-20 4:57 ` Jason Wang
2018-04-20 5:11 ` Peter Xu
2018-04-20 8:29 ` Jason Wang
2018-04-20 8:30 ` Jason Wang
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=20180418052822.GA14841@xz-mi \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=alexander.witte@baicanada.com \
--cc=eric.auger@redhat.com \
--cc=jasowang@redhat.com \
--cc=jintack@cs.columbia.edu \
--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).