From: Wei Huang <wei.huang2@amd.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: ehabkost@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
peterx@redhat.com, pbonzini@redhat.com,
Suravee.Suthikulpanit@amd.com, rth@twiddle.net
Subject: Re: [PATCH V1 2/3] amd-iommu: Sync IOVA-to-GPA translation during page invalidation
Date: Wed, 30 Sep 2020 15:43:26 -0500 [thread overview]
Message-ID: <20200930204326.GA1024738@weilap> (raw)
In-Reply-To: <20200929133414.41982c53@x1.home>
On 09/29 01:34, Alex Williamson wrote:
> On Mon, 28 Sep 2020 15:05:05 -0500
> Wei Huang <wei.huang2@amd.com> wrote:
>
> > Add support to sync the IOVA-to-GPA translation at the time of IOMMU
> > page invalidation. This function is called when two IOMMU commands,
> > AMDVI_CMD_INVAL_AMDVI_PAGES and AMDVI_CMD_INVAL_AMDVI_ALL, are
> > intercepted. Address space notifiers are called accordingly.
> >
> > Co-developed-by: Wei Huang <wei.huang2@amd.com>
> > Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
> > ---
> > hw/i386/amd_iommu.c | 177 ++++++++++++++++++++++++++++++++++++++++++++
> > hw/i386/amd_iommu.h | 10 +++
> > hw/vfio/common.c | 3 +-
> > 3 files changed, 189 insertions(+), 1 deletion(-)
> ...
> > diff --git a/hw/vfio/common.c b/hw/vfio/common.c
> > index 13471ae29436..243216499ce0 100644
> > --- a/hw/vfio/common.c
> > +++ b/hw/vfio/common.c
> > @@ -346,7 +346,8 @@ static int vfio_dma_map(VFIOContainer *container, hwaddr iova,
> > * the VGA ROM space.
> > */
> > if (ioctl(container->fd, VFIO_IOMMU_MAP_DMA, &map) == 0 ||
> > - (errno == EBUSY && vfio_dma_unmap(container, iova, size) == 0 &&
> > + ((errno == EEXIST || errno == EBUSY) &&
> > + vfio_dma_unmap(container, iova, size) == 0 &&
> > ioctl(container->fd, VFIO_IOMMU_MAP_DMA, &map) == 0)) {
> > return 0;
> > }
>
>
> This seems like it should be a separate patch. AFAICT the commit log
> doesn't even hint at why this change is necessary. I think the -EBUSY
> error pre-dates vIOMMU as well. Responding the same for an -EEXIST
> almost suggests a coherency issue between QEMU and the kernel, or a
> direct mapping replacement without an invalidation, which doesn't seem
> to be what this patch is implementing. Thanks,
I went back to check it. Removing this checking code (original code) didn't
trigger any issues with Intel 10G passthru NIC. I think this was from the
residual debugging code when we started to implement it. Sorry for the
confusion. I will remove this code in V2 with more tests.
-Wei
>
> Alex
>
next prev parent reply other threads:[~2020-09-30 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 20:05 [PATCH V1 0/3] Passthru device support under emulated amd-iommu Wei Huang
2020-09-28 20:05 ` [PATCH V1 1/3] amd-iommu: Add address space notifier and replay support Wei Huang
2020-09-28 20:05 ` [PATCH V1 2/3] amd-iommu: Sync IOVA-to-GPA translation during page invalidation Wei Huang
2020-09-29 19:34 ` Alex Williamson
2020-09-30 20:43 ` Wei Huang [this message]
2020-09-28 20:05 ` [PATCH V1 3/3] amd-iommu: Fix amdvi_mmio_trace() to differentiate MMIO R/W Wei Huang
2020-09-29 2:08 ` [PATCH V1 0/3] Passthru device support under emulated amd-iommu no-reply
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=20200930204326.GA1024738@weilap \
--to=wei.huang2@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=alex.williamson@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).