devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: Tomasz Jeznach <tjeznach@rivosinc.com>,
	Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Anup Patel <apatel@ventanamicro.com>,
	devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	Albert Ou <aou@eecs.berkeley.edu>,
	linux@rivosinc.com, linux-kernel@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>,
	Sebastien Boeuf <seb@rivosinc.com>,
	iommu@lists.linux.dev, Palmer Dabbelt <palmer@dabbelt.com>,
	Nick Kossifidis <mick@ics.forth.gr>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-riscv@lists.infradead.org,
	Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH v5 7/7] iommu/riscv: Paging domain support
Date: Thu, 23 May 2024 12:28:10 -0300	[thread overview]
Message-ID: <20240523152810.GL69273@ziepe.ca> (raw)
In-Reply-To: <20240522-b25680db03b547123f1cd59a@orel>

On Wed, May 22, 2024 at 10:07:14AM +0200, Andrew Jones wrote:
> On Tue, May 14, 2024 at 11:16:19AM GMT, Tomasz Jeznach wrote:
> ...
> > +static int riscv_iommu_bond_link(struct riscv_iommu_domain *domain,
> > +				 struct device *dev)
> > +{
> > +	struct riscv_iommu_device *iommu = dev_to_iommu(dev);
> > +	struct riscv_iommu_bond *bond;
> > +	struct list_head *bonds;
> > +
> > +	bond = kzalloc(sizeof(*bond), GFP_KERNEL);
> > +	if (!bond)
> > +		return -ENOMEM;
> > +	bond->dev = dev;
> > +
> > +	/*
> > +	 * List of devices attached to the domain is arranged based on
> > +	 * managed IOMMU device.
> > +	 */
> > +
> > +	spin_lock(&domain->lock);
> > +	list_for_each_rcu(bonds, &domain->bonds)
> > +		if (dev_to_iommu(list_entry(bonds, struct riscv_iommu_bond, list)->dev) == iommu)
> > +			break;
> 
> We should wrap this list_for_each_rcu() in rcu_read_lock() and
> rcu_read_unlock().

Not quite this is the write side, it is holding the spinlock so it
doesn't need RCU. It should just call the normal list_for_each_entry()

Jason

      reply	other threads:[~2024-05-23 15:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 18:16 [PATCH v5 0/7] Linux RISC-V IOMMU Support Tomasz Jeznach
2024-05-14 18:16 ` [PATCH v5 1/7] dt-bindings: iommu: riscv: Add bindings for RISC-V IOMMU Tomasz Jeznach
2024-05-14 18:16 ` [PATCH v5 2/7] iommu/riscv: Add RISC-V IOMMU platform device driver Tomasz Jeznach
2024-05-17  7:22   ` Zong Li
2024-05-17 15:46     ` Tomasz Jeznach
2024-05-17 16:28       ` Anup Patel
2024-05-17 19:41         ` Tomasz Jeznach
2024-05-18  3:51           ` Anup Patel
2024-05-23 16:13             ` Tomasz Jeznach
2024-05-24 15:09               ` Jason Gunthorpe
2024-05-24 16:32               ` Anup Patel
2024-05-14 18:16 ` [PATCH v5 3/7] iommu/riscv: Add RISC-V IOMMU PCIe " Tomasz Jeznach
2024-05-14 18:16 ` [PATCH v5 4/7] iommu/riscv: Enable IOMMU registration and device probe Tomasz Jeznach
2024-05-17  7:19   ` Zong Li
2024-05-14 18:16 ` [PATCH v5 5/7] iommu/riscv: Device directory management Tomasz Jeznach
2024-05-17  7:19   ` Zong Li
2024-05-14 18:16 ` [PATCH v5 6/7] iommu/riscv: Command and fault queue support Tomasz Jeznach
2024-05-17  7:18   ` Zong Li
2024-05-14 18:16 ` [PATCH v5 7/7] iommu/riscv: Paging domain support Tomasz Jeznach
2024-05-17  7:18   ` Zong Li
2024-05-22  8:07   ` Andrew Jones
2024-05-23 15:28     ` Jason Gunthorpe [this message]

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=20240523152810.GL69273@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=ajones@ventanamicro.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=apatel@ventanamicro.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@rivosinc.com \
    --cc=mick@ics.forth.gr \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=seb@rivosinc.com \
    --cc=tjeznach@rivosinc.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).