From: Eric Auger <eric.auger@redhat.com>
To: eric.auger.pro@gmail.com, eric.auger@redhat.com,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
peter.maydell@linaro.org, jean-philippe@linaro.org,
peterx@redhat.com, jasowang@redhat.com, pbonzini@redhat.com
Cc: vivek.gautam@arm.com, shameerali.kolothum.thodi@huawei.com
Subject: [PATCH v2 0/7] Some vIOMMU fixes
Date: Thu, 25 Feb 2021 10:14:28 +0100 [thread overview]
Message-ID: <20210225091435.644762-1-eric.auger@redhat.com> (raw)
Hi,
Here is a set of vIOMMU fixes:
SMMUv3:
- top SID computation overflow when handling SMMU_CMD_CFGI_ALL
- internal IOTLB handling (changes related to range invalidation)
- smmu_iotlb_inv_iova with asid = -1
- non power of 2 invalidation range handling.
VIRTIO-IOMMU:
- non power of 2 invalidation range handling.
Best Regards
Eric
v2: https://github.com/eauger/qemu/tree/viommu_fixes_for_6-v2
v1: https://github.com/eauger/qemu/tree/viommu_fixes_for_6
History:
v1 -> v2:
- new:
- dma: Introduce dma_aligned_pow2_mask()
- intel_iommu: Fix mask may be uninitialized in vtd_context_device_invalidate
- hw/arm/smmuv3: Uniformize sid traces
Eric Auger (7):
intel_iommu: Fix mask may be uninitialized in
vtd_context_device_invalidate
dma: Introduce dma_aligned_pow2_mask()
virtio-iommu: Handle non power of 2 range invalidations
hw/arm/smmu-common: Fix smmu_iotlb_inv_iova when asid is not set
hw/arm/smmuv3: Enforce invalidation on a power of two range
hw/arm/smmuv3: Fix SMMU_CMD_CFGI_STE_RANGE handling
hw/arm/smmuv3: Uniformize sid traces
hw/arm/smmu-common.c | 32 +++++++++++++---------
hw/arm/smmu-internal.h | 5 ++++
hw/arm/smmuv3.c | 58 +++++++++++++++++++++++++++-------------
hw/arm/trace-events | 24 ++++++++---------
hw/i386/intel_iommu.c | 32 +++++++---------------
hw/virtio/virtio-iommu.c | 19 ++++++++++---
include/sysemu/dma.h | 3 +++
softmmu/dma-helpers.c | 26 ++++++++++++++++++
8 files changed, 130 insertions(+), 69 deletions(-)
--
2.26.2
next reply other threads:[~2021-02-25 9:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 9:14 Eric Auger [this message]
2021-02-25 9:14 ` [PATCH v2 1/7] intel_iommu: Fix mask may be uninitialized in vtd_context_device_invalidate Eric Auger
2021-02-25 10:08 ` Philippe Mathieu-Daudé
2021-02-25 16:33 ` Auger Eric
2021-02-25 15:41 ` Peter Xu
2021-02-25 9:14 ` [PATCH v2 2/7] dma: Introduce dma_aligned_pow2_mask() Eric Auger
2021-02-25 15:56 ` Peter Xu
2021-03-08 16:34 ` Peter Maydell
2021-02-25 9:14 ` [PATCH v2 3/7] virtio-iommu: Handle non power of 2 range invalidations Eric Auger
2021-02-25 16:01 ` Peter Xu
2021-02-25 9:14 ` [PATCH v2 4/7] hw/arm/smmu-common: Fix smmu_iotlb_inv_iova when asid is not set Eric Auger
2021-03-08 16:37 ` Peter Maydell
2021-03-09 8:37 ` Auger Eric
2021-02-25 9:14 ` [PATCH v2 5/7] hw/arm/smmuv3: Enforce invalidation on a power of two range Eric Auger
2021-03-08 16:44 ` Peter Maydell
2021-02-25 9:14 ` [PATCH v2 6/7] hw/arm/smmuv3: Fix SMMU_CMD_CFGI_STE_RANGE handling Eric Auger
2021-03-08 16:41 ` Peter Maydell
2021-02-25 9:14 ` [PATCH v2 7/7] hw/arm/smmuv3: Uniformize sid traces Eric Auger
2021-02-25 10:11 ` Philippe Mathieu-Daudé
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=20210225091435.644762-1-eric.auger@redhat.com \
--to=eric.auger@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=jasowang@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=vivek.gautam@arm.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).