[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221117122335.GD839309@lothringen>
Date: Thu, 17 Nov 2022 13:23:35 +0100
From: Frederic Weisbecker <frederic@...nel.org>
To: "Leizhen (ThunderTown)" <thunder.leizhen@...wei.com>
Cc: "Paul E . McKenney" <paulmck@...nel.org>,
Neeraj Upadhyay <quic_neeraju@...cinc.com>,
Josh Triplett <josh@...htriplett.org>,
Steven Rostedt <rostedt@...dmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Lai Jiangshan <jiangshanlai@...il.com>,
Joel Fernandes <joel@...lfernandes.org>, rcu@...r.kernel.org,
linux-kernel@...r.kernel.org, Robert Elliott <elliott@....com>
Subject: Re: [PATCH v7 5/6] doc: Document CONFIG_RCU_CPU_STALL_CPUTIME=y
stall information
On Thu, Nov 17, 2022 at 10:03:17AM +0800, Leizhen (ThunderTown) wrote:
> On 2022/11/17 6:55, Frederic Weisbecker wrote:
> > On Fri, Nov 11, 2022 at 09:07:08PM +0800, Zhen Lei wrote:
> > One last question I have. Usually all these informations can be deduced by
> > just looking at the stacktrace that comes along an RCU stall report. So on
> > which kind of situation the stacktrace is not enough?
>
> Interrupt storm.
Now that makes sense :)
Thanks.
>
> >
> > Thanks.
> > .
> >
>
> --
> Regards,
> Zhen Lei
Powered by blists - more mailing lists