From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753298AbcKZDiU (ORCPT ); Fri, 25 Nov 2016 22:38:20 -0500 Received: from mail-io0-f193.google.com ([209.85.223.193]:34474 "EHLO mail-io0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753117AbcKZDiP (ORCPT ); Fri, 25 Nov 2016 22:38:15 -0500 Subject: Re: [PATCH 1/3] perf sched timehist: Mark schedule function in callchains To: Namhyung Kim References: <20161124011114.7102-1-namhyung@kernel.org> <0eaa350e-8b5d-539f-c073-f230353ae405@gmail.com> <20161124063046.GA12782@sejong> Cc: Arnaldo Carvalho de Melo , Ingo Molnar , Peter Zijlstra , Jiri Olsa , LKML , Stephane Eranian , Andi Kleen From: David Ahern Message-ID: <2e208823-dbc2-a0b3-1b13-2e0e8bd6926e@gmail.com> Date: Fri, 25 Nov 2016 20:38:11 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 In-Reply-To: <20161124063046.GA12782@sejong> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/23/16 11:30 PM, Namhyung Kim wrote: > Hi David, > > On Wed, Nov 23, 2016 at 10:13:46PM -0500, David Ahern wrote: >> On 11/23/16 8:11 PM, Namhyung Kim wrote: >>> The sched_switch event always captured from the scheduler function. So >>> it'd be great omit them from the callchain. This patch marks the >>> functions to be omitted by later patch. >> >> I had this covered by a symbol filter: >> >> https://github.com/dsahern/linux/blob/perf/full-monty-4.1/tools/perf/builtin-sched.c#L3000 >> >> Not sure what happened over the years but that should still work and >> allows the user to add more symbols to ignore: > > The symbol filter was removed by commit be39db9f2932 ("perf symbols: > Remove symbol_filter_t machinery"). That's unfortunate. The exclude list is huge in removing redundant callchains and getting more relevant information on the screen with a stack depth of 5. I'll see what I can cook up with the existing code.