From: "Paul E. McKenney" <paulmck@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: iommu@lists.linux.dev, 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
Subject: Re: amd iommu: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 0-.... } 8 jiffies s: 113 root: 0x1/.
Date: Thu, 4 Dec 2025 12:42:52 -0800 [thread overview]
Message-ID: <d90a3959-eacd-495e-99cd-836d07955912@paulmck-laptop> (raw)
In-Reply-To: <20251204144505.GCaTGecavu-E56OR8V@fat_crate.local>
On Thu, Dec 04, 2025 at 03:45:05PM +0100, Borislav Petkov wrote:
> On Wed, Dec 03, 2025 at 09:16:37AM -0800, Paul E. McKenney wrote:
> > Or to some value that works for you. But if you are not looking to be
> > an expedited RCU CPU stall-warning pioneer, yes, setting it to zero is
> > a good approach.
> >
> > If you would like to be a more sane pioneer, setting it to (say) 11000
> > (or 11 seconds) could be appropriate. But what fun is sanity? ;-)
>
> Oh, I have a lot of excitement even without RCU experiments. :-P
;-) ;-) ;-)
> But if you need me to try things, lemme know.
>
> For now I've simply reset the values as to what defconfig sets them to:
>
> CONFIG_RCU_CPU_STALL_TIMEOUT=21
> CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=0
Sounds good, and thank you!
Thanx, Paul
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2025-12-04 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 14:32 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 [this message]
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
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=d90a3959-eacd-495e-99cd-836d07955912@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=bp@alien8.de \
--cc=iommu@lists.linux.dev \
--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
all inboxes | Powered by JetHome®