From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: "Schaffner, Tobias" <tobias.schaffner@siemens.com>,
Thomas Gleixner <tglx@linutronix.de>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"minda.chen@starfivetech.com" <minda.chen@starfivetech.com>
Subject: Re: [PATCH RT 0/3] riscv: add PREEMPT_RT support
Date: Tue, 31 Oct 2023 16:34:27 +0100 [thread overview]
Message-ID: <20231031153427.goCGGJRm@linutronix.de> (raw)
In-Reply-To: <ZUESqBTSS/s47qM/@xhacker>
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
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: "Schaffner, Tobias" <tobias.schaffner@siemens.com>,
Thomas Gleixner <tglx@linutronix.de>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Arnd Bergmann <arnd@arndb.de>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"minda.chen@starfivetech.com" <minda.chen@starfivetech.com>
Subject: Re: [PATCH RT 0/3] riscv: add PREEMPT_RT support
Date: Tue, 31 Oct 2023 16:34:27 +0100 [thread overview]
Message-ID: <20231031153427.goCGGJRm@linutronix.de> (raw)
In-Reply-To: <ZUESqBTSS/s47qM/@xhacker>
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
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-10-31 15:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 16:24 [PATCH RT 0/3] riscv: add PREEMPT_RT support Jisheng Zhang
2023-05-10 16:24 ` Jisheng Zhang
2023-05-10 16:24 ` [PATCH RT 1/3] asm-generic/preempt: also check preempt_lazy_count for should_resched() etc Jisheng Zhang
2023-05-10 16:24 ` Jisheng Zhang
2023-05-10 16:24 ` [PATCH RT 2/3] riscv: add lazy preempt support Jisheng Zhang
2023-05-10 16:24 ` Jisheng Zhang
2023-05-10 16:24 ` [PATCH RT 3/3] riscv: Allow to enable RT Jisheng Zhang
2023-05-10 16:24 ` Jisheng Zhang
2023-10-23 16:33 ` [PATCH RT 0/3] riscv: add PREEMPT_RT support Schaffner, Tobias
2023-10-23 16:33 ` Schaffner, Tobias
2023-10-23 16:40 ` Jisheng Zhang
2023-10-23 16:40 ` Jisheng Zhang
2023-10-24 6:18 ` Sebastian Andrzej Siewior
2023-10-24 6:18 ` Sebastian Andrzej Siewior
2023-10-31 14:43 ` Jisheng Zhang
2023-10-31 14:43 ` Jisheng Zhang
2023-10-31 15:34 ` Sebastian Andrzej Siewior [this message]
2023-10-31 15:34 ` Sebastian Andrzej Siewior
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=20231031153427.goCGGJRm@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=jszhang@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=minda.chen@starfivetech.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=tglx@linutronix.de \
--cc=tobias.schaffner@siemens.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.