Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754594Ab2ENHFO (ORCPT ); Mon, 14 May 2012 03:05:14 -0400 Received: from mail-wi0-f178.google.com ([209.85.212.178]:54851 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754231Ab2ENHFM (ORCPT ); Mon, 14 May 2012 03:05:12 -0400 Date: Mon, 14 May 2012 09:05:07 +0200 From: Ingo Molnar To: Linus Torvalds Cc: Arnaldo Carvalho de Melo , linux-kernel@vger.kernel.org, Arjan van de Ven , David Ahern , Frederic Weisbecker , Mike Galbraith , Namhyung Kim , Paul Mackerras , Peter Zijlstra , Stephane Eranian Subject: Re: [GIT PULL 0/8] Annotation weekly ponies delivery Message-ID: <20120514070507.GB27980@gmail.com> References: <1336852387-16322-1-git-send-email-acme@infradead.org> <20120512212531.GC20057@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1462 Lines: 37 * Linus Torvalds wrote: > On Sat, May 12, 2012 at 2:25 PM, Arnaldo Carvalho de Melo > wrote: > > > > Didn't notice it, but then I'm not updating the kernel that frequently, > > will check on this Sandy Bridge nobo (i7-2920XM). > > I think SNB has problems with PEBS and cycles anyway. I have a > westmere machine that I use for profiling for that reason. I have a pre-westmere Nehalem that I use most for perf testing - that one appears to be working well both with default cycles and with cycles:pp. Will test on a Westmere. btw., Arnaldo, could we make cycles:pp the default event on perf record and perf top? We have the new AMD IBS code in perf/core queued up for v3.5, which is roughly equivalent to cycles:p on Intel CPUs, so if we standardize on cycles:pp we'll get improved skidless (and on Intel pre-SB CPUs, precise) profiling output by default. While at it I'd also suggest increasing the default sampling frequency, from 1000 Hz per CPU to at least 4Khz auto-freq or so - this should work well all across the board I think. CPUs are getting faster and command/app run times are getting shorter, 1Khz is a bit low IMO. Thanks, Ingo -- 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/