From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mingcong Bai <jeffbai@aosc.io>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Albert Ou <aou@eecs.berkeley.edu>, Borislav Petkov <bp@alien8.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Clark Williams <williams@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
John Ogness <john.ogness@linutronix.de>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH 0/3] Allow to enable PREEMPT_RT.
Date: Thu, 12 Sep 2024 09:14:03 +0200 [thread overview]
Message-ID: <20240912071403.KMVCGTA2@linutronix.de> (raw)
In-Reply-To: <f9070564-4672-4aee-8e63-c9ca9d985f4b@aosc.io>
On 2024-09-10 10:39:45 [+0800], Mingcong Bai wrote:
> Hi Sebastian,
Hi Mingcong,
> Congratulations, it's been a long time coming!
thank you.
> I'm wondering, for the architectures not included in the enablement this
> time, do we have a readiness checklist/guide for maintainers to refer to?
I don't think there is. The plain PREEMPT should work. Then need to
follow the checklist for forced-threaded interrupts. Generic code such
as GENERIC_ENTRY makes things easier but at least
HAVE_POSIX_CPU_TIMERS_TASK_WORK is needed with kvm enabled if my memory
serves me right. Everything else is part of generic code.
> Thanks in advance.
> Best Regards,
> Mingcong Bai
Sebastian
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2024-09-12 7:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 10:59 [PATCH 0/3] Allow to enable PREEMPT_RT Sebastian Andrzej Siewior
2024-09-06 10:59 ` [PATCH 1/3] x86: " 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-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-10 2:39 ` [PATCH 0/3] " Mingcong Bai
2024-09-12 7:14 ` Sebastian Andrzej Siewior [this message]
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=20240912071403.KMVCGTA2@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=aou@eecs.berkeley.edu \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jeffbai@aosc.io \
--cc=john.ogness@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=williams@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).