Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751731AbbFLArU (ORCPT ); Thu, 11 Jun 2015 20:47:20 -0400 Received: from mail-ig0-f170.google.com ([209.85.213.170]:37891 "EHLO mail-ig0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750818AbbFLArS (ORCPT ); Thu, 11 Jun 2015 20:47:18 -0400 Message-ID: <557A2C14.4010804@gmail.com> Date: Thu, 11 Jun 2015 18:47:16 -0600 From: David Ahern User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Peter Zijlstra , Adrian Hunter CC: Andi Kleen , Arnaldo Carvalho de Melo , Ingo Molnar , linux-kernel@vger.kernel.org, Jiri Olsa , Stephane Eranian , mathieu.poirier@linaro.org, Pawel Moll Subject: Re: [RFC PATCH] perf: Add PERF_RECORD_SWITCH to indicate context switches References: <1433859670-10806-1-git-send-email-adrian.hunter@intel.com> <20150611141548.GW19282@twins.programming.kicks-ass.net> In-Reply-To: <20150611141548.GW19282@twins.programming.kicks-ass.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 825 Lines: 18 On 6/11/15 8:15 AM, Peter Zijlstra wrote: >> This new PERF_RECORD_SWITCH event does not have those problems >> and it also has a couple of other small advantages. It is >> easier to use because it is an auxiliary event (like mmap, >> comm and task events) which can be enabled by setting a single >> bit. It is smaller than sched:sched_switch and easier to parse. > > Right, so the one wee problem I have is that this only provides sched_in > data, I imagine people might be interested in sched_out as well. Yes and with the option of collecting callchains for sched_out. David -- 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/