From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: "Mikołaj Lenczewski" <miko.lenczewski@arm.com>,
ryan.roberts@arm.com, yang@os.amperecomputing.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, ardb@kernel.org, mark.rutland@arm.com,
joey.gouly@arm.com, maz@kernel.org, james.morse@arm.com,
broonie@kernel.org, oliver.upton@linux.dev, baohua@kernel.org,
david@redhat.com, ioworker0@gmail.com, jgg@ziepe.ca,
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 v5 1/3] arm64: Add BBM Level 2 cpu feature
Date: Tue, 25 Mar 2025 11:06:37 +0000 [thread overview]
Message-ID: <5e49377e-6a3e-4a48-94c9-db06f13cffe8@arm.com> (raw)
In-Reply-To: <20250325093625.55184-2-miko.lenczewski@arm.com>
On 25/03/2025 09:36, Mikołaj Lenczewski wrote:
> The Break-Before-Make cpu feature supports multiple levels (levels 0-2),
> and this commit adds a dedicated BBML2 cpufeature to test against
> support for, as well as a kernel commandline parameter to optionally
> disable BBML2 altogether.
>
> This is a system feature as we might have a big.LITTLE architecture
> where some cores support BBML2 and some don't, but we want all cores to
> be available and BBM to default to level 0 (as opposed to having cores
> without BBML2 not coming online).
>
> To support BBML2 in as wide a range of contexts as we can, we want not
> only the architectural guarantees that BBML2 makes, but additionally
> want BBML2 to not create TLB conflict aborts. Not causing aborts avoids
> us having to prove that no recursive faults can be induced in any path
> that uses BBML2, allowing its use for arbitrary kernel mappings.
> Support detection of such CPUs.
>
> Signed-off-by: Mikołaj Lenczewski <miko.lenczewski@arm.com>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
next prev parent reply other threads:[~2025-03-25 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 9:36 [PATCH v5 0/3] Initial BBML2 support for contpte_convert() Mikołaj Lenczewski
2025-03-25 9:36 ` [PATCH v5 1/3] arm64: Add BBM Level 2 cpu feature Mikołaj Lenczewski
2025-03-25 11:06 ` Suzuki K Poulose [this message]
2025-04-03 8:15 ` Ryan Roberts
2025-03-25 9:36 ` [PATCH v5 2/3] iommu/arm: Add BBM Level 2 smmu feature Mikołaj Lenczewski
2025-03-25 9:36 ` [PATCH v5 3/3] arm64/mm: Elide tlbi in contpte_convert() under BBML2 Mikołaj Lenczewski
2025-04-01 13:38 ` David Hildenbrand
2025-04-03 8:14 ` Ryan Roberts
2025-04-03 8:28 ` 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=5e49377e-6a3e-4a48-94c9-db06f13cffe8@arm.com \
--to=suzuki.poulose@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--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=ryan.roberts@arm.com \
--cc=smostafa@google.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®