Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754755Ab2H0V43 (ORCPT ); Mon, 27 Aug 2012 17:56:29 -0400 Received: from mail-pz0-f46.google.com ([209.85.210.46]:52203 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754531Ab2H0V41 (ORCPT ); Mon, 27 Aug 2012 17:56:27 -0400 Message-ID: <503BED07.9030404@gmail.com> Date: Mon, 27 Aug 2012 15:56:23 -0600 From: David Ahern User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Andi Kleen CC: Andrew Vagin , linux-kernel@vger.kernel.org, Peter Zijlstra , Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo Subject: Re: [PATCH 3/4] perf: teach perf inject to merge sched_stat_* and sched_switch events (v2) References: <1344344165-369636-1-git-send-email-avagin@openvz.org> <1344344165-369636-4-git-send-email-avagin@openvz.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; 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: 949 Lines: 23 On 8/27/12 2:51 PM, Andi Kleen wrote: > Andrew Vagin writes: >> >> My code saves sched_switch event for each process and when it meets >> stat_iowait, it reports the sched_switch event, because this event >> contains a correct callchain. By another words it replaces all >> stat_iowait events on proper sched_switch events. > > Is there any way to generalize this to arbitary events? I found myself > writing scripts to compute lengths between various events. But I You mean delta-time between events? I have toyed around with patches to perf-script for this -- dt between same event on a cpu, dt between consecutive events on a cpu, dt between events for a thread, etc. 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/