From: sergey.senozhatsky.work@gmail.com (Sergey Senozhatsky)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 5/5] printk/nmi: flush NMI messages on the system panic
Date: Mon, 4 Apr 2016 13:52:00 +0900 [thread overview]
Message-ID: <20160404045200.GE6164@swordfish> (raw)
In-Reply-To: <20160331123657.GN5522@pathway.suse.cz>
Hello,
On (03/31/16 14:36), Petr Mladek wrote:
[..]
> #ifdef CONFIG_PRINTK_NMI
> +#define deferred_console_in_nmi() in_nmi()
> #else
> +#define deferred_console_in_nmi() 0
[..]
> + if (!in_sched && !deferred_console_in_nmi()) {
> lockdep_off();
> /*
> * Try to acquire and then immediately release the console
or use SCHED level for nmi messages instead of defining deferred_console_in_nmi()?
so !in_sched will work for both SCHED and NMI messages.
-ss
prev parent reply other threads:[~2016-04-04 4:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 15:53 [PATCH v4 0/5] Cleaning printk stuff in NMI context Petr Mladek
2016-03-30 15:53 ` [PATCH v4 1/5] printk/nmi: generic solution for safe printk in NMI Petr Mladek
2016-04-04 4:49 ` Sergey Senozhatsky
2016-04-04 9:38 ` Petr Mladek
2016-04-20 13:49 ` Petr Mladek
2016-03-30 15:53 ` [PATCH v4 2/5] printk/nmi: use IRQ work only when ready Petr Mladek
2016-04-04 4:56 ` Sergey Senozhatsky
2016-03-30 15:53 ` [PATCH v4 3/5] printk/nmi: warn when some message has been lost in NMI context Petr Mladek
2016-03-30 15:53 ` [PATCH v4 4/5] printk/nmi: increase the size of NMI buffer and make it configurable Petr Mladek
2016-03-30 15:53 ` [PATCH v4 5/5] printk/nmi: flush NMI messages on the system panic Petr Mladek
2016-03-30 16:33 ` kbuild test robot
2016-03-31 12:36 ` Petr Mladek
2016-04-04 4:52 ` Sergey Senozhatsky [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=20160404045200.GE6164@swordfish \
--to=sergey.senozhatsky.work@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).