From: Petr Mladek <pmladek@suse.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 1/4] printk/nmi: generic solution for safe printk in NMI
Date: Fri, 28 Apr 2017 13:44:23 +0000 [thread overview]
Message-ID: <20170428134423.GB3452@pathway.suse.cz> (raw)
In-Reply-To: <20170428090226.qqoe6qbewjeo57kd@hirez.programming.kicks-ass.net>
On Fri 2017-04-28 11:02:26, Peter Zijlstra wrote:
> On Thu, Apr 27, 2017 at 03:38:19PM +0200, Petr Mladek wrote:
> > Also we need to look for alternatives. There is a chance
> > to create crashdump and get the ftrace messages from it.
> > Also this might be scenario when we might need to suggest
> > the early_printk() patchset from Peter Zijlstra.
>
> I'd be happy to repost those. I still carry them in my tree.
You do not need to if they are still the same as
https://lkml.kernel.org/r/20161018170830.405990950@infradead.org
I rather do not promise anything but I would like to look at them
within next few weeks (after the merge window).
Best Regards,
Petr
WARNING: multiple messages have this Message-ID (diff)
From: Petr Mladek <pmladek@suse.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Daniel Thompson <daniel.thompson@linaro.org>,
Jiri Kosina <jkosina@suse.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Chris Metcalf <cmetcalf@ezchip.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
linux-arm-kernel@lists.infradead.org,
adi-buildroot-devel@lists.sourceforge.net,
linux-cris-kernel@axis.com, linux-mips@linux-mips.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-sh@vger.kernel.org, sparclinux@vger.kernel.org,
Jan Kara <jack@suse.cz>, Ralf Baechle <ralf@linux-mips.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH v5 1/4] printk/nmi: generic solution for safe printk in NMI
Date: Fri, 28 Apr 2017 15:44:23 +0200 [thread overview]
Message-ID: <20170428134423.GB3452@pathway.suse.cz> (raw)
In-Reply-To: <20170428090226.qqoe6qbewjeo57kd@hirez.programming.kicks-ass.net>
On Fri 2017-04-28 11:02:26, Peter Zijlstra wrote:
> On Thu, Apr 27, 2017 at 03:38:19PM +0200, Petr Mladek wrote:
> > Also we need to look for alternatives. There is a chance
> > to create crashdump and get the ftrace messages from it.
> > Also this might be scenario when we might need to suggest
> > the early_printk() patchset from Peter Zijlstra.
>
> I'd be happy to repost those. I still carry them in my tree.
You do not need to if they are still the same as
https://lkml.kernel.org/r/20161018170830.405990950@infradead.org
I rather do not promise anything but I would like to look at them
within next few weeks (after the merge window).
Best Regards,
Petr
WARNING: multiple messages have this Message-ID (diff)
From: pmladek@suse.com (Petr Mladek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/4] printk/nmi: generic solution for safe printk in NMI
Date: Fri, 28 Apr 2017 15:44:23 +0200 [thread overview]
Message-ID: <20170428134423.GB3452@pathway.suse.cz> (raw)
In-Reply-To: <20170428090226.qqoe6qbewjeo57kd@hirez.programming.kicks-ass.net>
On Fri 2017-04-28 11:02:26, Peter Zijlstra wrote:
> On Thu, Apr 27, 2017 at 03:38:19PM +0200, Petr Mladek wrote:
> > Also we need to look for alternatives. There is a chance
> > to create crashdump and get the ftrace messages from it.
> > Also this might be scenario when we might need to suggest
> > the early_printk() patchset from Peter Zijlstra.
>
> I'd be happy to repost those. I still carry them in my tree.
You do not need to if they are still the same as
https://lkml.kernel.org/r/20161018170830.405990950 at infradead.org
I rather do not promise anything but I would like to look at them
within next few weeks (after the merge window).
Best Regards,
Petr
next prev parent reply other threads:[~2017-04-28 13:44 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 11:48 [PATCH v5 0/4] Cleaning printk stuff in NMI context Petr Mladek
2016-04-21 11:48 ` Petr Mladek
2016-04-21 11:48 ` Petr Mladek
2016-04-21 11:48 ` [PATCH v5 1/4] printk/nmi: generic solution for safe printk in NMI Petr Mladek
2016-04-21 11:48 ` Petr Mladek
2016-04-21 11:48 ` Petr Mladek
2016-04-27 9:31 ` Russell King - ARM Linux
2016-04-27 9:31 ` Russell King - ARM Linux
2016-04-27 9:31 ` Russell King - ARM Linux
2017-04-19 17:13 ` Steven Rostedt
2017-04-19 17:13 ` Steven Rostedt
2017-04-19 17:13 ` Steven Rostedt
2017-04-19 17:21 ` Peter Zijlstra
2017-04-19 17:21 ` Peter Zijlstra
2017-04-19 17:21 ` Peter Zijlstra
2017-04-20 3:31 ` Sergey Senozhatsky
2017-04-20 3:31 ` Sergey Senozhatsky
2017-04-20 3:31 ` Sergey Senozhatsky
2017-04-20 13:11 ` Petr Mladek
2017-04-20 13:11 ` Petr Mladek
2017-04-20 13:11 ` Petr Mladek
2017-04-20 13:11 ` Petr Mladek
2017-04-21 1:57 ` Sergey Senozhatsky
2017-04-21 1:57 ` Sergey Senozhatsky
2017-04-21 1:57 ` Sergey Senozhatsky
2017-04-21 12:06 ` Petr Mladek
2017-04-21 12:06 ` Petr Mladek
2017-04-21 12:06 ` Petr Mladek
2017-04-24 2:17 ` Sergey Senozhatsky
2017-04-24 2:17 ` Sergey Senozhatsky
2017-04-24 2:17 ` Sergey Senozhatsky
2017-04-27 13:38 ` Petr Mladek
2017-04-27 13:38 ` Petr Mladek
2017-04-27 13:38 ` Petr Mladek
2017-04-27 14:31 ` Steven Rostedt
2017-04-27 14:31 ` Steven Rostedt
2017-04-27 14:31 ` Steven Rostedt
2017-04-27 15:28 ` Petr Mladek
2017-04-27 15:28 ` Petr Mladek
2017-04-27 15:28 ` Petr Mladek
2017-04-27 15:42 ` Steven Rostedt
2017-04-27 15:42 ` Steven Rostedt
2017-04-27 15:42 ` Steven Rostedt
2017-04-28 9:02 ` Peter Zijlstra
2017-04-28 9:02 ` Peter Zijlstra
2017-04-28 9:02 ` Peter Zijlstra
2017-04-28 13:44 ` Petr Mladek [this message]
2017-04-28 13:44 ` Petr Mladek
2017-04-28 13:44 ` Petr Mladek
2017-04-28 13:58 ` Peter Zijlstra
2017-04-28 13:58 ` Peter Zijlstra
2017-04-28 13:58 ` Peter Zijlstra
2017-04-28 14:47 ` Steven Rostedt
2017-04-28 14:47 ` Steven Rostedt
2017-04-28 14:47 ` Steven Rostedt
2017-04-27 16:14 ` Steven Rostedt
2017-04-27 16:14 ` Steven Rostedt
2017-04-27 16:14 ` Steven Rostedt
2017-04-28 1:35 ` Sergey Senozhatsky
2017-04-28 1:35 ` Sergey Senozhatsky
2017-04-28 1:35 ` Sergey Senozhatsky
2017-04-28 12:57 ` Petr Mladek
2017-04-28 12:57 ` Petr Mladek
2017-04-28 12:57 ` Petr Mladek
2017-04-28 14:16 ` Steven Rostedt
2017-04-28 14:16 ` Steven Rostedt
2017-04-28 14:16 ` Steven Rostedt
2017-04-28 1:25 ` Sergey Senozhatsky
2017-04-28 1:25 ` Sergey Senozhatsky
2017-04-28 1:25 ` Sergey Senozhatsky
2017-04-28 12:38 ` Petr Mladek
2017-04-28 12:38 ` Petr Mladek
2017-04-28 12:38 ` Petr Mladek
2016-04-21 11:48 ` [PATCH v5 2/4] printk/nmi: warn when some message has been lost in NMI context Petr Mladek
2016-04-21 11:48 ` Petr Mladek
2016-04-21 11:48 ` Petr Mladek
2016-04-27 9:34 ` Russell King - ARM Linux
2016-04-27 9:34 ` Russell King - ARM Linux
2016-04-27 9:34 ` Russell King - ARM Linux
2016-04-21 11:48 ` [PATCH v5 3/4] printk/nmi: increase the size of NMI buffer and make it configurable Petr Mladek
2016-04-21 11:48 ` Petr Mladek
2016-04-21 11:48 ` Petr Mladek
2016-04-21 11:48 ` [PATCH v5 4/4] printk/nmi: flush NMI messages on the system panic Petr Mladek
2016-04-21 11:48 ` Petr Mladek
2016-04-21 11:48 ` Petr Mladek
2016-04-23 3:49 ` Sergey Senozhatsky
2016-04-23 3:49 ` Sergey Senozhatsky
2016-04-23 3:49 ` Sergey Senozhatsky
2016-04-26 14:21 ` Petr Mladek
2016-04-26 14:21 ` Petr Mladek
2016-04-26 14:21 ` Petr Mladek
2016-04-27 0:34 ` Sergey Senozhatsky
2016-04-27 0:34 ` Sergey Senozhatsky
2016-04-27 0:34 ` Sergey Senozhatsky
2016-04-27 0:36 ` [PATCH v5 0/4] Cleaning printk stuff in NMI context Sergey Senozhatsky
2016-04-27 0:36 ` Sergey Senozhatsky
2016-04-27 0:36 ` Sergey Senozhatsky
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=20170428134423.GB3452@pathway.suse.cz \
--to=pmladek@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.