From: David Mosberger <davidm@napali.hpl.hp.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] generic show_stack facility
Date: Fri, 29 Mar 2002 07:46:07 -0800 [thread overview]
Message-ID: <15524.35903.821173.784043@napali.hpl.hp.com> (raw)
In-Reply-To: <20020329152314.A22333@phoenix.infradead.org>
>>>>> On Fri, 29 Mar 2002 15:23:14 +0000, Christoph Hellwig <hch@infradead.org> said:
Christoph> This patch adds a prototype for show_stack to sched.h and
Christoph> exports it. Andrea's VM updates want this, as does Tux
Christoph> and I think it's a facility we want to proive genericly.
Christoph> Note that some architectures (e.g. ia64) have a
Christoph> conflicting prototype and some (e.g. sparc) don't have
Christoph> show_stack at all, but I think -pre5 is early enough in
Christoph> the 2.4.19 cycle to let the maintainers fix it.
Christoph> Could you apply the patch to your tree?
Please don't. The patch is broken.
Christoph, why do you think the prototype for ia64 is different? It's
because it *has to be*. In general, you can't do a backtrace without
having the full (preserved) state of the CPU at the point of which the
backtrace begins.
--david
next prev parent reply other threads:[~2002-03-29 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 15:23 Christoph Hellwig
2002-03-29 15:46 ` David Mosberger [this message]
2002-03-29 16:06 ` Christoph Hellwig
2002-03-29 17:08 ` David Mosberger
2002-03-29 17:16 ` arjan
2002-03-29 18:25 ` David Mosberger
2002-03-30 10:06 ` Kai Henningsen
2002-03-29 17:36 ` Andrew Morton
2002-03-29 18:26 ` David Mosberger
2002-03-29 18:34 ` Christoph Hellwig
2002-03-29 18:41 ` Andrew Morton
2002-03-30 3:05 Keith Owens
2002-03-30 3:31 ` Andrew Morton
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=15524.35903.821173.784043@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@zip.com.au \
--cc=davidm@hpl.hp.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®