From: Yang Shi <yang@os.amperecomputing.com>
To: "Ryan Roberts" <ryan.roberts@arm.com>,
"Mikołaj Lenczewski" <miko.lenczewski@arm.com>,
suzuki.poulose@arm.com, catalin.marinas@arm.com, will@kernel.org,
joro@8bytes.org, jean-philippe@linaro.org, mark.rutland@arm.com,
joey.gouly@arm.com, oliver.upton@linux.dev, james.morse@arm.com,
broonie@kernel.org, maz@kernel.org, david@redhat.com,
akpm@linux-foundation.org, jgg@ziepe.ca, nicolinc@nvidia.com,
mshavit@google.com, jsnitsel@redhat.com, smostafa@google.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [PATCH v2 4/4] iommu/arm: Add BBM Level 2 smmu feature
Date: Mon, 3 Mar 2025 11:56:33 -0800 [thread overview]
Message-ID: <2f46a07a-20c3-4a7a-8174-99631cfbeade@os.amperecomputing.com> (raw)
In-Reply-To: <43732270-8fd0-4a18-abec-096e383a6a4d@arm.com>
On 3/3/25 2:17 AM, Ryan Roberts wrote:
> On 01/03/2025 01:32, Yang Shi wrote:
>>
>>
>> On 2/28/25 10:24 AM, Mikołaj Lenczewski wrote:
>>> For supporting BBM Level 2 for userspace mappings, we want to ensure
>>> that the smmu also supports its own version of BBM Level 2. Luckily, the
>>> smmu spec (IHI 0070G 3.21.1.3) is stricter than the aarch64 spec (DDI
>>> 0487K.a D8.16.2), so already guarantees that no aborts are raised when
>>> BBM level 2 is claimed.
>>>
>>> Add the feature and testing for it under arm_smmu_sva_supported().
>>>
>>> Signed-off-by: Mikołaj Lenczewski <miko.lenczewski@arm.com>
>>> ---
>>> arch/arm64/kernel/cpufeature.c | 7 +++----
>>> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c | 3 +++
>>> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 3 +++
>>> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 4 ++++
>>> 4 files changed, 13 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
>>> index 63f6d356dc77..1022c63f81b2 100644
>>> --- a/arch/arm64/kernel/cpufeature.c
>>> +++ b/arch/arm64/kernel/cpufeature.c
>>> @@ -2223,8 +2223,6 @@ static bool has_bbml2_noabort(const struct
>>> arm64_cpu_capabilities *caps, int sco
>>> if (!cpu_has_bbml2_noabort(__cpu_read_midr(cpu)))
>>> return false;
>>> }
>>> -
>>> - return true;
>>> } else if (scope & SCOPE_LOCAL_CPU) {
>>> /* We are a hot-plugged CPU, so only need to check our MIDR.
>>> * If we have the correct MIDR, but the kernel booted on an
>>> @@ -2232,10 +2230,11 @@ static bool has_bbml2_noabort(const struct
>>> arm64_cpu_capabilities *caps, int sco
>>> * we have an incorrect MIDR, but the kernel booted on a
>>> * sufficient CPU, we will not bring up this CPU.
>>> */
>>> - return cpu_has_bbml2_noabort(read_cpuid_id());
>>> + if (!cpu_has_bbml2_noabort(read_cpuid_id()))
>>> + return false;
>>> }
>>> - return false;
>>> + return has_cpuid_feature(caps, scope);
>> Do we really need this? IIRC, it means the MIDR has to be in the allow list
>> *AND* MMFR2 register has to be set too. AmpereOne doesn't have MMFR2 register set.
> Miko, I think this should have been squashed into patch #1? It doesn't belong in
> this patch.
>
> Yang, we discussed this internally and decided that we thought it was best to
> still require BBML2 being advertised in the feature register. That way if trying
> to use KVM to emulate a CPU that is in the allow list but doesn't really support
> BBML2, we won't try to use it.
>
> But we still end up with the same problem if running on a physical CPU that
> supports BBML2 with conflict aborts, but emulating a CPU in the allow list. So
> given AmpereOne doesn't advertise BBML2 but does support it, I'd be happy to
> remove this check.
Thank you.
Yang
>
> Thanks,
> Ryan
>
>
>> Thanks,
>> Yang
>>
>>> }
>>> #ifdef CONFIG_ARM64_PAN
>>> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c b/drivers/iommu/
>>> arm/arm-smmu-v3/arm-smmu-v3-sva.c
>>> index 9ba596430e7c..6ba182572788 100644
>>> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c
>>> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c
>>> @@ -222,6 +222,9 @@ bool arm_smmu_sva_supported(struct arm_smmu_device *smmu)
>>> feat_mask |= ARM_SMMU_FEAT_VAX;
>>> }
>>> + if (system_supports_bbml2_noabort())
>>> + feat_mask |= ARM_SMMU_FEAT_BBML2;
>>> +
>>> if ((smmu->features & feat_mask) != feat_mask)
>>> return false;
>>> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c b/drivers/iommu/
>>> arm/arm-smmu-v3/arm-smmu-v3.c
>>> index 358072b4e293..dcee0bdec924 100644
>>> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
>>> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
>>> @@ -4406,6 +4406,9 @@ static int arm_smmu_device_hw_probe(struct
>>> arm_smmu_device *smmu)
>>> if (FIELD_GET(IDR3_RIL, reg))
>>> smmu->features |= ARM_SMMU_FEAT_RANGE_INV;
>>> + if (FIELD_GET(IDR3_BBML, reg) == IDR3_BBML2)
>>> + smmu->features |= ARM_SMMU_FEAT_BBML2;
>>> +
>>> /* IDR5 */
>>> reg = readl_relaxed(smmu->base + ARM_SMMU_IDR5);
>>> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h b/drivers/iommu/
>>> arm/arm-smmu-v3/arm-smmu-v3.h
>>> index bd9d7c85576a..85eaf3ab88c2 100644
>>> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
>>> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
>>> @@ -60,6 +60,9 @@ struct arm_smmu_device;
>>> #define ARM_SMMU_IDR3 0xc
>>> #define IDR3_FWB (1 << 8)
>>> #define IDR3_RIL (1 << 10)
>>> +#define IDR3_BBML GENMASK(12, 11)
>>> +#define IDR3_BBML1 (1 << 11)
>>> +#define IDR3_BBML2 (2 << 11)
>>> #define ARM_SMMU_IDR5 0x14
>>> #define IDR5_STALL_MAX GENMASK(31, 16)
>>> @@ -754,6 +757,7 @@ struct arm_smmu_device {
>>> #define ARM_SMMU_FEAT_HA (1 << 21)
>>> #define ARM_SMMU_FEAT_HD (1 << 22)
>>> #define ARM_SMMU_FEAT_S2FWB (1 << 23)
>>> +#define ARM_SMMU_FEAT_BBML2 (1 << 24)
>>> u32 features;
>>> #define ARM_SMMU_OPT_SKIP_PREFETCH (1 << 0)
next prev parent reply other threads:[~2025-03-03 19:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 18:24 [PATCH v2 0/4] Initial BBML2 support for contpte_convert() Mikołaj Lenczewski
2025-02-28 18:24 ` [PATCH v2 1/4] arm64: Add BBM Level 2 cpu feature Mikołaj Lenczewski
2025-02-28 21:16 ` Yang Shi
2025-03-01 1:29 ` Yang Shi
2025-03-01 2:45 ` Yang Shi
2025-03-03 9:40 ` Mikołaj Lenczewski
2025-03-03 9:40 ` Mikołaj Lenczewski
2025-03-03 19:55 ` Yang Shi
2025-02-28 18:24 ` [PATCH v2 2/4] arm64/mm: Delay tlbi in contpte_convert() under BBML2 Mikołaj Lenczewski
2025-02-28 18:24 ` [PATCH v2 3/4] arm64/mm: Elide " Mikołaj Lenczewski
2025-03-03 9:17 ` David Hildenbrand
2025-03-03 9:49 ` Mikołaj Lenczewski
2025-03-03 9:57 ` David Hildenbrand
2025-03-03 10:55 ` Mikołaj Lenczewski
2025-03-03 11:42 ` David Hildenbrand
2025-03-03 11:52 ` Mikołaj Lenczewski
2025-02-28 18:24 ` [PATCH v2 4/4] iommu/arm: Add BBM Level 2 smmu feature Mikołaj Lenczewski
2025-02-28 19:32 ` Jason Gunthorpe
2025-03-03 8:49 ` Shameerali Kolothum Thodi
2025-03-03 10:31 ` Mikołaj Lenczewski
2025-03-03 16:52 ` Jason Gunthorpe
2025-03-03 19:03 ` Mikołaj Lenczewski
2025-03-04 14:26 ` Jason Gunthorpe
2025-03-04 16:02 ` Ryan Roberts
2025-03-04 16:19 ` Jason Gunthorpe
2025-03-11 14:37 ` Robin Murphy
2025-03-01 1:32 ` Yang Shi
2025-03-03 10:17 ` Ryan Roberts
2025-03-03 10:32 ` Mikołaj Lenczewski
2025-03-03 19:56 ` Yang Shi [this message]
2025-03-11 10:17 ` Suzuki K Poulose
2025-03-11 10:58 ` Ryan Roberts
2025-03-11 12:16 ` Suzuki K Poulose
2025-03-11 13:20 ` Ryan Roberts
2025-03-03 9:14 ` [PATCH v2 0/4] Initial BBML2 support for contpte_convert() David Hildenbrand
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=2f46a07a-20c3-4a7a-8174-99631cfbeade@os.amperecomputing.com \
--to=yang@os.amperecomputing.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=james.morse@arm.com \
--cc=jean-philippe@linaro.org \
--cc=jgg@ziepe.ca \
--cc=joey.gouly@arm.com \
--cc=joro@8bytes.org \
--cc=jsnitsel@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=miko.lenczewski@arm.com \
--cc=mshavit@google.com \
--cc=nicolinc@nvidia.com \
--cc=oliver.upton@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=smostafa@google.com \
--cc=suzuki.poulose@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