From: Robin Murphy <robin.murphy@arm.com>
To: Zhiyuan Dai <daizhiyuan@phytium.com.cn>,
Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>
Cc: linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iommu/arm-smmu-v3: Restrict MMU-700 errata 2268618 and 2812531 to affected
Date: Fri, 6 Feb 2026 17:36:04 +0000 [thread overview]
Message-ID: <9c15f736-9737-400f-a757-2640d07ba551@arm.com> (raw)
In-Reply-To: <20260206-smmuv3-v2-1-f381a2125392@phytium.com.cn>
On 2026-02-06 8:18 am, Zhiyuan Dai wrote:
> According to SDEN-1786925, Arm errata 2268618 and 2812531 are present in
> r0p0, r0p1, and r1p0, and fixed in r1p1.
>
> Introduce this patch to avoid performance degradation caused by
> restricting features on unaffected revisions.
>
> Signed-off-by: Zhiyuan Dai <daizhiyuan@phytium.com.cn>
> ---
> Changelog:
> - Change the revision threshold from < 0 to < 1 to correctly.
> - Link to v1: https://lore.kernel.org/linux-iommu/3f22f7b8-449c-40d9-b4c8-fff3e520d563@arm.com/raw
> ---
> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> index d16d35c78c06..d5c35be5c858 100644
> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> @@ -4272,11 +4272,13 @@ static void arm_smmu_device_iidr_probe(struct arm_smmu_device *smmu)
> smmu->features &= ~ARM_SMMU_FEAT_NESTING;
> break;
> case IIDR_PRODUCTID_ARM_MMU_700:
> - /* Arm erratum 2812531 */
> - smmu->features &= ~ARM_SMMU_FEAT_BTM;
> - smmu->options |= ARM_SMMU_OPT_CMDQ_FORCE_SYNC;
> - /* Arm errata 2268618, 2812531 */
> - smmu->features &= ~ARM_SMMU_FEAT_NESTING;
> + if (variant <= 1 && revision < 1) {
This still breaks r0p1, and you've not addressed the other point I made...
I've now dug up the old branch where I started my own patch (back in May
2024, yikes!), and gone through the newer errata for MMU-700 plus the
newer MMU S3 and MMU L1 products that have also inherited some of its
bugs - I'll finish writing up a cover letter for that and share it on
Monday.
Thanks,
Robin.
> + /* Arm erratum 2812531 */
> + smmu->features &= ~ARM_SMMU_FEAT_BTM;
> + smmu->options |= ARM_SMMU_OPT_CMDQ_FORCE_SYNC;
> + /* Arm errata 2268618, 2812531 */
> + smmu->features &= ~ARM_SMMU_FEAT_NESTING;
> + }
> break;
> }
> break;
>
> ---
> base-commit: b7ff7151e653aa296ab6c5495b2c1ab7c21eb250
> change-id: 20260206-smmuv3-a88772377c20
>
> Best regards,
prev parent reply other threads:[~2026-02-06 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 8:18 Zhiyuan Dai
2026-02-06 17:36 ` Robin Murphy [this message]
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=9c15f736-9737-400f-a757-2640d07ba551@arm.com \
--to=robin.murphy@arm.com \
--cc=daizhiyuan@phytium.com.cn \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®