From: Will Deacon <will@kernel.org>
To: Mostafa Saleh <smostafa@google.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, robin.murphy@arm.com,
joro@8bytes.org
Subject: Re: [PATCH v2 1/2] iommu/io-pgtable-arm: Fix stage-2 concatenation with 16K
Date: Mon, 9 Dec 2024 23:58:05 +0000 [thread overview]
Message-ID: <20241209235804.GA14069@willie-the-truck> (raw)
In-Reply-To: <20241202140604.422235-2-smostafa@google.com>
On Mon, Dec 02, 2024 at 02:06:03PM +0000, Mostafa Saleh wrote:
> At the moment, io-pgtable-arm uses concatenation only if it is
> possible at level 0, which misses a case where concatenation is
> mandatory at level 1 according to R_SRKBC in Arm spec DDI0487 K.a.
>
> Also, that means concatenation can be used when not mandated,
> contradicting the comment on the code. However, these cases can only
> happen if the SMMUv3 driver is changed to use ias != oas for stage-2.
>
> This patch re-writes the code to use concatenation only if mandatory,
> fixing the missing case for level-1 and granule 16K with PA = 40 bits.
>
> Signed-off-by: Mostafa Saleh <smostafa@google.com>
> ---
> drivers/iommu/io-pgtable-arm.c | 45 +++++++++++++++++++++++++---------
> 1 file changed, 33 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/iommu/io-pgtable-arm.c b/drivers/iommu/io-pgtable-arm.c
> index 6b9bb58a414f..0055876b3527 100644
> --- a/drivers/iommu/io-pgtable-arm.c
> +++ b/drivers/iommu/io-pgtable-arm.c
> @@ -223,6 +223,33 @@ static inline int arm_lpae_max_entries(int i, struct arm_lpae_io_pgtable *data)
> return ptes_per_table - (i & (ptes_per_table - 1));
> }
>
> +/*
> + * Check if concatenated PGDs are mandatory according to Arm DDI0487 (K.a)
> + * 1) R_DXBSH: For 16KB, and 48-bit input size, use level 1 instead of 0.
> + * 2) R_SRKBC: After de-ciphering the table for PA size and valid initial lookup
> + * a) 40 bits PA size with 4K: use level 1 instead of level 0 (2 tables for ias = oas)
> + * b) 40 bits PA size with 16K: use level 2 instead of level 1 (16 tables for ias = oas)
> + * c) 42 bits PA size with 4K: use level 1 instead of level 0 (8 tables for ias = oas)
> + * d) 48 bits PA size with 16K: use level 1 instead of level 0 (2 tables for ias = oas)
> + */
> +static inline bool arm_lpae_concat_mandatory(struct arm_lpae_io_pgtable *data)
> +{
> + unsigned int ias = data->iop.cfg.ias;
> + unsigned int oas = data->iop.cfg.oas;
> +
> + /* Covers 1 and 2.d */
> + if ((ARM_LPAE_GRANULE(data) == SZ_16K) && (data->start_level == 0))
> + return (oas == 48) || (ias = 48);
I'm guessing the second disjunct here should be:
(ias == 48);
I'll make that change when applying...
Will
next prev parent reply other threads:[~2024-12-09 23:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 14:06 [PATCH v2 0/2] Fix missing case for concatenation Mostafa Saleh
2024-12-02 14:06 ` [PATCH v2 1/2] iommu/io-pgtable-arm: Fix stage-2 concatenation with 16K Mostafa Saleh
2024-12-09 23:58 ` Will Deacon [this message]
2024-12-10 9:40 ` Mostafa Saleh
2024-12-02 14:06 ` [PATCH v2 2/2] iommu/io-pgtable-arm: Add coverage for different OAS in selftest Mostafa Saleh
2024-12-10 0:17 ` [PATCH v2 0/2] Fix missing case for concatenation 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=20241209235804.GA14069@willie-the-truck \
--to=will@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=smostafa@google.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