[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240912071403.KMVCGTA2@linutronix.de>
Date: Thu, 12 Sep 2024 09:14:03 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Mingcong Bai <jeffbai@...c.io>
Cc: Thomas Gleixner <tglx@...utronix.de>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, Albert Ou <aou@...s.berkeley.edu>,
Borislav Petkov <bp@...en8.de>,
Catalin Marinas <catalin.marinas@....com>,
Clark Williams <williams@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>,
John Ogness <john.ogness@...utronix.de>,
Palmer Dabbelt <palmer@...belt.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>, Will Deacon <will@...nel.org>
Subject: Re: [PATCH 0/3] Allow to enable PREEMPT_RT.
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
Powered by blists - more mailing lists