From: "long.wanglong" <long.wanglong@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: 王龙 <wanglong@laoqinren.net>, jkosina <jkosina@suse.cz>,
paulmck <paulmck@linux.vnet.ibm.com>, pmladek <pmladek@suse.cz>,
dzickus <dzickus@redhat.com>,
johannes <johannes@sipsolutions.net>, koct9i <koct9i@gmail.com>,
tglx <tglx@linutronix.de>, mingo <mingo@redhat.com>,
hpa <hpa@zytor.com>, x86 <x86@kernel.org>,
atomlin <atomlin@redhat.com>, akpm <akpm@linux-foundation.org>,
"sasha.levin" <sasha.levin@oracle.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
peifeiyue <peifeiyue@huawei.com>,
"morgan.wang" <morgan.wang@huawei.com>
Subject: Re: [RFC] how to perform a safe NMI stack trace on all CPUs on x86?
Date: Thu, 14 May 2015 19:15:20 +0800 [thread overview]
Message-ID: <555483C8.9060603@huawei.com> (raw)
In-Reply-To: <20150513102246.344ca5ba@gandalf.local.home>
On 2015/5/13 22:22, Steven Rostedt wrote:
> On Wed, 13 May 2015 22:14:54 +0800
> "王龙" <wanglong@laoqinren.net> wrote:
>
>
>> context. But how do we fix this problem in older version of kernel(eg, 3.10 stable)?
>> The 3.10 stable has no "switch printk routine" and "seq_buf" infrastructures.
>>
>> Could anyone give me some ideas?
>>
>
> Backport the necessary patches.
>
> -- Steve
>
Hi Steve,
Thank you for your reply, I will backport necessary patches to 3.10 stable.
Welcome you to review my backport patches.
Best Regards
Wang Long
> .
>
next prev parent reply other threads:[~2015-05-14 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 14:14 [RFC] how to perform a safe NMI stack trace on all CPUs on x86? 王龙
2015-05-13 14:22 ` Steven Rostedt
2015-05-14 11:15 ` long.wanglong [this message]
2015-05-13 14:26 ` Jiri Kosina
2015-05-14 11:20 ` long.wanglong
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=555483C8.9060603@huawei.com \
--to=long.wanglong@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=dzickus@redhat.com \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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=tglx@linutronix.de \
--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