From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757664Ab1DHTBC (ORCPT ); Fri, 8 Apr 2011 15:01:02 -0400 Received: from mail-wy0-f174.google.com ([74.125.82.174]:49320 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756846Ab1DHTBA (ORCPT ); Fri, 8 Apr 2011 15:01:00 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=VQfLvToW1s8L7aSFGuwpTY/BdRqjX6avHRyfqd7Me7Gokgy37kmH1f8PHgx9rZmF1X imRQPzuzUA3W27IDx994ZBo8DBFctRD/8hGG4nzsQsqruRfqvcsSPxSIGXgLO4ALsrdl 3l5bA+jbpULy1Nz/98fKM6Razov6dq5bEwRBg= Date: Fri, 8 Apr 2011 21:00:56 +0200 From: Frederic Weisbecker To: Steven Rostedt Cc: David Sharp , Vaibhav Nagarnaik , Paul Menage , Li Zefan , Stephane Eranian , Andrew Morton , Michael Rubin , Ken Chen , linux-kernel@vger.kernel.org, containers@lists.linux-foundation.org, Thomas Gleixner , Ingo Molnar , Peter Zijlstra , Arnaldo Carvalho de Melo Subject: Re: [RFC] tracing: Adding cgroup aware tracing functionality Message-ID: <20110408190052.GC1967@nowhere> References: <20110407013349.GH1867@nowhere> <20110407120608.GB1798@nowhere> <20110407213208.GE1798@nowhere> <20110408002812.GG1798@nowhere> <1302248268.21026.18.camel@frodo> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1302248268.21026.18.camel@frodo> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 08, 2011 at 03:37:48AM -0400, Steven Rostedt wrote: > I actually agree, as perf is more focused on per process (or group) than > ftrace. But that said, I guess the issue is also, if they have a simple > solution that is not invasive and suits their needs, what's the harm in > accepting it? What about a kind of cgroup_of(path) operator that we can use on filters? common_pid cgroup_of(path) or common_pid __cgroup_of__ path That way you don't bloat the tracing fast path?