From: Jiri Slaby <jirislaby@kernel.org>
To: Leonardo Bras <leobras@redhat.com>,
John Ogness <john.ogness@linutronix.de>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Tony Lindgren" <tony@atomide.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-serial <linux-serial@vger.kernel.org>
Subject: Re: [RESEND RFC PATCH v1 2/2] serial/8250: Avoid getting lock in RT atomic context
Date: Thu, 18 Jan 2024 11:33:08 +0100 [thread overview]
Message-ID: <3632cc5e-f1d4-4780-a233-19bfcfe8af69@kernel.org> (raw)
In-Reply-To: <ZajxMc05uVmK7e60@LeoBras>
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
next prev parent reply other threads:[~2024-01-18 10:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 7:36 [RESEND RFC PATCH v1 0/2] Fix serial console for PREEMPT_RT Leonardo Bras
2024-01-16 7:36 ` [RESEND RFC PATCH v1 1/2] irq/spurious: Reset irqs_unhandled if an irq_thread handles one IRQ request Leonardo Bras
2024-01-17 22:08 ` Thomas Gleixner
2024-01-17 22:46 ` Leonardo Bras
2024-01-18 9:24 ` Leonardo Bras
2024-01-16 7:37 ` [RESEND RFC PATCH v1 2/2] serial/8250: Avoid getting lock in RT atomic context Leonardo Bras
2024-01-16 8:48 ` Ilpo Järvinen
2024-01-16 18:21 ` Leonardo Bras
2024-01-18 9:01 ` John Ogness
2024-01-18 9:36 ` Leonardo Bras
2024-01-18 10:27 ` John Ogness
2024-01-18 17:50 ` Leonardo Bras
2024-01-18 10:33 ` Jiri Slaby [this message]
2024-01-18 17:57 ` Leonardo Bras
2024-01-17 22:44 ` Thomas Gleixner
2024-01-17 23:18 ` Leonardo Bras
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=3632cc5e-f1d4-4780-a233-19bfcfe8af69@kernel.org \
--to=jirislaby@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=john.ogness@linutronix.de \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
/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®