From: Vasant Hegde <vasant.hegde@amd.com>
To: Borislav Petkov <bp@alien8.de>, iommu@lists.linux.dev
Cc: Joerg Roedel <joro@8bytes.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org, Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: amd iommu: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-.... } 8 jiffies s: 113 root: 0x1/.
Date: Thu, 27 Nov 2025 10:45:28 +0530 [thread overview]
Message-ID: <499db877-2587-46cf-96cc-486ec66db3df@amd.com> (raw)
In-Reply-To: <20251126160031.GGaSckH3SHrC8ckPa7@fat_crate.local>
Hi Boris,
On 11/26/2025 9:30 PM, Borislav Petkov wrote:
> + Vasant.
>
> On Wed, Nov 26, 2025 at 03:32:19PM +0100, Borislav Petkov wrote:
>> Hi,
>>
>> this is latest Linus + latest tip/master. Box is Zen3. CCing AMD IOMMU folks
>> because the backtrace points to it.
I have tried tip/master on my Zen3 and I didn't hit this issue. Can you pass
your config file?
We haven't touched that code path recently and generally it should work fine. At
least we shouldn't hit issues under normal condition.
Having said that recently we observed that under really stressed environment we
hit softlock in the culprit code path. We are working on moving wait_on_sem()
out of spinlock.
-Vasant
prev parent reply other threads:[~2025-11-27 5:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 14:32 amd iommu: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-.... } 8 jiffies s: 113 root: 0x1/ Borislav Petkov
2025-11-26 15:26 ` Borislav Petkov
2025-11-28 20:28 ` Paul E. McKenney
2025-12-03 12:44 ` Borislav Petkov
2025-12-03 17:16 ` Paul E. McKenney
2025-12-04 14:45 ` Borislav Petkov
2025-12-04 20:42 ` Paul E. McKenney
2025-12-08 4:57 ` Paul E. McKenney
2025-11-26 16:00 ` Borislav Petkov
2025-11-26 19:50 ` Jason Gunthorpe
2025-11-27 5:15 ` Vasant Hegde [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=499db877-2587-46cf-96cc-486ec66db3df@amd.com \
--to=vasant.hegde@amd.com \
--cc=bp@alien8.de \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.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