From: Nicolin Chen <nicolinc@nvidia.com>
To: Kiryl Shutsemau <kas@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"Joerg Roedel" <joro@8bytes.org>,
Jason Gunthorpe <jgg@nvidia.com>,
"Pranjal Shrivastava" <praan@google.com>,
Mostafa Saleh <smostafa@google.com>,
"Thierry Reding" <thierry.reding@kernel.org>,
Krishna Reddy <vdumpa@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Breno Leitao <leitao@debian.org>, Kyle McMartin <jkkm@meta.com>,
Usama Arif <usama.arif@linux.dev>, <kernel-team@meta.com>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/2] iommu/arm-smmu-v3: Add a cmdq_max_entries module parameter
Date: Tue, 8 Sep 2026 14:56:20 -0700 [thread overview]
Message-ID: <aqCEhG6NA3Ho5noV@nvidia.com> (raw)
In-Reply-To: <ap_Rktiv5hms9IvH@thinkstation>
On Tue, Sep 08, 2026 at 10:19:44AM +0100, Kiryl Shutsemau wrote:
> On Mon, Sep 07, 2026 at 02:56:26PM -0700, Nicolin Chen wrote:
> > On Mon, Sep 07, 2026 at 10:58:34AM +0100, Kiryl Shutsemau (Meta) wrote:
> >
> > I still think that cmdq_max_n_shift can slightly tidy things here.
> >
> > > +static u32 arm_smmu_queue_max_n_shift(u32 ceiling, u32 ent_sz_shift,
> > > + u32 entries)
> >
> > Here, all three inputs would have been "shifts", instead of two
> > "shifts" and one "number of entries".
> >
> > > +{
> > > + u32 floor = PAGE_SHIFT - ent_sz_shift;
> > > +
> > > + if (!entries)
> > > + return ceiling;
> > > +
> > > + return min(ceiling, max(ilog2(entries), floor));
> >
> > And I see Sashiko keeps complaining against the ilog2 here:
>
> It does build: GCC 15 and clang 21, at -O2 and -Os, without a warning.
>
> But the reason is not obvious.
>
> ilog2() on a runtime u32 returns int, and minmax.h only accepts an int
> against a u32 when __is_nonneg() can prove it non-negative at compile
> time.
>
> __ilog2_u32() is fls(n) - 1, so that proof only exists because the
> if (entries) guard lets the compiler see entries != 0 through the inlined
> fls().
>
> But this is fragile. If a compiler does not get there, or a later change
> that moves the guard, it turns it into a BUILD_BUG_ON.
>
> Rather than a max_t() cast, we can give the shift its type first:
>
> if (entries) {
> new_ceiling = ilog2(entries);
> new_ceiling = max(new_ceiling, floor);
> } else if (is_kdump_kernel()) {
>
> Two u32s, nothing left for the compiler to prove, same result.
>
> If it looks good, I can re-spin v6 with the change.
It looks probably okay.. though I still don't get why you aren't
picking the straightforward "max_n_shift" over "max_entries".
max_n_shift is used by both HW and SW, and it does not have such
converting problem or need min/max, making the code cleaner :-/
Nicolin
next prev parent reply other threads:[~2026-09-08 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 9:58 [PATCH v5 0/2] iommu/arm-smmu-v3: Make the queue depths tunable, and shrink them in a kdump kernel Kiryl Shutsemau (Meta)
2026-09-07 9:58 ` [PATCH v5 1/2] iommu/arm-smmu-v3: Add a cmdq_max_entries module parameter Kiryl Shutsemau (Meta)
2026-09-07 21:56 ` Nicolin Chen
2026-09-08 9:19 ` Kiryl Shutsemau
2026-09-08 21:56 ` Nicolin Chen [this message]
2026-09-09 9:50 ` Kiryl Shutsemau
2026-09-07 9:58 ` [PATCH v5 2/2] iommu/arm-smmu-v3: Default queue depths to one page in a kdump kernel Kiryl Shutsemau (Meta)
2026-09-07 21:57 ` Nicolin Chen
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=aqCEhG6NA3Ho5noV@nvidia.com \
--to=nicolinc@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jkkm@meta.com \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=kas@kernel.org \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=praan@google.com \
--cc=robin.murphy@arm.com \
--cc=smostafa@google.com \
--cc=thierry.reding@kernel.org \
--cc=usama.arif@linux.dev \
--cc=vdumpa@nvidia.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
all inboxes | Powered by JetHome®