From: "Jörg Rödel" <joro@8bytes.org>
To: fangyu.yu@linux.alibaba.com
Cc: tomasz.jeznach@linux.dev, will@kernel.org, robin.murphy@arm.com,
pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
alex@ghiti.fr, baolu.lu@linux.intel.com, jroedel@suse.de,
zong.li@sifive.com, andrew.jones@oss.qualcomm.com,
anup@brainfault.org, jgg@nvidia.com, jgg@ziepe.ca,
guoren@kernel.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH v2 0/3] iommu/riscv: Fix command queue publishing races
Date: Mon, 7 Sep 2026 14:35:24 +0200 [thread overview]
Message-ID: <ap6veD4V8RGHL9zE@8bytes.org> (raw)
In-Reply-To: <20260901133920.14550-1-fangyu.yu@linux.alibaba.com>
On Tue, Sep 01, 2026 at 09:39:17PM +0800, fangyu.yu@linux.alibaba.com wrote:
> Changes in v2:
> - Avoid reacquiring the command queue lock after waiting for space
> times out.
> - Link to v1:
> https://lore.kernel.org/linux-riscv/20260817142728.61783-1-fangyu.yu@linux.alibaba.com/
>
> Fangyu Yu (3):
> iommu/riscv: Add command queue lock
> iommu/riscv: Serialize command queue publishing
> iommu/riscv: Avoid waiting on failed command enqueue
>
> drivers/iommu/riscv/iommu.c | 117 +++++++++++++++++++++---------------
> drivers/iommu/riscv/iommu.h | 2 +
> 2 files changed, 72 insertions(+), 47 deletions(-)
Queued for -rc, thanks.
prev parent reply other threads:[~2026-09-07 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 13:39 fangyu.yu
2026-09-01 13:39 ` [PATCH v2 1/3] iommu/riscv: Add command queue lock fangyu.yu
2026-09-07 3:52 ` Nutty.Liu
2026-09-01 13:39 ` [PATCH v2 2/3] iommu/riscv: Serialize command queue publishing fangyu.yu
2026-09-01 13:39 ` [PATCH v2 3/3] iommu/riscv: Avoid waiting on failed command enqueue fangyu.yu
2026-09-07 12:35 ` Jörg Rödel [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=ap6veD4V8RGHL9zE@8bytes.org \
--to=joro@8bytes.org \
--cc=alex@ghiti.fr \
--cc=andrew.jones@oss.qualcomm.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=baolu.lu@linux.intel.com \
--cc=fangyu.yu@linux.alibaba.com \
--cc=guoren@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robin.murphy@arm.com \
--cc=tomasz.jeznach@linux.dev \
--cc=will@kernel.org \
--cc=zong.li@sifive.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®