From: Jason Gunthorpe <jgg@ziepe.ca>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>
Cc: joro@8bytes.org, will@kernel.org, robin.murphy@arm.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
heiko@sntech.de, nicolas.dufresne@collabora.com,
iommu@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v4 3/5] iommu: Add verisilicon IOMMU driver
Date: Sat, 5 Jul 2025 15:38:26 -0300 [thread overview]
Message-ID: <20250705183826.GN904431@ziepe.ca> (raw)
In-Reply-To: <62cead85-2d50-45f1-8020-7aea77f6833b@collabora.com>
On Sat, Jul 05, 2025 at 12:04:05PM +0200, Benjamin Gaignard wrote:
> I would like to avoid that but maybe a static spinlock can solve that problem ?
I think you can't really (technically) store an iommu pointer in a
domain and not prevent it from being used by other iommus.
Can't the spinlock be in the domain?
Jason
next prev parent reply other threads:[~2025-07-05 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 15:39 [PATCH v4 0/5] Add support for Verisilicon IOMMU used by media codec blocks Benjamin Gaignard
2025-06-23 15:39 ` [PATCH v4 1/5] dt-bindings: vendor-prefixes: Add Verisilicon Benjamin Gaignard
2025-06-23 15:39 ` [PATCH v4 2/5] dt-bindings: iommu: verisilicon: Add binding for VSI IOMMU Benjamin Gaignard
2025-06-23 16:15 ` Conor Dooley
2025-06-23 15:39 ` [PATCH v4 3/5] iommu: Add verisilicon IOMMU driver Benjamin Gaignard
2025-06-24 12:14 ` kernel test robot
2025-06-30 16:13 ` Dan Carpenter
2025-06-30 16:44 ` Benjamin Gaignard
2025-07-04 17:54 ` Jason Gunthorpe
2025-07-05 10:04 ` Benjamin Gaignard
2025-07-05 18:38 ` Jason Gunthorpe [this message]
2025-06-23 15:39 ` [PATCH v4 4/5] arm64: dts: rockchip: Add verisilicon IOMMU node on RK3588 Benjamin Gaignard
2025-06-23 15:39 ` [PATCH v4 5/5] arm64: defconfig: enable Verisilicon IOMMU Benjamin Gaignard
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=20250705183826.GN904431@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=benjamin.gaignard@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nicolas.dufresne@collabora.com \
--cc=robh@kernel.org \
--cc=robin.murphy@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;
as well as URLs for NNTP newsgroup(s).