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, peterx@redhat.com
Cc: jean-philippe@linaro.org, robh@kernel.org, robin.murphy@arm.com,
mst@redhat.com, zhangfei.gao@foxmail.com,
shameerali.kolothum.thodi@huawei.com, will@kernel.org
Subject: [PATCH v2 9/9] hw/arm/smmuv3: Advertise SMMUv3.2 range invalidation
Date: Thu, 2 Jul 2020 17:26:59 +0200 [thread overview]
Message-ID: <20200702152659.8522-10-eric.auger@redhat.com> (raw)
In-Reply-To: <20200702152659.8522-1-eric.auger@redhat.com>
Expose the RIL bit so that the guest driver uses range
invalidation.
Signed-off-by: Eric Auger <eric.auger@redhat.com>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
---
hw/arm/smmuv3-internal.h | 1 +
hw/arm/smmuv3.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/hw/arm/smmuv3-internal.h b/hw/arm/smmuv3-internal.h
index 5babf72f7d..4e7ec252ed 100644
--- a/hw/arm/smmuv3-internal.h
+++ b/hw/arm/smmuv3-internal.h
@@ -54,6 +54,7 @@ REG32(IDR1, 0x4)
REG32(IDR2, 0x8)
REG32(IDR3, 0xc)
+ FIELD(IDR3, RIL, 10, 1);
REG32(IDR4, 0x10)
REG32(IDR5, 0x14)
FIELD(IDR5, OAS, 0, 3);
diff --git a/hw/arm/smmuv3.c b/hw/arm/smmuv3.c
index 89ab11fc36..add4ba4543 100644
--- a/hw/arm/smmuv3.c
+++ b/hw/arm/smmuv3.c
@@ -254,6 +254,8 @@ static void smmuv3_init_regs(SMMUv3State *s)
s->idr[1] = FIELD_DP32(s->idr[1], IDR1, EVENTQS, SMMU_EVENTQS);
s->idr[1] = FIELD_DP32(s->idr[1], IDR1, CMDQS, SMMU_CMDQS);
+ s->idr[3] = FIELD_DP32(s->idr[3], IDR3, RIL, 1);
+
/* 4K and 64K granule support */
s->idr[5] = FIELD_DP32(s->idr[5], IDR5, GRAN4K, 1);
s->idr[5] = FIELD_DP32(s->idr[5], IDR5, GRAN64K, 1);
--
2.21.3
next prev parent reply other threads:[~2020-07-02 15:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 15:26 [PATCH v2 0/9] SMMUv3.2 Range-based TLB Invalidation Support Eric Auger
2020-07-02 15:26 ` [PATCH v2 1/9] hw/arm/smmu-common: Factorize some code in smmu_ptw_64() Eric Auger
2020-07-06 13:11 ` Peter Maydell
2020-07-02 15:26 ` [PATCH v2 2/9] hw/arm/smmu-common: Add IOTLB helpers Eric Auger
2020-07-02 15:26 ` [PATCH v2 3/9] hw/arm/smmu: Introduce smmu_get_iotlb_key() Eric Auger
2020-07-06 13:13 ` Peter Maydell
2020-07-02 15:26 ` [PATCH v2 4/9] hw/arm/smmu: Simplify the IOTLB key format Eric Auger
2020-07-06 13:26 ` Peter Maydell
2020-07-06 14:00 ` Auger Eric
2020-07-02 15:26 ` [PATCH v2 5/9] hw/arm/smmu: Introduce SMMUTLBEntry for PTW and IOTLB value Eric Auger
2020-07-02 15:26 ` [PATCH v2 6/9] hw/arm/smmu-common: Manage IOTLB block entries Eric Auger
2020-07-07 15:04 ` Peter Maydell
2020-07-02 15:26 ` [PATCH v2 7/9] hw/arm/smmuv3: Introduce smmuv3_s1_range_inval() helper Eric Auger
2020-07-02 15:26 ` [PATCH v2 8/9] hw/arm/smmuv3: Get prepared for range invalidation Eric Auger
2020-07-02 15:26 ` Eric Auger [this message]
2020-07-06 16:18 ` [PATCH v2 9/9] hw/arm/smmuv3: Advertise SMMUv3.2 " Robin Murphy
2020-07-06 16:48 ` Auger Eric
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=20200702152659.8522-10-eric.auger@redhat.com \
--to=eric.auger@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=jean-philippe@linaro.org \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=will@kernel.org \
--cc=zhangfei.gao@foxmail.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).