From: Peter Xu <peterx@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: qemu-devel@nongnu.org, Pei Zhang <pezhang@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Jason Wang <jasowang@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
QEMU Stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] intel_iommu: handle invalid ce for shadow sync
Date: Thu, 13 Sep 2018 16:33:17 +0800 [thread overview]
Message-ID: <20180913083317.GG10763@xz-x1> (raw)
In-Reply-To: <2ad9db94-3d74-2879-e0a5-a0c4369d3a7f@redhat.com>
On Thu, Sep 13, 2018 at 10:16:20AM +0200, Maxime Coquelin wrote:
> Hi Peter,
>
> On 09/13/2018 09:55 AM, Peter Xu wrote:
> > There are two callers for vtd_sync_shadow_page_table_range(), one
> > provided a valid context entry and one not. Move that fetching
> > operation into the caller vtd_sync_shadow_page_table() where we need to
> > fetch the context entry.
> >
> > Meanwhile, we should handle VTD_FR_CONTEXT_ENTRY_P properly when
> > synchronizing shadow page tables. Having invalid context entry there is
> > perfectly valid when we move a device out of an existing domain. When
> > that happens, instead of posting an error we invalidate the whole region.
> >
> > Without this patch, QEMU will crash if we do these steps:
> >
> > (1) start QEMU with VT-d IOMMU and two 10G NICs (ixgbe)
> > (2) bind the NICs with vfio-pci in the guest
> > (3) start testpmd with the NICs applied
> > (4) stop testpmd
> > (5) rebind the NIC back to ixgbe kernel driver
> >
> > The patch should fix it.
> >
> > Reported-by: Pei Zhang<pezhang@redhat.com>
> > Tested-by: Pei Zhang<pezhang@redhat.com>
> > CC: Pei Zhang<pezhang@redhat.com>
> > CC: Alex Williamson<alex.williamson@redhat.com>
> > CC: Jason Wang<jasowang@redhat.com>
> > CC: Maxime Coquelin<maxime.coquelin@redhat.com>
> > CC: Michael S. Tsirkin<mst@redhat.com>
> > CC: QEMU Stable<qemu-stable@nongnu.org>
> > Fixes:https://bugzilla.redhat.com/show_bug.cgi?id=1627272
>
> It seems like a regression as it wasn't reported earlier, isn't it?
> If it is, do you know what is the faulty commit?
I think it should be 63b88968f1 ("intel-iommu: rework the page walk
logic", 2018-05-23). The old code would possibly unmap all (using the
old replay logic) before we introduce the shadow page sync helpers and
I must have overlooked on that point.
>
> > Signed-off-by: Peter Xu<peterx@redhat.com>
> > ---
> > hw/i386/intel_iommu.c | 54 ++++++++++++++++++++++++++-----------------
> > 1 file changed, 33 insertions(+), 21 deletions(-)
>
> Other than that, the patch looks good to me.
> FWIW:
> Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2018-09-13 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 7:55 [Qemu-devel] [PATCH] intel_iommu: handle invalid ce for shadow sync Peter Xu
2018-09-13 8:16 ` Maxime Coquelin
2018-09-13 8:33 ` Peter Xu [this message]
2018-10-01 11:36 ` Auger Eric
2018-10-08 5:59 ` Peter Xu
2018-10-08 3:08 ` Jason Wang
2018-10-08 6:06 ` Peter Xu
2018-10-08 6:33 ` Peter Xu
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=20180913083317.GG10763@xz-x1 \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jasowang@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=pezhang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).