[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231031153427.goCGGJRm@linutronix.de>
Date: Tue, 31 Oct 2023 16:34:27 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Jisheng Zhang <jszhang@...nel.org>
Cc: "Schaffner, Tobias" <tobias.schaffner@...mens.com>,
Thomas Gleixner <tglx@...utronix.de>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Arnd Bergmann <arnd@...db.de>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"minda.chen@...rfivetech.com" <minda.chen@...rfivetech.com>
Subject: Re: [PATCH RT 0/3] riscv: add PREEMPT_RT support
On 2023-10-31 22:43:52 [+0800], Jisheng Zhang wrote:
> Hi Sebastian,
Hi Jisheng,
> Thank you so much for pointing out PREEMPT_AUTO, I read the discussions
> last weekend, glad to know PREEMPT_AUTO. And riscv has switched to
> generic entry, so it's easy to support PREEMPT_AUTO for riscv. V2 was
> sent out a few mintues ago. Could you please review?
Sure. I have no idea what the upstream status about PREEMPT_AUTO but I
think we want this.
> > Are there any reports of this booting without warnings with LOCKDEP and
> > CONFIG_DEBUG_ATOMIC_SLEEP enabled? I remember there was something
> > earlier.
>
> IIRC, Conor reported the warning and stack trace is ext4 related. But
> I didn't reproduce the warning. And Schaffner also tried the series
> but it seems he didn't see the warning either. So I'm asking for Conor's
> help to retry v2.
oki.
> Thanks
Sebastian
Powered by blists - more mailing lists