[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3632cc5e-f1d4-4780-a233-19bfcfe8af69@kernel.org>
Date: Thu, 18 Jan 2024 11:33:08 +0100
From: Jiri Slaby <jirislaby@...nel.org>
To: Leonardo Bras <leobras@...hat.com>,
John Ogness <john.ogness@...utronix.de>
Cc: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Florian Fainelli <f.fainelli@...il.com>, Tony Lindgren <tony@...mide.com>,
Marcelo Tosatti <mtosatti@...hat.com>, LKML <linux-kernel@...r.kernel.org>,
linux-serial <linux-serial@...r.kernel.org>
Subject: Re: [RESEND RFC PATCH v1 2/2] serial/8250: Avoid getting lock in RT
atomic context
On 18. 01. 24, 10:36, Leonardo Bras wrote:
> I am using mainline (torvalds/linux) kernel, forcing ARCH_SUPPORTS_RT:
>
> diff --git a/arch/Kconfig b/arch/Kconfig
> index 5ca66aad0d08..879c34398cb7 100644
> --- a/arch/Kconfig
> +++ b/arch/Kconfig
> @@ -1195,7 +1195,7 @@ config ARCH_NO_PREEMPT
> bool
>
> config ARCH_SUPPORTS_RT
> - bool
> + def_bool y
>
> Since I was not aware of a PREEMPT_RT-patched tree, I did this so I could
> compile a PREEMPT_RT kernel.
Huh, when exactly did you intend to mention this?
--
js
suse labs
Powered by blists - more mailing lists