From: "Mikołaj Lenczewski" <miko.lenczewski@arm.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
yang@os.amperecomputing.com, catalin.marinas@arm.com,
will@kernel.org, joey.gouly@arm.com, broonie@kernel.org,
mark.rutland@arm.com, james.morse@arm.com,
yangyicong@hisilicon.com, anshuman.khandual@arm.com,
maz@kernel.org, liaochang1@huawei.com, akpm@linux-foundation.org,
david@redhat.com, baohua@kernel.org, ioworker0@gmail.com,
oliver.upton@linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/3] arm64: Add BBM Level 2 cpu feature
Date: Thu, 20 Feb 2025 09:33:52 +0000 [thread overview]
Message-ID: <20250220093352.GA11745@mazurka.cambridge.arm.com> (raw)
In-Reply-To: <e0a6308f-5628-4698-95a7-ec1b918358b0@arm.com>
On Wed, Feb 19, 2025 at 04:25:56PM +0000, Robin Murphy wrote:
> > On 19/02/2025 15:39, Robin Murphy wrote:
> >> ...
> >>
> >> If this may be used for splitting/compacting userspace mappings, then similarly
> >> to 6e192214c6c8 ("iommu/arm-smmu-v3: Document SVA interaction with new pagetable
> >> features"), strictly we'll also want a check in arm_smmu_sva_supported() to make
> >> sure that the SMMU is OK with BBML2 behaviour too, and disallow SVA if not. Note
> >> that the corresponding SMMUv3.2-BBML2 feature is already strict about TLB
> >> conflict aborts, so is comparatively nice and straightforward.
>
> Yup, it's really more just a theoretical correctness concern - certainly
> Arm's implementations from MMU-700 onwards do support BBML2, while
> MMU-600 is now sufficiently old that nobody is likely to pair it with
> new BBML-capable CPUs anyway - so it's just to cover the gap that in
> principle there may be 3rd-party implementations which might get confused.
>
> Cheers,
> Robin.
Hi Robin,
Thank you for taking the time to review these patches. I will add the
check in the next patch series.
--
Kind regards,
Mikołaj Lenczewski
next prev parent reply other threads:[~2025-02-20 9:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 14:38 [PATCH v1 0/3] Initial BBML2 support for contpte_convert() Mikołaj Lenczewski
2025-02-19 14:38 ` [PATCH v1 1/3] arm64: Add BBM Level 2 cpu feature Mikołaj Lenczewski
2025-02-19 15:39 ` Robin Murphy
2025-02-19 15:43 ` Ryan Roberts
2025-02-19 16:25 ` Robin Murphy
2025-02-20 9:33 ` Mikołaj Lenczewski [this message]
2025-02-19 23:34 ` Oliver Upton
2025-02-19 23:57 ` Oliver Upton
2025-02-20 9:37 ` Mikołaj Lenczewski
2025-02-20 1:25 ` Yang Shi
2025-02-20 10:34 ` Mikołaj Lenczewski
2025-02-20 20:01 ` Yang Shi
2025-02-19 14:38 ` [PATCH v1 2/3] arm64/mm: Delay tlbi in contpte_convert() under BBML2 Mikołaj Lenczewski
2025-02-19 14:38 ` [PATCH v1 3/3] arm64/mm: Elide " 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=20250220093352.GA11745@mazurka.cambridge.arm.com \
--to=miko.lenczewski@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=david@redhat.com \
--cc=ioworker0@gmail.com \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=liaochang1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=robin.murphy@arm.com \
--cc=ryan.roberts@arm.com \
--cc=will@kernel.org \
--cc=yang@os.amperecomputing.com \
--cc=yangyicong@hisilicon.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®