From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753910Ab1BVHmO (ORCPT ); Tue, 22 Feb 2011 02:42:14 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:49734 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753831Ab1BVHmN (ORCPT ); Tue, 22 Feb 2011 02:42:13 -0500 Date: Tue, 22 Feb 2011 08:41:58 +0100 From: Ingo Molnar To: Frederic Weisbecker Cc: David Ahern , linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, acme@ghostprotocols.net, peterz@infradead.org, paulus@samba.org, tglx@linutronix.de Subject: Re: [PATCH 0/4] perf events: Add realtime clock event and timehist option -v2 Message-ID: <20110222074158.GA32322@elte.hu> References: <1298322150-15505-1-git-send-email-daahern@cisco.com> <20110221213740.GC3583@nowhere> <4D62DC21.4070407@cisco.com> <20110221215533.GD3583@nowhere> <4D62E2B0.1070607@cisco.com> <20110221222104.GE3583@nowhere> <4D630E79.7030106@cisco.com> <20110222025001.GA5475@nowhere> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110222025001.GA5475@nowhere> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Frederic Weisbecker wrote: > perf-script is not new, it was there in november already, although named perf > trace at that time. Yes. The new 'perf trace' utility - which might be the straightforward 'report a trace' utility that David is looking for is still WIP and can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git tmp.perf/trace Warning: the code is stale and needs much more work to become mergable. But displaying GTOD timestamps is very much something that looks sensible in the 'perf trace' context as well. Thanks, Ingo