From: Petr Mladek <pmladek@suse.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Arnd Bergmann <arnd@arndb.de>,
jkosina@suse.com, pmladek@suse.com
Subject: [PATCH v4 0/4] Cleaning printk stuff in NMI context
Date: Fri, 11 Dec 2015 14:20:48 +0100 [thread overview]
Message-ID: <1449840052-10491-1-git-send-email-pmladek@suse.com> (raw)
Hi Andrew,
this is just a quick respin of the previous version. It changes
the few details as you suggested. Also it fixes the build problem
on ARM as reported by Geert and Arnd.
I rather send the whole patch set because there is the renamed header.
Also the extra blank space affects two patches. I hope that it will
safe you some work. Please, let me know if you would prefer
incremental patches.
Changes against v3:
+ used size_t for "len" and "size"
+ replaced WARN() with pr_err()
+ renamed kernel/printk/printk.h -> internal.h
+ fixed build on ARM (undefined NMI_LOG_BUF_SHIFT)
Changes against v2:
+ fixed compilation problems reported by 0-day build robot
+ MN10300 and Xtensa architectures will get handled separately
+ dropped the patch that printed NMI messages directly when Oops
in progress; it made the solution less reliable
+ made the size of the buffer configurable; use real numbers
instead of PAGE_SIZE
Changes against v1:
+ rebased on top of 4.4-rc2; there the old implementation was
moved to lib/nmi_backtrace.c and used also on arm; I hope that
I got the arm side correctly; I was not able to test on arm :-(
+ defined HAVE_NMI on arm for !CPU_V7M instead of !CPU_V7;
handle_fiq_as_nmi() is called from entry-armv.S that
is compiled when !CPU_V7M
+ defined HAVE_NMI also on mips; it calls nmi_enter() and
seems to have real NMIs (or am I wrong?)
+ serialized backtraces when printing directly
(oops_in_progress)
Petr Mladek (4):
printk/nmi: Generic solution for safe printk in NMI
printk/nmi: Use IRQ work only when ready
printk/nmi: Warn when some message has been lost in NMI context
printk/nmi: Increase the size of NMI buffer and make it configurable
arch/Kconfig | 7 ++
arch/arm/Kconfig | 2 +
arch/arm/kernel/smp.c | 2 +
arch/avr32/Kconfig | 1 +
arch/blackfin/Kconfig | 1 +
arch/cris/Kconfig | 1 +
arch/mips/Kconfig | 1 +
arch/powerpc/Kconfig | 1 +
arch/s390/Kconfig | 1 +
arch/sh/Kconfig | 1 +
arch/sparc/Kconfig | 1 +
arch/tile/Kconfig | 1 +
arch/x86/Kconfig | 1 +
arch/x86/kernel/apic/hw_nmi.c | 1 -
include/linux/hardirq.h | 2 +
include/linux/percpu.h | 3 -
include/linux/printk.h | 12 ++-
init/Kconfig | 27 +++++
init/main.c | 1 +
kernel/printk/Makefile | 1 +
kernel/printk/internal.h | 55 +++++++++++
kernel/printk/nmi.c | 222 ++++++++++++++++++++++++++++++++++++++++++
kernel/printk/printk.c | 29 +++---
lib/nmi_backtrace.c | 89 +----------------
24 files changed, 356 insertions(+), 107 deletions(-)
create mode 100644 kernel/printk/internal.h
create mode 100644 kernel/printk/nmi.c
--
1.8.5.6
next reply other threads:[~2015-12-11 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 13:20 Petr Mladek [this message]
2015-12-11 13:20 ` [PATCH v4 1/4] printk/nmi: Generic solution for safe printk in NMI Petr Mladek
2015-12-11 13:20 ` [PATCH v4 2/4] printk/nmi: Use IRQ work only when ready Petr Mladek
2015-12-11 13:20 ` [PATCH v4 3/4] printk/nmi: Warn when some message has been lost in NMI context Petr Mladek
2015-12-11 13:20 ` [PATCH v4 4/4] printk/nmi: Increase the size of NMI buffer and make it configurable Petr Mladek
2015-12-11 13:31 ` [PATCH v4 0/4] Cleaning printk stuff in NMI context Petr Mladek
2016-01-20 21:17 ` Andrew Morton
2016-01-21 11:30 ` Petr Mladek
2016-02-08 16:38 ` 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=1449840052-10491-1-git-send-email-pmladek@suse.com \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=jkosina@suse.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome