From: Nicolin Chen <nicolinc@nvidia.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: <will@kernel.org>, <joro@8bytes.org>, <iommu@lists.linux.dev>,
<linux-arm-kernel@lists.infradead.org>,
<jean-philippe@linaro.org>
Subject: Re: [PATCH 2/4] iommu/arm-smmu-v3: Document MMU-700 erratum 2812531
Date: Wed, 10 May 2023 11:31:25 -0700 [thread overview]
Message-ID: <ZFvi/WEksryM0cin@Asurada-Nvidia> (raw)
In-Reply-To: <ZFvec0JGfbaYHie2@Asurada-Nvidia>
On Wed, May 10, 2023 at 11:12:05AM -0700, Nicolin Chen wrote:
> On Wed, May 10, 2023 at 04:38:44PM +0100, Robin Murphy wrote:
>
> > To work around MMU-700 erratum 2812531 we need to ensure that certain
> > sequences of commands cannot be issued without an intervening sync. In
> > practice this falls out of our current command-batching machinery
> > anyway - each batch only contains a single type of invalidation command,
>
> Hmm. This doesn't apply to the user cache invalidation solution
> in my v2. A user cmdq could possibly mix different commands in
> a single batch if the driver isn't aware of such an errata. So,
> I think I'd need some twist when the host has a FORCE_SYNC flag
> in my v3.
Just found that you unset the NESTING feature flag in PATCH-4
for this errata too. So, the solution in my v2 should be safe.
Thanks
Nicolin
next prev parent reply other threads:[~2023-05-10 18:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 15:38 [PATCH 0/4] iommu/arm-smmu-v3: Arm SMMU errata bits Robin Murphy
2023-05-10 15:38 ` [PATCH 1/4] iommu/arm-smmu-v3: Work around MMU-600 erratum 1076982 Robin Murphy
2023-05-10 17:40 ` Nicolin Chen
2023-05-12 19:02 ` Robin Murphy
2023-05-18 0:53 ` Nicolin Chen
2023-05-10 15:38 ` [PATCH 2/4] iommu/arm-smmu-v3: Document MMU-700 erratum 2812531 Robin Murphy
2023-05-10 18:12 ` Nicolin Chen
2023-05-10 18:31 ` Nicolin Chen [this message]
2023-05-12 19:23 ` Robin Murphy
2023-05-15 15:44 ` Nicolin Chen
2023-05-10 15:38 ` [PATCH 3/4] iommu/arm-smmu-v3: Add explicit feature for nesting Robin Murphy
2023-05-10 18:13 ` Nicolin Chen
2023-05-10 15:38 ` [PATCH 4/4] iommu/arm-smmu-v3: Document nesting-related errata Robin Murphy
2023-05-10 18:37 ` Nicolin Chen
2023-06-08 21:36 ` [PATCH 0/4] iommu/arm-smmu-v3: Arm SMMU errata bits Will Deacon
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=ZFvi/WEksryM0cin@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robin.murphy@arm.com \
--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