From: "tip-bot2 for Sebastian Andrzej Siewior" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
Nam Cao <namcao@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/rt] riscv: Allow to enable PREEMPT_RT.
Date: Mon, 09 Sep 2024 17:27:39 -0000 [thread overview]
Message-ID: <172590286013.2215.4253522884856320667.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20240906111841.562402-4-bigeasy@linutronix.de>
The following commit has been merged into the sched/rt branch of tip:
Commit-ID: 41639286fd0b2538de8cfe3e99db18ed0df520cd
Gitweb: https://git.kernel.org/tip/41639286fd0b2538de8cfe3e99db18ed0df520cd
Author: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
AuthorDate: Fri, 06 Sep 2024 12:59:06 +02:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Mon, 09 Sep 2024 19:24:11 +02:00
riscv: Allow to enable PREEMPT_RT.
It is really time.
riscv has all the required architecture related changes, that have been
identified over time, in order to enable PREEMPT_RT. With the recent
printk changes, the last known road block has been addressed.
Allow to enable PREEMPT_RT on riscv.
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Nam Cao <namcao@linutronix.de> # Visionfive 2
Link: https://lore.kernel.org/all/20240906111841.562402-4-bigeasy@linutronix.de
---
arch/riscv/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index 0f3cd7c..b03f6d2 100644
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@ -64,6 +64,7 @@ config RISCV
select ARCH_SUPPORTS_LTO_CLANG_THIN if LLD_VERSION >= 140000
select ARCH_SUPPORTS_PAGE_TABLE_CHECK if MMU
select ARCH_SUPPORTS_PER_VMA_LOCK if MMU
+ select ARCH_SUPPORTS_RT
select ARCH_SUPPORTS_SHADOW_CALL_STACK if HAVE_SHADOW_CALL_STACK
select ARCH_USE_CMPXCHG_LOCKREF if 64BIT
select ARCH_USE_MEMTEST
next prev parent reply other threads:[~2024-09-09 17:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 10:59 [PATCH 0/3] " Sebastian Andrzej Siewior
2024-09-06 10:59 ` [PATCH 1/3] x86: " Sebastian Andrzej Siewior
2024-09-09 17:27 ` [tip: sched/rt] " tip-bot2 for Sebastian Andrzej Siewior
2024-09-17 9:15 ` tip-bot2 for Sebastian Andrzej Siewior
2024-09-06 10:59 ` [PATCH 2/3] arm64: " Sebastian Andrzej Siewior
2024-09-06 11:30 ` Will Deacon
2024-09-06 14:13 ` Steven Rostedt
2024-09-09 17:27 ` [tip: sched/rt] " tip-bot2 for Sebastian Andrzej Siewior
2024-09-17 9:15 ` tip-bot2 for Sebastian Andrzej Siewior
2024-09-06 10:59 ` [PATCH 3/3] riscv: " Sebastian Andrzej Siewior
2024-09-06 15:13 ` Nam Cao
2024-09-06 18:48 ` Palmer Dabbelt
2024-09-17 10:44 ` Sebastian Andrzej Siewior
2024-10-09 16:47 ` Palmer Dabbelt
2024-10-09 16:44 ` Palmer Dabbelt
2024-10-09 17:41 ` Nam Cao
2024-10-10 8:54 ` John Ogness
2024-10-10 12:21 ` Sebastian Andrzej Siewior
2024-09-09 17:27 ` tip-bot2 for Sebastian Andrzej Siewior [this message]
2024-09-17 9:15 ` [tip: sched/rt] " tip-bot2 for Sebastian Andrzej Siewior
2024-09-10 2:39 ` [PATCH 0/3] " Mingcong Bai
2024-09-12 7:14 ` Sebastian Andrzej Siewior
2024-09-30 5:09 ` Shrikanth Hegde
2024-09-30 10:22 ` 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=172590286013.2215.4253522884856320667.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®