Date: Fri, 9 Sep 2005 13:19:15 +0200
From: Andi Kleen <ak@suse.de>
To: Philippe Elie <phil.el@wanadoo.fr>
Cc: Andi Kleen <ak@suse.de>, Jan Beulich <JBeulich@novell.com>,
       discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
Message-ID: <20050909111909.GJ19913@wotan.suse.de>
References: <43207D28020000780002451E@emea1-mh.id2.novell.com> <200509091054.11932.ak@suse.de> <43216EFB020000780002489B@emea1-mh.id2.novell.com> <200509091123.59205.ak@suse.de> <20050909110702.GA787@zaniah>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050909110702.GA787@zaniah>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 705
Lines: 19

On Fri, Sep 09, 2005 at 01:07:02PM +0200, Philippe Elie wrote:
> On Fri, 09 Sep 2005 at 11:23 +0000, Andi Kleen wrote:
> 
>  
> > Indeed. Someone must have fixed it.  But why would anyone want frame pointers
> > on x86-64?
> 
> Oprofile can use it, I though it was already used but apparently only
> to backtrace userspace actually.

You should be using dwarf2 unwind information instead. Near all
user space on x86-64 has it, and kernels sometimes too.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/