[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <875y334k6m.ffs@tglx>
Date: Thu, 19 Oct 2023 00:53:05 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: paulmck@...nel.org, Ankur Arora <ankur.a.arora@...cle.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, x86@...nel.org,
akpm@...ux-foundation.org, luto@...nel.org, bp@...en8.de,
dave.hansen@...ux.intel.com, hpa@...or.com, mingo@...hat.com,
juri.lelli@...hat.com, vincent.guittot@...aro.org,
willy@...radead.org, mgorman@...e.de, rostedt@...dmis.org,
jon.grimm@....com, bharata@....com, raghavendra.kt@....com,
boris.ostrovsky@...cle.com, konrad.wilk@...cle.com,
jgross@...e.com, andrew.cooper3@...rix.com,
Frederic Weisbecker <fweisbec@...il.com>, urezki@...il.com
Subject: Re: [PATCH v2 7/9] sched: define TIF_ALLOW_RESCHED
On Wed, Oct 18 2023 at 10:51, Paul E. McKenney wrote:
> On Wed, Oct 18, 2023 at 05:09:46AM -0700, Ankur Arora wrote:
Can you folks please trim your replies. It's annoying to scroll
through hundreds of quoted lines to figure out that nothing is there.
>> This probably allows for more configuration flexibility across archs?
>> Would allow for TREE_RCU=y, for instance. That said, so far I've only
>> been working with PREEMPT_RCU=y.)
>
> Then this is a bug that needs to be fixed. We need a way to make
> RCU readers non-preemptible.
Why?
Powered by blists - more mailing lists