All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Kirill Korotaev <dev@openvz.org>
Cc: devel@openvz.org, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	xemul@openvz.org
Subject: Re: [PATCH][x86_64] IPI calltraces on x86_64
Date: Fri, 21 Apr 2006 14:02:28 +0200	[thread overview]
Message-ID: <200604211402.29107.ak@suse.de> (raw)
In-Reply-To: <444381A9.4020400@openvz.org>

On Monday 17 April 2006 13:53, Kirill Korotaev wrote:
> [PATCH] IPI calltraces on x86_64
>
> This patch makes x86_64 kernel to print calltraces on _all_
> CPUs on Alt-SysRq-p and NMI LOCKUP.
> This patch supplements the one made for i386
> some time ago and included in -mm tree.
> Since it proved its usefullness many times already
> we did the same patch for x86_64.

Sorry for the late answer.
I don't like the new call back. Can you change it to use the die notifier 
chain?

-Andi


      reply	other threads:[~2006-04-21 12:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 11:53 [PATCH][x86_64] IPI calltraces on x86_64 Kirill Korotaev
2006-04-21 12:02 ` Andi Kleen [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=200604211402.29107.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=dev@openvz.org \
    --cc=devel@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xemul@openvz.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.