From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Mikołaj Lenczewski" <miko.lenczewski@arm.com>
Cc: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
"suzuki.poulose@arm.com" <suzuki.poulose@arm.com>,
"yang@os.amperecomputing.com" <yang@os.amperecomputing.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"joro@8bytes.org" <joro@8bytes.org>,
"jean-philippe@linaro.org" <jean-philippe@linaro.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"joey.gouly@arm.com" <joey.gouly@arm.com>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
"james.morse@arm.com" <james.morse@arm.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"maz@kernel.org" <maz@kernel.org>,
"david@redhat.com" <david@redhat.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
"mshavit@google.com" <mshavit@google.com>,
"jsnitsel@redhat.com" <jsnitsel@redhat.com>,
"smostafa@google.com" <smostafa@google.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>
Subject: Re: [PATCH v2 4/4] iommu/arm: Add BBM Level 2 smmu feature
Date: Tue, 4 Mar 2025 10:26:34 -0400 [thread overview]
Message-ID: <20250304142634.GC5011@ziepe.ca> (raw)
In-Reply-To: <20250303190330.GA426248@e133081.arm.com>
On Mon, Mar 03, 2025 at 07:03:42PM +0000, Mikołaj Lenczewski wrote:
> For example, if we use BBML2 for kernel mappings, does that require us
> to repaint all kernel mappings when disabling BBML2 on smmu attach? I
> am not sure, but definitely something to be worked out.
No, it would be a per-mm_struct basis only if we did something like
that
When the SMMU driver puts a SVA on top of the mm_struct it would
disable BBML2 usage only for that mm_struct and it's contained VMAs.
Kernel mappings are never made into a SVA so are not effected.
Userspace only.
Jason
next prev parent reply other threads:[~2025-03-04 14:26 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 [this message]
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
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=20250304142634.GC5011@ziepe.ca \
--to=jgg@ziepe.ca \
--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=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=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