From: Auger Eric <eric.auger@redhat.com>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
QEMU Stable <qemu-stable@nongnu.org>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Pei Zhang <pezhang@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] intel_iommu: handle invalid ce for shadow sync
Date: Mon, 1 Oct 2018 13:36:50 +0200 [thread overview]
Message-ID: <8e8f2a55-7ed0-eee7-a68c-85dde8494fa8@redhat.com> (raw)
In-Reply-To: <20180913075517.11140-1-peterx@redhat.com>
Hi Peter,
On 9/13/18 9: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
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
> hw/i386/intel_iommu.c | 54 ++++++++++++++++++++++++++-----------------
> 1 file changed, 33 insertions(+), 21 deletions(-)
>
> diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> index 3dfada19a6..2509520d6f 100644
> --- a/hw/i386/intel_iommu.c
> +++ b/hw/i386/intel_iommu.c
> @@ -37,6 +37,8 @@
> #include "kvm_i386.h"
> #include "trace.h"
>
> +static void vtd_address_space_unmap(VTDAddressSpace *as, IOMMUNotifier *n);
> +
> static void vtd_define_quad(IntelIOMMUState *s, hwaddr addr, uint64_t val,
> uint64_t wmask, uint64_t w1cmask)
> {
Comment above is outdated:
/* If context entry is NULL, we'll try to fetch it on our own. */
> @@ -1047,39 +1049,49 @@ static int vtd_sync_shadow_page_table_range(VTDAddressSpace *vtd_as,
> .notify_unmap = true,
> .aw = s->aw_bits,
> .as = vtd_as,
> + .domain_id = VTD_CONTEXT_ENTRY_DID(ce->hi),
> };
> - VTDContextEntry ce_cache;
> +
> + return vtd_page_walk(ce, addr, addr + size, &info);
> +}
Maybe change would gain in clarity if split into 2 patches, code
reorganization and fix on the side.
Thanks
Eric
> +
> +static int vtd_sync_shadow_page_table(VTDAddressSpace *vtd_as)
> +{
> int ret;
> + VTDContextEntry ce;
> + IOMMUNotifier *n;
>
> - if (ce) {
> - /* If the caller provided context entry, use it */
> - ce_cache = *ce;
> - } else {
> - /* If the caller didn't provide ce, try to fetch */
> - ret = vtd_dev_to_context_entry(s, pci_bus_num(vtd_as->bus),
> - vtd_as->devfn, &ce_cache);
> - if (ret) {
> + ret = vtd_dev_to_context_entry(vtd_as->iommu_state,
> + pci_bus_num(vtd_as->bus),
> + vtd_as->devfn, &ce);
> + if (ret) {
> + if (ret == -VTD_FR_CONTEXT_ENTRY_P) {
> + /*
> + * It's a valid scenario to have a context entry that is
> + * not present. For example, when a device is removed
> + * from an existing domain then the context entry will be
> + * zeroed by the guest before it was put into another
> + * domain. When this happens, instead of synchronizing
> + * the shadow pages we should invalidate all existing
> + * mappings and notify the backends.
> + */
> + IOMMU_NOTIFIER_FOREACH(n, &vtd_as->iommu) {
> + vtd_address_space_unmap(vtd_as, n);
> + }
> + } else {
> /*
> * This should not really happen, but in case it happens,
> * we just skip the sync for this time. After all we even
> * don't have the root table pointer!
> */
> error_report_once("%s: invalid context entry for bus 0x%x"
> - " devfn 0x%x",
> - __func__, pci_bus_num(vtd_as->bus),
> - vtd_as->devfn);
> - return 0;
> + " devfn 0x%x", __func__,
> + pci_bus_num(vtd_as->bus), vtd_as->devfn);
> }
> + return 0;
> }
>
> - info.domain_id = VTD_CONTEXT_ENTRY_DID(ce_cache.hi);
> -
> - return vtd_page_walk(&ce_cache, addr, addr + size, &info);
> -}
> -
> -static int vtd_sync_shadow_page_table(VTDAddressSpace *vtd_as)
> -{
> - return vtd_sync_shadow_page_table_range(vtd_as, NULL, 0, UINT64_MAX);
> + return vtd_sync_shadow_page_table_range(vtd_as, &ce, 0, UINT64_MAX);
> }
>
> /*
>
next prev parent reply other threads:[~2018-10-01 11:37 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
2018-10-01 11:36 ` Auger Eric [this message]
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=8e8f2a55-7ed0-eee7-a68c-85dde8494fa8@redhat.com \
--to=eric.auger@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jasowang@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@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).