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, 24 Oct 2023 08:18:52 +0200 [thread overview]
Message-ID: <20231024061852.7BzoCFwW@linutronix.de> (raw)
In-Reply-To: <ZTah9NOMbZkf6dfL@xhacker>
On 2023-10-24 00:40:20 [+0800], Jisheng Zhang wrote:
> Hi Thomas, Sebastian
>
> could you please review? Any comments are appreciated. or do you want a
> rebase on linux-6.5.y-rt?
Please resend on top of latest v6.6-RT. Lazy preempt is gone so only
PREEMPT_RT config switch remains from your three patch series. If you
have generic-entry then you could use the new PREEMPT_AUTO.
Are there any reports of this booting without warnings with LOCKDEP and
CONFIG_DEBUG_ATOMIC_SLEEP enabled? I remember there was something
earlier.
> 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-24 6:19 UTC|newest]
Thread overview: 9+ 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 ` [PATCH RT 1/3] asm-generic/preempt: also check preempt_lazy_count for should_resched() etc Jisheng Zhang
2023-05-10 16:24 ` [PATCH RT 2/3] riscv: add lazy preempt support Jisheng Zhang
2023-05-10 16:24 ` [PATCH RT 3/3] riscv: Allow to enable RT Jisheng Zhang
2023-10-23 16:33 ` [PATCH RT 0/3] riscv: add PREEMPT_RT support Schaffner, Tobias
2023-10-23 16:40 ` Jisheng Zhang
2023-10-24 6:18 ` Sebastian Andrzej Siewior [this message]
2023-10-31 14:43 ` Jisheng Zhang
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=20231024061852.7BzoCFwW@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).