All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <ak@muc.de>
Cc: Arjan van de Ven <arjan@infradead.org>, Jan Hubicka <jh@suse.cz>,
	Jack F Vogel <jfv@bluesong.net>,
	linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [discuss] booting a kernel compiled with -mregparm=0
Date: Mon, 17 Jan 2005 12:38:37 -0800	[thread overview]
Message-ID: <41EC224D.5080204@zytor.com> (raw)
In-Reply-To: <m1wtubvm8y.fsf@muc.de>

Andi Kleen wrote:
> 
> To be fair there isn't a nice library for it on x86-64.  There
> is libunwind on IA64, but afaik nobody ported it to x86-64 yet.
> 
> Just various projects have their own private unwind
> implementation. The kernel including KDB has always lived with
> imprecise backtraces and no argument printing. I don't think it has
> been a show stopper so far.  If you really want the arguments you can
> always use kgdb.
> 
> However I'm not sure we really want libunwind in the kernel anyways
> (not even in KDB ;-) If anything better something stripped down and 
> simple which libunwind isn't.
> 
> Unfortunately dwarf2 is not exactly a simple spec so implementing
> a new backtracer for the kernel is not a trivial task. 
> 

Seems like the unwinder should be running client-side, like it does on 
kgdb.  Or does kdb not have a client at all?  (If so, I have no sympathy 
for it.)

	-hpa


  reply	other threads:[~2005-01-17 20:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 16:34 booting a kernel compiled with -mregparm=0 Tigran Aivazian
2005-01-14 20:56 ` [discuss] " Jan Hubicka
2005-01-14 21:28   ` linux-os
2005-01-15  2:29     ` H. Peter Anvin
2005-01-17  9:30       ` Tigran Aivazian
2005-01-17  9:53         ` Arjan van de Ven
2005-01-17 10:04           ` Tigran Aivazian
2005-01-17 18:10             ` H. Peter Anvin
2005-01-17 20:22               ` Andi Kleen
2005-01-17 20:38                 ` H. Peter Anvin [this message]
2005-01-17 22:08                   ` Andi Kleen
2005-01-18 11:25                   ` Tigran Aivazian
2005-01-18 11:51                     ` Arjan van de Ven
2005-01-18 13:04                     ` Tigran Aivazian
2005-01-18 13:16                       ` Tigran Aivazian
2005-01-17 10:59         ` Andi Kleen
2005-01-17 13:17           ` Tigran Aivazian
2005-01-17 16:38         ` Linus Torvalds
2005-01-18 20:38         ` Keith Owens
2005-01-18 23:15           ` Andi Kleen

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=41EC224D.5080204@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@muc.de \
    --cc=arjan@infradead.org \
    --cc=jfv@bluesong.net \
    --cc=jh@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.