mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/rt] x86: Allow to enable PREEMPT_RT.
Date: Tue, 17 Sep 2024 09:15:44 -0000	[thread overview]
Message-ID: <172656454487.2215.2022637587652544393.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20240906111841.562402-2-bigeasy@linutronix.de>

The following commit has been merged into the sched/rt branch of tip:

Commit-ID:     d2d6422f8bd17c6bb205133e290625a564194496
Gitweb:        https://git.kernel.org/tip/d2d6422f8bd17c6bb205133e290625a564194496
Author:        Sebastian Andrzej Siewior <bigeasy@linutronix.de>
AuthorDate:    Fri, 06 Sep 2024 12:59:04 +02:00
Committer:     Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Tue, 17 Sep 2024 11:05:53 +02:00

x86: Allow to enable PREEMPT_RT.

It is really time.

x86 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 x86.

Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/all/20240906111841.562402-2-bigeasy@linutronix.de

---
 arch/x86/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 6f1c31f..865573b 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -122,6 +122,7 @@ config X86
 	select ARCH_USES_CFI_TRAPS		if X86_64 && CFI_CLANG
 	select ARCH_SUPPORTS_LTO_CLANG
 	select ARCH_SUPPORTS_LTO_CLANG_THIN
+	select ARCH_SUPPORTS_RT
 	select ARCH_USE_BUILTIN_BSWAP
 	select ARCH_USE_CMPXCHG_LOCKREF		if X86_CMPXCHG64
 	select ARCH_USE_MEMTEST

  parent reply	other threads:[~2024-09-17  9:15 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 [this message]
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: sched/rt] " tip-bot2 for Sebastian Andrzej Siewior
2024-09-17  9:15   ` 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=172656454487.2215.2022637587652544393.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=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®