Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755430Ab1BSOih (ORCPT ); Sat, 19 Feb 2011 09:38:37 -0500 Received: from mail-yw0-f46.google.com ([209.85.213.46]:45878 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754368Ab1BSOid (ORCPT ); Sat, 19 Feb 2011 09:38:33 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-url:user-agent; b=M/Tp+d0Gn79Wrh9rxYcL4q2C46UMFI8Lxw+vDWmFNQV/CdM7mNsRf+MRS35RD91Bc7 NEfywo0N9AwCCkra5xRfJvVimSBjExGxjPdBXUbOnN3B/8T22W1HOKXvIQhbXcZisvQJ 139eqmgEoITwwzxqGBvSMD1d6kUCOlHmsJZj0= Date: Sat, 19 Feb 2011 12:38:25 -0200 From: Arnaldo Carvalho de Melo To: Ingo Molnar Cc: David Ahern , Peter Zijlstra , Frederic Weisbecker , linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, paulus@samba.org, Thomas Gleixner Subject: Re: [PATCH 3/3] perf events: add timehist option to record and report Message-ID: <20110219143825.GA2729@ghostprotocols.net> References: <1298008433-22911-1-git-send-email-daahern@cisco.com> <1298008433-22911-4-git-send-email-daahern@cisco.com> <20110218070657.GA11404@elte.hu> <4D5E8204.2090501@cisco.com> <20110218175926.GA3445@nowhere> <4D5EB564.6030504@cisco.com> <1298054399.5226.779.camel@laptop> <4D5EBE2C.7000701@cisco.com> <20110219093216.GA30331@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110219093216.GA30331@elte.hu> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1343 Lines: 31 Em Sat, Feb 19, 2011 at 10:32:16AM +0100, Ingo Molnar escreveu: > * David Ahern wrote: > > > On 01/23/11 at 03:45:67 a syslog event noted an application restart. > > Checking the applications logs it went silent. Why? What does perf say? > > > > Oh, 2 days have gone by before said event is reported to engineering, > > and the server was been rebooted to 'clear' the problem - hence > > resetting monotonic clock. > > I think that's a valid usecase and the feature you are suggestion is very useful. > > Why not extend the regular trace output to also (optionally) output GTOD timestamps? That is how this this feature request/submission originally started. David tried with an extra header, then a synthesized event, then after some discussion with Peter I started working on a monotonic clock event, but got sidetracked with other stuff, he tried picking up from where I left and here we are. I think the summary is: we need a clock_gettime like interface so that users can pick and choose what clock matches best whatever app they're trying to merge logs. - Arnaldo -- 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/