From: Keith Owens <kaos@ocs.com.au>
To: Nicolas Pitre <nico@cam.org>
Cc: Daniel Jacobowitz <dan@debian.org>,
Linus Torvalds <torvalds@osdl.org>, Ingo Molnar <mingo@elte.hu>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Arjan van de Ven <arjanv@infradead.org>,
Jes Sorensen <jes@trained-monkey.org>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Oleg Nesterov <oleg@tv-sign.ru>,
David Howells <dhowells@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Benjamin LaHaise <bcrl@kvack.org>,
Steven Rostedt <rostedt@goodmis.org>,
Christoph Hellwig <hch@infradead.org>, Andi Kleen <ak@suse.de>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [patch 3/8] mutex subsystem, add atomic_*_call_if_*() to i386
Date: Thu, 22 Dec 2005 20:18:07 +1100 [thread overview]
Message-ID: <19454.1135243087@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 21 Dec 2005 15:54:13 CDT." <Pine.LNX.4.64.0512211552080.26663@localhost.localdomain>
On Wed, 21 Dec 2005 15:54:13 -0500 (EST),
Nicolas Pitre <nico@cam.org> wrote:
>On Wed, 21 Dec 2005, Daniel Jacobowitz wrote:
>
>> This new macro is only going to be used in x86-specific files, right?
>> There's no practical way to implement this on lots of other
>> architectures.
>
>The default implementation does the call in C.
>
>> Embedding a call in asm("") can break other things too - for instance,
>> unwind tables could become inaccurate.
>
>I doubt unwind tables are used at all for the kernel, are they?
Yes they are. ia64 absolutely requires accurate unwind tables, it is
part of the ABI. x86_64 is tending towards requiring accurate CFI
data.
Without valid unwind tables, backtraces are flakey at best. The lack
of decent kernel unwind for i386 is one of the reasons that kdb
backtrace for i386 is so horrible.
next prev parent reply other threads:[~2005-12-22 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 15:54 [patch 3/8] mutex subsystem, add atomic_*_call_if_*() to i386 Ingo Molnar
2005-12-21 18:54 ` Linus Torvalds
2005-12-21 18:57 ` Linus Torvalds
2005-12-21 20:01 ` Ingo Molnar
2005-12-21 20:32 ` Daniel Jacobowitz
2005-12-21 20:54 ` Nicolas Pitre
2005-12-22 9:18 ` Keith Owens [this message]
2005-12-21 19:47 ` Ingo Molnar
2005-12-21 22:40 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2005-12-21 22:37 Ingo Molnar
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=19454.1135243087@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@infradead.org \
--cc=bcrl@kvack.org \
--cc=dan@debian.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nico@cam.org \
--cc=oleg@tv-sign.ru \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=rostedt@goodmis.org \
--cc=torvalds@osdl.org \
--cc=zwane@arm.linux.org.uk \
/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