From: Keith Owens <kaos@ocs.com.au>
To: Andrew Morton <akpm@zip.com.au>
Cc: Christoph Hellwig <hch@infradead.org>,
davidm@hpl.hp.com, Marcelo Tosatti <marcelo@conectiva.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] generic show_stack facility
Date: Sat, 30 Mar 2002 14:05:46 +1100 [thread overview]
Message-ID: <1886.1017457546@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 29 Mar 2002 10:41:11 -0800." 3CA4B547.AB359F0E@zip.com.au>
On Fri, 29 Mar 2002 10:41:11 -0800,
Andrew Morton <akpm@zip.com.au> wrote:
>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 have a problem with putting routines in lib.a and relying on the
linker to pull them out by default. It does not work for routines
called from modules, modules do not include lib.a. Remember the recent
problems with crc32.o?
bust_spinlocks() is not an issue because it is only called from built
in code. show_stack() has been used as a debugging facility and it
could be called from a module.
next reply other threads:[~2002-03-30 3:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-30 3:05 Keith Owens [this message]
2002-03-30 3:31 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2002-03-29 15:23 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
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=1886.1017457546@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--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®