From: Ingo Molnar <mingo@elte.hu>
To: Jan Beulich <JBeulich@novell.com>
Cc: tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: don't call dump_stack() from arch_trigger_all_cpu_backtrace_handler()
Date: Fri, 18 Feb 2011 08:44:36 +0100 [thread overview]
Message-ID: <20110218074436.GH11404@elte.hu> (raw)
In-Reply-To: <4D5D512902000078000326EE@vpn.id2.novell.com>
* Jan Beulich <JBeulich@novell.com> wrote:
> show_regs() already prints two(!) stack traces, [...]
That ought to get fixed as well, right?
> no need for a third one.
Agreed.
Thanks,
Ingo
next prev parent reply other threads:[~2011-02-18 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 15:47 [PATCH] x86: don't call dump_stack() from arch_trigger_all_cpu_backtrace_handler() Jan Beulich
2011-02-18 7:44 ` Ingo Molnar [this message]
2011-02-18 7:59 ` Jan Beulich
2011-02-18 10:39 ` [tip:x86/debug] x86: Don't " tip-bot for Jan Beulich
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=20110218074436.GH11404@elte.hu \
--to=mingo@elte.hu \
--cc=JBeulich@novell.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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