Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753837AbZLSWEM (ORCPT ); Sat, 19 Dec 2009 17:04:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753504AbZLSWEL (ORCPT ); Sat, 19 Dec 2009 17:04:11 -0500 Received: from bombadil.infradead.org ([18.85.46.34]:36932 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753324AbZLSWEJ (ORCPT ); Sat, 19 Dec 2009 17:04:09 -0500 Subject: Re: [PATCH 1/1 v2] perf record: We should fork only if a program was specified to run From: Peter Zijlstra To: Arnaldo Carvalho de Melo Cc: Ingo Molnar , linux-kernel@vger.kernel.org, =?ISO-8859-1?Q?Fr=E9d=E9ric?= Weisbecker , Mike Galbraith , Paul Mackerras In-Reply-To: <20091219215834.GE19708@ghostprotocols.net> References: <1261257771-10263-1-git-send-email-acme@infradead.org> <1261258741.4314.0.camel@laptop> <20091219215834.GE19708@ghostprotocols.net> Content-Type: text/plain; charset="UTF-8" Date: Sat, 19 Dec 2009 23:03:27 +0100 Message-ID: <1261260207.4314.4.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1420 Lines: 31 On Sat, 2009-12-19 at 19:58 -0200, Arnaldo Carvalho de Melo wrote: > Em Sat, Dec 19, 2009 at 10:39:01PM +0100, Peter Zijlstra escreveu: > > On Sat, 2009-12-19 at 19:22 -0200, Arnaldo Carvalho de Melo wrote: > > > @@ -550,7 +551,7 @@ static int __cmd_record(int argc __used, const char **argv) > > > return err; > > > } > > > > > > - if (!system_wide) > > > + if (!system_wide && profile_cpu == -1) > > > event__synthesize_thread(pid, process_synthesized_event, > > > session); > > > > Not actually sure about this bit though, since we now have > > per-task-per-cpu things, the profile_cpu is also used to !system_wide. > > this actually means: if it is not system wide and not for an specific > cpu, it must be for an specific pid. But it can be for a specific pid and specific cpu. > Not clear, right, you may want to profile an specific pid but only when > it is running on an specific CPU... But at least this patch allows for > specifiying either an specific CPU or an specific pid or systemwide. Ah, right, not enough state to tell what we meant, fair enough. -- 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/