From: Arun Iyengar via B4 Relay <devnull+aiyengar1990.gmail.com@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@collabora.com>,
"Joerg Roedel (AMD)" <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Arun Iyengar <aiyengar1990@gmail.com>
Subject: [PATCH 0/2] iommu/vsi: Fix the runtime PM of the IOMMU
Date: Fri, 13 Nov 2026 20:04:35 +0000 [thread overview]
Message-ID: <20261113-vsi-iommu-pm-ref-v1-0-fd917eebdf18@gmail.com> (raw)
Patch 1 lets the IOMMU suspend again: a failed pm_runtime_get() in the
TLB flush leaked a usage count. Patch 2 stops the interrupt handler
from resuming the IOMMU in hard IRQ context.
Tested on RK3588S (Orange Pi 5), v7.3-based kernel that also has
hantro-robust v3 [1] and the vsi-iommu suspend patch I will send next:
without patch 1 the AV1 IOMMU stayed active after decoding. With both
it is runtime suspended with usage count 0 after AV1 fluster (203/242,
unchanged), 20 AV1 decoder unbind/bind cycles and 3 s2idle cycles. No
IOMMU fault occurred, so patch 2's handler path did not run.
No conflict with patch 10 of [1], which touches the probe.
Developed with Claude (Anthropic), which wrote the code and the commit
messages. I reviewed every change.
[1] https://lore.kernel.org/r/20261113-hantro-robust-v3-0-82383c722ad2@gmail.com
Signed-off-by: Arun Iyengar <aiyengar1990@gmail.com>
---
Arun Iyengar (2):
iommu/vsi: Don't leak a runtime PM reference in the TLB flush
iommu/vsi: Don't resume the IOMMU in its interrupt handler
drivers/iommu/vsi-iommu.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
---
base-commit: 2cf4be57b301ed2d7af82e70cff5dfd96894d8de
change-id: 20261113-vsi-iommu-pm-ref-22c83a5473be
Best regards,
--
Arun Iyengar <aiyengar1990@gmail.com>
next reply other threads:[~2026-11-13 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 20:04 Arun Iyengar via B4 Relay [this message]
2026-11-13 20:04 ` [PATCH 1/2] iommu/vsi: Don't leak a runtime PM reference in the TLB flush Arun Iyengar via B4 Relay
2026-11-13 20:04 ` [PATCH 2/2] iommu/vsi: Don't resume the IOMMU in its interrupt handler Arun Iyengar via B4 Relay
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=20261113-vsi-iommu-pm-ref-v1-0-fd917eebdf18@gmail.com \
--to=devnull+aiyengar1990.gmail.com@kernel.org \
--cc=aiyengar1990@gmail.com \
--cc=benjamin.gaignard@collabora.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®