Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932624Ab2BONrr (ORCPT ); Wed, 15 Feb 2012 08:47:47 -0500 Received: from mail-gx0-f174.google.com ([209.85.161.174]:41884 "EHLO mail-gx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932226Ab2BONrn (ORCPT ); Wed, 15 Feb 2012 08:47:43 -0500 Date: Wed, 15 Feb 2012 11:47:33 -0200 From: Arnaldo Carvalho de Melo To: Peter Zijlstra Cc: Luigi Semenzato , Alexander Viro , Paul Mackerras , Ingo Molnar , Andrew Morton , Vasiliy Kulikov , Stephen Wilson , Oleg Nesterov , Tejun Heo , Paul Gortmaker , Andi Kleen , Lucas De Marchi , Greg Kroah-Hartman , "Eric W. Biederman" , "Rafael J. Wysocki" , Frederic Weisbecker , David Ahern , Namhyung Kim , Robert Richter , linux-kernel@vger.kernel.org, sonnyrao@chromium.org, olofj@chromium.org, eranian@google.com Subject: Re: [PATCH] Perf: bug fix: distinguish between rename and exec Message-ID: <20120215134733.GL28614@infradead.org> References: <1329195360-10699-1-git-send-email-semenzato@chromium.org> <1329310113.2293.72.camel@twins> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1329310113.2293.72.camel@twins> 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: 1582 Lines: 36 Em Wed, Feb 15, 2012 at 01:48:33PM +0100, Peter Zijlstra escreveu: > I really dislike changing generic code purely for the purpose of > instrumentation like this. Better to pull perf_event_comm() out of here > if you want to change semantics. > > Personally I couldn't care less about renames, I think they're a waste > of time, so I'm ok with the simple patch moving the perf_event_comm() > into setup_new_exec() and possibly renaming it to perf_event_exec(). > > Acme, do you care about renames? I like your idea of keeping the semantics of PERF_RECORD_COMM and introducing a PERF_RECORD_EXEC, just have to think about how to handle that in a way that the tools detect that we have PERF_RECORD_EXEC... Humm, will be yet another fallback for setting an perf_event_attr bit, just like with .sample_id_all and .exclude_{guest,host}... That together with the per class errnos + __strerror() method will allow to move all the event creation finally to perf_evlist__open() where all this gets nicely hidden away from poor tools. We can then even have an ui__evlist_perror() method that does all the ui__warning calls, etc. So, yes, from a tooling perspective, I want to be notified of renames and being able to stop relying on PERF_RECORD_COMM to call map_groups__flush and instead do it at PERF_RECORD_EXEC seems a bonus. - 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/