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 1/4] iommu/arm-smmu-v3: Work around MMU-600 erratum 1076982
Date: Wed, 17 May 2023 17:53:19 -0700 [thread overview]
Message-ID: <ZGV2/6487F9S3Blq@Asurada-Nvidia> (raw)
In-Reply-To: <ZFvXF3gKL4WHiBeZ@Asurada-Nvidia>
On Wed, May 10, 2023 at 10:40:42AM -0700, Nicolin Chen wrote:
> On Wed, May 10, 2023 at 04:38:43PM +0100, Robin Murphy wrote:
>
> > MMU-600 versions prior to r1p0 fail to correctly generate a WFE wakeup
> > event when the command queue transitions fom full to non-full. We can
> > easily work around this by simply hiding the SEV capability such that we
> > fall back to polling for space in the queue - since MMU-600 implements
> > MSIs we wouldn't expect to need SEV for sync completion either, so this
> > should have little to no impact.
> >
> > Signed-off-by: Robin Murphy <robin.murphy@arm.com>
>
> Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
It happens that I have a simulation environment where the
IIDR value hits the errata, i.e. the NESTING feature bit
gets canceled by this patch. So,
Tested-by: Nicolin Chen <nicolinc@nvidia.com>
Hopefully we can get this series merged soon.
Thanks!
Nic
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-05-18 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1683731256.git.robin.murphy@arm.com>
[not found] ` <330221cdfd0003cd51b6c04e7ff3566741ad8374.1683731256.git.robin.murphy@arm.com>
[not found] ` <ZFvec0JGfbaYHie2@Asurada-Nvidia>
[not found] ` <ZFvi/WEksryM0cin@Asurada-Nvidia>
[not found] ` <a45be5e3-c605-f93a-f523-1bb1f6150986@arm.com>
2023-05-15 15:44 ` [PATCH 2/4] iommu/arm-smmu-v3: Document MMU-700 erratum 2812531 Nicolin Chen
[not found] ` <08adbe3d01024d8382a478325f73b56851f76e49.1683731256.git.robin.murphy@arm.com>
[not found] ` <ZFvXF3gKL4WHiBeZ@Asurada-Nvidia>
2023-05-18 0:53 ` Nicolin Chen [this message]
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=ZGV2/6487F9S3Blq@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