From: Andrew Morton <akpm@zip.com.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: davidm@hpl.hp.com, Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] generic show_stack facility
Date: Fri, 29 Mar 2002 10:41:11 -0800 [thread overview]
Message-ID: <3CA4B547.AB359F0E@zip.com.au> (raw)
In-Reply-To: <20020329160618.A25410@phoenix.infradead.org> <15524.40817.306204.292158@napali.hpl.hp.com> <3CA4A61A.A844E21B@zip.com.au> <20020329183457.A4087@phoenix.infradead.org>
Christoph Hellwig wrote:
>
> On Fri, Mar 29, 2002 at 09:36:26AM -0800, Andrew Morton wrote:
> > Here's the diff. Comments?
>
> I don't see who having to independand declaration in the same kernel
> image are supposed to work..
It goes in lib/lib.a. The linker will only pick up
the default version if the architecture doesn't
have its own dump_stack().
bust_spinlocks() has worked that way for quite some time.
> I think you really want some HAVE_ARCH_SHOW_STACK define to disable
> the generic version..
Yup. But it's nice to be able to slot the default version
into lib.a. In the bust_spinlocks case, architectures only
need to implement a version if they have special needs.
-
next prev parent reply other threads:[~2002-03-29 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 15:23 [PATCH] generic show_stack facility Christoph Hellwig
2002-03-29 15:46 ` David Mosberger
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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=3CA4B547.AB359F0E@zip.com.au \
--to=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 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.