Re: [PATCH v4 0/6] Micro-optimize vclock_gettime

From: Thomas Gleixner
Date: Mon May 16 2011 - 12:25:27 EST


On Mon, 16 May 2011, Andi Kleen wrote:

> > - Don't turn off frame pointers in vDSO code.
>
> Why? Note frame pointers are costly on some CPUs, like Atom.

That's the least worry on ATOM.

> Also unlike the primitive state of the kernel the user space debuggers
> are usually advanced enough to support dwarf2 unwinding.

And unless you or someone else changes the primitive state of the
kernel, framepointers are going to stay simply because removing them
breaks profiling backtraces when the hit is inside vread().

Thanks,

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