From: Ryan Roberts <ryan.roberts@arm.com>
To: "Mikołaj Lenczewski" <miko.lenczewski@arm.com>,
"Yang Shi" <yang@os.amperecomputing.com>
Cc: suzuki.poulose@arm.com, corbet@lwn.net, catalin.marinas@arm.com,
will@kernel.org, jean-philippe@linaro.org, robin.murphy@arm.com,
joro@8bytes.org, akpm@linux-foundation.org, mark.rutland@arm.com,
joey.gouly@arm.com, maz@kernel.org, james.morse@arm.com,
broonie@kernel.org, anshuman.khandual@arm.com,
oliver.upton@linux.dev, ioworker0@gmail.com, baohua@kernel.org,
david@redhat.com, jgg@ziepe.ca,
shameerali.kolothum.thodi@huawei.com, nicolinc@nvidia.com,
mshavit@google.com, jsnitsel@redhat.com, smostafa@google.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev
Subject: Re: [PATCH v3 1/3] arm64: Add BBM Level 2 cpu feature
Date: Thu, 13 Mar 2025 18:17:02 +0000 [thread overview]
Message-ID: <83c04cc2-a170-4d4d-82e3-23aec9749352@arm.com> (raw)
In-Reply-To: <20250313181319.GB40525@mazurka.cambridge.arm.com>
On 13/03/2025 18:13, Mikołaj Lenczewski wrote:
> On Thu, Mar 13, 2025 at 10:21:51AM -0700, Yang Shi wrote:
>> On 3/13/25 3:41 AM, Mikołaj Lenczewski wrote:
>>> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
>>> index fb8752b42ec8..3e4cc917a07e 100644
>>> --- a/Documentation/admin-guide/kernel-parameters.txt
>>> +++ b/Documentation/admin-guide/kernel-parameters.txt
>>> @@ -453,6 +453,9 @@
>>> arm64.no32bit_el0 [ARM64] Unconditionally disable the execution of
>>> 32 bit applications.
>>>
>>> + arm64.nobbml2 [ARM64] Unconditionally disable Break-Before-Make Level
>>> + 2 support
>>
>> Hi Miko,
>>
>> A question about the kernel boot parameter. Can this parameter be used
>> in early boot stage? A quick look at the code shows it should be ok, for
>> example, cpu_has_bti() is called in map_kernel(). But I'd like to double
>> check because my patchset needs to check this parameter in map_mem() to
>> determine whether large block mapping can be used or not.
>>
>> And a nit below.
>
> I will need to double check exactly when the arm64 software overrides
> are finalised, but as long as those values are finalised in / before (?)
> the early boot stage then it should be fine? Will reply again once I
> check and have an answer.
This will work fine. The override is setup in the PI code before start_kernel().
>
>>> +static inline bool bbml2_possible(void)
>>> +{
>>> + return !arm64_test_sw_feature_override(ARM64_SW_FEATURE_OVERRIDE_NOBBML2);
>>> +}
>>
>> Can this be moved to cpufeature.h? My patch will use this, anyway I can
>> do it in my patchset.
I'd prefer to do the moving as part of the series that needs it moved.
Thanks,
Ryan
>>
>> Thanks,
>> Yang
>
> I can do so. In fact, on second thought, I will probably extend this to
> also include the `IS_ENABLED(CONFIG_ARM64_BBML2_NOABORT)` check as well,
> and then move it to cpufeature.h, instead of folding said check into
> has_bbml2_noabort().
>
next prev parent reply other threads:[~2025-03-13 18:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 10:41 [PATCH v3 0/3] Initial BBML2 support for contpte_convert() Mikołaj Lenczewski
2025-03-13 10:41 ` [PATCH v3 1/3] arm64: Add BBM Level 2 cpu feature Mikołaj Lenczewski
2025-03-13 16:13 ` Ryan Roberts
2025-03-13 18:08 ` Mikołaj Lenczewski
2025-03-14 9:26 ` Ryan Roberts
2025-03-13 17:21 ` Yang Shi
2025-03-13 18:13 ` Mikołaj Lenczewski
2025-03-13 18:17 ` Ryan Roberts [this message]
2025-03-13 17:34 ` Marc Zyngier
2025-03-13 18:20 ` Mikołaj Lenczewski
2025-03-13 18:39 ` Marc Zyngier
2025-03-13 18:22 ` Ryan Roberts
2025-03-13 18:36 ` Marc Zyngier
2025-03-14 9:18 ` Ryan Roberts
2025-03-14 10:11 ` Marc Zyngier
2025-03-14 12:33 ` Suzuki K Poulose
2025-03-14 13:12 ` Ryan Roberts
2025-03-13 10:41 ` [PATCH v3 2/3] iommu/arm: Add BBM Level 2 smmu feature Mikołaj Lenczewski
2025-03-13 11:39 ` Robin Murphy
2025-03-13 16:18 ` Ryan Roberts
2025-03-13 10:41 ` [PATCH v3 3/3] arm64/mm: Elide tlbi in contpte_convert() under BBML2 Mikołaj Lenczewski
2025-03-13 16:28 ` Ryan Roberts
2025-03-13 11:22 ` [PATCH v3 0/3] Initial BBML2 support for contpte_convert() Suzuki K Poulose
2025-03-13 11:30 ` Mikołaj Lenczewski
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=83c04cc2-a170-4d4d-82e3-23aec9749352@arm.com \
--to=ryan.roberts@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=baohua@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=ioworker0@gmail.com \
--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-doc@vger.kernel.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=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=smostafa@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.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
all inboxes | Powered by JetHome®