From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753047Ab1EPQZW (ORCPT ); Mon, 16 May 2011 12:25:22 -0400 Received: from www.linutronix.de ([62.245.132.108]:60812 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751790Ab1EPQZV (ORCPT ); Mon, 16 May 2011 12:25:21 -0400 Date: Mon, 16 May 2011 18:25:14 +0200 (CEST) From: Thomas Gleixner To: Andi Kleen cc: Andy Lutomirski , x86@kernel.org, linux-kernel@vger.kernel.org, Ingo Molnar , Linus Torvalds , "David S. Miller" , Eric Dumazet , Peter Zijlstra , Borislav Petkov Subject: Re: [PATCH v4 0/6] Micro-optimize vclock_gettime In-Reply-To: <20110516160943.GC25898@one.firstfloor.org> Message-ID: References: <20110516160943.GC25898@one.firstfloor.org> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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