Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755084Ab2EPP01 (ORCPT ); Wed, 16 May 2012 11:26:27 -0400 Received: from mail-yw0-f46.google.com ([209.85.213.46]:63142 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753950Ab2EPP0Z (ORCPT ); Wed, 16 May 2012 11:26:25 -0400 Date: Wed, 16 May 2012 12:26:19 -0300 From: Arnaldo Carvalho de Melo To: Namhyung Kim Cc: Peter Zijlstra , Paul Mackerras , Ingo Molnar , Namhyung Kim , LKML Subject: Re: [PATCH 2/3] Revert 'perf evlist: Fix creation of cpu map' Message-ID: <20120516152619.GD7864@infradead.org> References: <1337161549-9870-1-git-send-email-namhyung.kim@lge.com> <1337161549-9870-2-git-send-email-namhyung.kim@lge.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1337161549-9870-2-git-send-email-namhyung.kim@lge.com> X-Url: http://acmel.wordpress.com 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: 1126 Lines: 31 Em Wed, May 16, 2012 at 06:45:48PM +0900, Namhyung Kim escreveu: > The commit 55261f46702c ("perf evlist: Fix creation of cpu > map") changed to create a per-task event when no cpu target > is specified. However it caused a problem since perf-task do > not allow event inheritance due to scalability issues so > that the result will contain samples only from parent, not > from its children. > > So we should use perf-task-per-cpu events anyway to get the > right result. Revert it. > > Reported-by: Linus Torvalds > Analysed-by: Ingo Molnar > Acked-and-tested-by: Peter Zijlstra I'm applying it, but while trying to figure out if the logic was right I tried: perf top -C 0 -u acme To check what is that this user is doing on that CPU, and its not possible :-\ UID switch overriding CPU! - Arnaldo -- 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/