All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>
Cc: linux-riscv@lists.infradead.org, tobias.schaffner@siemens.com,
	Arnd Bergmann <arnd@arndb.de>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH RT v2 0/3] riscv: add PREEMPT_RT support
Date: Tue, 31 Oct 2023 22:35:19 +0800	[thread overview]
Message-ID: <20231031143521.441-1-jszhang@kernel.org> (raw)

This series is to add PREEMPT_RT support to riscv. Compared with last
year's try[1], there are two major changes:

1. riscv has been converted to Generic Entry. And RT maintainers has
introduced PREEMPT_AUTO, so its support for riscv as well.

2. three preparation patches(patch1/2/3 in [1]) has been merged in
mainline.

Link: https://lore.kernel.org/linux-riscv/20220831175920.2806-1-jszhang@kernel.org/ [1]

Hi @Conor,

IIRC, you reported warnings with LOCKDEP(and DEBUG_ATOMIC_SLEEP?) with
previous version RT patch, but I tried on c906, c910 platforms and
can't reproduce the warnings. And Schaffner also tried them and
didn't reproduce warnings either. So could you please help try
v6.6-RT + this series again?

Thanks

Since v1:
 - rebase on v6.6-rt
 - support the new PREEMPT_AUTO instead of Lazy preempt

Jisheng Zhang (2):
  riscv: add PREEMPT_AUTO support
  riscv: allow to enable RT

 arch/riscv/Kconfig                   | 2 ++
 arch/riscv/include/asm/thread_info.h | 2 ++
 2 files changed, 4 insertions(+)

-- 
2.40.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2023-10-31 14:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 14:35 Jisheng Zhang [this message]
2023-10-31 14:35 ` [PATCH RT v2 1/2] riscv: add PREEMPT_AUTO support Jisheng Zhang
2023-10-31 14:35 ` [PATCH RT v2 2/2] riscv: allow to enable RT Jisheng Zhang
2023-10-31 15:32 ` [PATCH RT v2 0/3] riscv: add PREEMPT_RT support Sebastian Andrzej Siewior
2023-10-31 15:49   ` Jisheng Zhang
2023-10-31 16:44     ` Sebastian Andrzej Siewior
2023-11-01 11:41       ` Jisheng Zhang
2023-11-02 12:31         ` Conor Dooley
2023-11-02 15:54           ` Sebastian Andrzej Siewior
2023-11-02 17:03             ` Jisheng Zhang
2023-11-02 21:37             ` Palmer Dabbelt
2023-11-03  8:17               ` Sebastian Andrzej Siewior
2023-11-03  8:14             ` Conor Dooley
2023-11-03  8:24               ` Sebastian Andrzej Siewior
2023-11-03 17:19                 ` Evan Green
2023-11-03 17:39                   ` Sebastian Andrzej Siewior
2023-11-03 18:22                     ` Evan Green
2023-11-06  8:53                       ` Sebastian Andrzej Siewior
2023-11-06 16:25                         ` Evan Green
2023-11-06 21:58 ` Palmer Dabbelt
2023-11-10 15:37   ` 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=20231031143521.441-1-jszhang@kernel.org \
    --to=jszhang@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=bigeasy@linutronix.de \
    --cc=conor.dooley@microchip.com \
    --cc=linux-riscv@lists.infradead.org \
    --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.