From: Nicolin Chen <nicolinc@nvidia.com>
To: Will Deacon <will@kernel.org>
Cc: zhurui <zhurui3@huawei.com>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Yicong Yang <yangyicong@hisilicon.com>,
Tomas Krcka <krckatom@amazon.de>,
"Jean-Philippe Brucker" <jean-philippe@linaro.org>
Subject: Re: [PATCH v2 1/1] iommu/arm-smmu-v3: Fix error case of range command
Date: Fri, 4 Aug 2023 11:30:03 -0700 [thread overview]
Message-ID: <ZM1DqxXcBT2SOs8/@Asurada-Nvidia> (raw)
In-Reply-To: <20230804165225.GF30679@willie-the-truck>
On Fri, Aug 04, 2023 at 05:52:25PM +0100, Will Deacon wrote:
> On Fri, Aug 04, 2023 at 05:31:20PM +0800, zhurui wrote:
> > When tg != 0 but ttl, scale, num all 0 in a range tlbi command, it
> > is reserved and will cause the CERROR_ILL error. This case means
> > that the size to be invalidated is only one page size, and the
> > range invalidation is meaningless here. So we set tg to 0 in this
> > case to do an non-range invalidation instead.
> > @@ -1930,6 +1927,12 @@ static void __arm_smmu_tlb_inv_range(struct arm_smmu_cmdq_ent *cmd,
> > num = (num_pages >> scale) & CMDQ_TLBI_RANGE_NUM_MAX;
> > cmd->tlbi.num = num - 1;
> >
> > + /* Prevent error caused by one page tlbi with leaf 0 */
> > + if (scale == 0 && num == 1 && cmd->tlbi.leaf == 0)
> > + cmd->tlbi.tg = 0;
>
> This should only be true for the last iteration, right (i.e. when num_pages
> == 1)? In which case, I'd prefer to leave the old code as-is and just add:
>
> /* Single-page leaf invalidation requires a TG field of 0 */
> if (num_pages == 1 && !cmd->tlbi.leaf)
> cmd->tlbi.tg = 0;
Is "!cmd->tlbi.leaf" to be "leaf" or "non-leaf"?
IIUIC, this "num_pages == 1" implies "NUM == 0, SCALE == 0" while
the "!cmd->tlbi.leaf" implies "TTL = 0b00", which in combination
would result in a CERROR_ILL mentioned by the spec?
I feel this could be more clear by just checking the three fields
following the spec...
Thanks
Nicolin
_______________________________________________
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-08-04 18:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 6:21 [PATCH 1/1] Revert "iommu/arm-smmu-v3: Set TTL invalidation hint better" wangwudi
2023-08-01 8:55 ` Will Deacon
2023-08-02 10:52 ` zhurui
2023-08-04 9:31 ` [PATCH v2 1/1] iommu/arm-smmu-v3: Fix error case of range command zhurui
2023-08-04 16:52 ` Will Deacon
2023-08-04 18:30 ` Nicolin Chen [this message]
2023-08-06 5:28 ` zhurui
2023-08-07 19:20 ` Robin Murphy
2023-08-08 16:24 ` Will Deacon
2023-08-08 16:43 ` Robin Murphy
2023-08-09 9:22 ` zhurui
2023-08-09 11:23 ` Will Deacon
2023-08-09 13:48 ` Robin Murphy
2023-08-18 16:19 ` Robin Murphy
2023-08-18 16:21 ` Will Deacon
2023-08-25 8:12 ` zhurui
2023-09-06 5:05 ` Easwar Hariharan
2023-09-06 12:59 ` Robin Murphy
2023-09-07 9:21 ` Will Deacon
2023-08-08 16:12 ` 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=ZM1DqxXcBT2SOs8/@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=krckatom@amazon.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=zhurui3@huawei.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