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. -- Philippe Elie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
- From: Eric Dumazet <[email protected]>
- Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
- From: Andi Kleen <[email protected]>
- Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
- References:
- [PATCH] allow CONFIG_FRAME_POINTER for x86-64
- From: "Jan Beulich" <[email protected]>
- Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
- From: Andi Kleen <[email protected]>
- Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
- From: "Jan Beulich" <[email protected]>
- Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
- From: Andi Kleen <[email protected]>
- [PATCH] allow CONFIG_FRAME_POINTER for x86-64
- Prev by Date: Re: [PATCH 2/25] NTFS: Allow highmem kmalloc() in ntfs_malloc_nofs() and add _nofail() version.
- Next by Date: Re: [PATCH 2/25] NTFS: Allow highmem kmalloc() in ntfs_malloc_nofs() and add _nofail() version.
- Previous by thread: Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
- Next by thread: Re: [discuss] [PATCH] allow CONFIG_FRAME_POINTER for x86-64
- Index(es):
