From: Jason Gunthorpe <jgg@ziepe.ca>
To: Mostafa Saleh <smostafa@google.com>
Cc: iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robin.murphy@arm.com,
will@kernel.org, joro@8bytes.org, praan@google.com
Subject: Re: [PATCH v2 1/3] iommu/io-pgtable-arm: Move selftests to a separate file
Date: Wed, 17 Sep 2025 16:38:18 -0300 [thread overview]
Message-ID: <20250917193818.GK1326709@ziepe.ca> (raw)
In-Reply-To: <20250917191143.3847487-2-smostafa@google.com>
On Wed, Sep 17, 2025 at 07:11:38PM +0000, Mostafa Saleh wrote:
> +static void __init arm_lpae_dump_ops(struct io_pgtable_ops *ops)
> +{
> + struct arm_lpae_io_pgtable *data = io_pgtable_ops_to_data(ops);
> + struct io_pgtable_cfg *cfg = &data->iop.cfg;
Can be:
struct io_pgtable_cfg *cfg =
&io_pgtable_ops_to_pgtable(pgtbl_ops)->cfg;
> +
> + pr_err("cfg: pgsize_bitmap 0x%lx, ias %u-bit\n",
> + cfg->pgsize_bitmap, cfg->ias);
> + pr_err("data: %d levels, 0x%zx pgd_size, %u pg_shift, %u bits_per_level, pgd @ %p\n",
> + ARM_LPAE_MAX_LEVELS - data->start_level, ARM_LPAE_PGD_SIZE(data),
> + ilog2(ARM_LPAE_GRANULE(data)), data->bits_per_level, data->pgd);
The entire struct arm_lpae_io_pgtable is exposed to a public header
just for this one print.. Seems undesirable.
Drop the print? Honestly, I prefer this, given the maturity let's not
compromise modularity to print someting nobody will ever read..
Alternatively call a kunit-only exported function to do the print
directly from ops so. smmuv3 has an example how to do that
Either way a precursor patch to adjust it will allow this patch to
avoid publishing most stuff.
> +/*
> + * Calculate the right shift amount to get to the portion describing level l
> + * in a virtual address mapped by the pagetable in d.
> + */
> +#define ARM_LPAE_LVL_SHIFT(l,d) \
> + (((ARM_LPAE_MAX_LEVELS - (l)) * (d)->bits_per_level) + \
> + ilog2(sizeof(arm_lpae_iopte)))
Didn't see this being used?
> +#define ARM_LPAE_GRANULE(d) \
> + (sizeof(arm_lpae_iopte) << (d)->bits_per_level)
Only used by the above print
> +#define ARM_LPAE_PGD_SIZE(d) \
> + (sizeof(arm_lpae_iopte) << (d)->pgd_bits)
Only used by the above print
> +#define ARM_LPAE_PTES_PER_TABLE(d) \
> + (ARM_LPAE_GRANULE(d) >> ilog2(sizeof(arm_lpae_iopte)))
Didn't see this being used?
> +typedef u64 arm_lpae_iopte;
Only used by the defines and the above print.
Jason
next prev parent reply other threads:[~2025-09-17 19:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 19:11 [PATCH v2 0/3] Move io-pgtable-arm selftest to KUnit Mostafa Saleh
2025-09-17 19:11 ` [PATCH v2 1/3] iommu/io-pgtable-arm: Move selftests to a separate file Mostafa Saleh
2025-09-17 19:38 ` Jason Gunthorpe [this message]
2025-09-17 20:20 ` Mostafa Saleh
2025-09-17 21:48 ` Jason Gunthorpe
2025-09-18 11:41 ` Mostafa Saleh
2025-09-17 19:11 ` [PATCH v2 2/3] iommu/io-pgtable-arm-selftests: Modularize the test Mostafa Saleh
2025-09-17 19:39 ` Jason Gunthorpe
2025-09-17 19:11 ` [PATCH v2 3/3] iommu/io-pgtable-arm-selftests: Use KUnit Mostafa Saleh
2025-09-17 19:44 ` Jason Gunthorpe
2025-09-17 20:31 ` Mostafa Saleh
2025-09-17 19:27 ` [PATCH v2 0/3] Move io-pgtable-arm selftest to KUnit Jason Gunthorpe
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=20250917193818.GK1326709@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=praan@google.com \
--cc=robin.murphy@arm.com \
--cc=smostafa@google.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®