mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, Juri Lelli <juri.lelli@redhat.com>
Subject: [PATCH printk 0/1] alternate fix for nbcon_cpu_emergency_flush()
Date: Fri, 19 Jul 2024 15:54:17 +0206	[thread overview]
Message-ID: <20240719134818.3311665-1-john.ogness@linutronix.de> (raw)

Hi Petr,

Currently in linux-next we have commit b955f0eead54 ("printk: nbcon:
Fix nbcon_cpu_emergency_flush() when preemptible"). But as you
pointed out [0], there is no need to disable preemption at all if
we only need to know if the current CPU is in emergency state.

Here is an alternative patch that correctly addresses the issue by
avoiding the migration checks.

Since the previous patch is not yet mainline, perhaps you want to
use this one instead in order to avoid a revert. Up to you.

John Ogness

[0] https://lore.kernel.org/lkml/Zn7b8g1HtuTIAwyi@pathway.suse.cz

John Ogness (1):
  printk: nbcon: do not require migration disabled for
    nbcon_get_cpu_emergency_nesting()

 kernel/printk/nbcon.c | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)


base-commit: c51cf7315db1392af58b909d1004133f6dbf0bf6
-- 
2.39.2


             reply	other threads:[~2024-07-19 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 13:48 John Ogness [this message]
2024-07-19 13:48 ` [PATCH printk 1/1] printk: nbcon: do not require migration disabled for nbcon_get_cpu_emergency_nesting() John Ogness
2024-07-22 13:58   ` Petr Mladek
2024-07-22 14:47 ` [PATCH printk 0/1] alternate fix for nbcon_cpu_emergency_flush() Petr Mladek

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=20240719134818.3311665-1-john.ogness@linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=tglx@linutronix.de \
    /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®