From: "long.wanglong" <long.wanglong@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: <jkosina@suse.cz>, <gregkh@linuxfoundation.org>,
<stable@vger.kernel.org>, <wanglong@laoqinren.net>,
<peifeiyue@huawei.com>, <linux-kernel@vger.kernel.org>,
<morgan.wang@huawei.com>, <paulmck@linux.vnet.ibm.com>,
<pmladek@suse.cz>, <dzickus@redhat.com>, <x86@kernel.org>,
<sasha.levin@oracle.com>
Subject: Re: [RFC PATCH 00/17][request for stable 3.10 inclusion] x86/nmi: Print all cpu stacks from NMI safely
Date: Mon, 18 May 2015 11:52:49 +0800 [thread overview]
Message-ID: <55596211.7050606@huawei.com> (raw)
In-Reply-To: <20150514095504.3076310c@gandalf.local.home>
On 2015/5/14 21:55, Steven Rostedt wrote:
> On Thu, 14 May 2015 11:34:47 +0000
> Wang Long <long.wanglong@huawei.com> wrote:
>
>> The patch 1-13 backport the "seq_buf" infrastructures. in detail, patch 1, 2
>> and 6 only backport "seq_buf" related code.
>>
>
> Ah, so basically you just backported the seq_buf.c code without
> modifying the trace_seq code. That's a good approach. I don't have much
> time to look at these but I'll try to skim them to see if I find
> anything broken.
>
> I may pull all of them into a test branch and run my tests to make sure
> they don't break anything else.
>
> -- Steve
>
Hi Steve,
Thank you for your review and test. Does your testcases run OK with this
series patches?
Best Regards
Wang Long
>
>> arch/x86/kernel/apic/hw_nmi.c | 86 +++++++++-
>> include/linux/percpu.h | 4 +
>> include/linux/printk.h | 2 +
>> include/linux/seq_buf.h | 136 ++++++++++++++++
>> kernel/printk.c | 41 +++--
>> lib/Makefile | 2 +-
>> lib/seq_buf.c | 359 ++++++++++++++++++++++++++++++++++++++++++
>> 7 files changed, 617 insertions(+), 13 deletions(-)
>> create mode 100644 include/linux/seq_buf.h
>> create mode 100644 lib/seq_buf.c
>>
>
>
> .
>
prev parent reply other threads:[~2015-05-18 3:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 11:34 [RFC PATCH 00/17][request for stable 3.10 inclusion] x86/nmi: Print all cpu stacks from NMI safely Wang Long
2015-05-14 11:34 ` [RFC PATCH 01/17] tracing: Create seq_buf layer in trace_seq Wang Long
2015-05-14 11:34 ` [RFC PATCH 02/17] tracing: Convert seq_buf_path() to be like seq_path() Wang Long
2015-05-14 11:34 ` [RFC PATCH 03/17] tracing: Convert seq_buf fields to be like seq_file fields Wang Long
2015-05-14 11:34 ` [RFC PATCH 04/17] tracing: Add a seq_buf_clear() helper and clear len and readpos in init Wang Long
2015-05-14 11:34 ` [RFC PATCH 05/17] seq_buf: Create seq_buf_used() to find out how much was written Wang Long
2015-05-14 11:34 ` [RFC PATCH 06/17] tracing: Use trace_seq_used() and seq_buf_used() instead of len Wang Long
2015-05-14 11:34 ` [RFC PATCH 07/17] seq_buf: Add seq_buf_can_fit() helper function Wang Long
2015-05-14 11:34 ` [RFC PATCH 08/17] tracing: Have seq_buf use full buffer Wang Long
2015-05-14 11:34 ` [RFC PATCH 09/17] tracing: Add seq_buf_get_buf() and seq_buf_commit() helper functions Wang Long
2015-05-14 11:34 ` [RFC PATCH 10/17] seq-buf: Make seq_buf_bprintf() conditional on CONFIG_BINARY_PRINTF Wang Long
2015-05-14 11:34 ` [RFC PATCH 11/17] seq_buf: Move the seq_buf code to lib/ Wang Long
2015-05-14 11:34 ` [RFC PATCH 12/17] seq_buf: Fix seq_buf_vprintf() truncation Wang Long
2015-05-14 11:35 ` [RFC PATCH 13/17] seq_buf: Fix seq_buf_bprintf() truncation Wang Long
2015-05-14 11:35 ` [RFC PATCH 14/17] printk: Add per_cpu printk func to allow printk to be diverted Wang Long
2015-05-18 13:56 ` Petr Mladek
2015-05-14 11:35 ` [RFC PATCH 15/17] printk/percpu: Define printk_func when printk is not defined Wang Long
2015-05-14 11:35 ` [RFC PATCH 16/17] x86/nmi: Perform a safe NMI stack trace on all CPUs Wang Long
2015-05-18 14:17 ` Petr Mladek
2015-05-19 8:56 ` long.wanglong
2015-05-14 11:35 ` [RFC PATCH 17/17] x86/nmi: Fix use of unallocated cpumask_var_t Wang Long
2015-05-14 13:55 ` [RFC PATCH 00/17][request for stable 3.10 inclusion] x86/nmi: Print all cpu stacks from NMI safely Steven Rostedt
2015-05-18 3:52 ` long.wanglong [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=55596211.7050606@huawei.com \
--to=long.wanglong@huawei.com \
--cc=dzickus@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan.wang@huawei.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peifeiyue@huawei.com \
--cc=pmladek@suse.cz \
--cc=rostedt@goodmis.org \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=wanglong@laoqinren.net \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).