From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Frank Ch. Eigler" Subject: Re: timing information with perf Date: Mon, 16 Nov 2015 19:30:20 -0500 Message-ID: <20151117003020.GD25870@redhat.com> References: <94D0C06D-C3A7-4BD1-9898-124EE0AA923D@netapp.com> <20151117001233.GC11993@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx1.redhat.com ([209.132.183.28]:38249 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751236AbbKQAaV (ORCPT ); Mon, 16 Nov 2015 19:30:21 -0500 Content-Disposition: inline In-Reply-To: <20151117001233.GC11993@kernel.org> Sender: linux-perf-users-owner@vger.kernel.org List-ID: To: Arnaldo Carvalho de Melo Cc: "Kornievskaia, Olga" , "linux-perf-users@vger.kernel.org" Hi - acme wrote: > [...] > > For completeness, a complete systemtap implementation of this could look like: > > > # stap -e ' > > global s, t% > > probe kernel.trace("foobar_enter") { > > t[tid()]=gettimeofday_us() > > } [...] > > ' > > Is that done syncronously? Meaning - calculated live as the tracepoints hit? Yes, right during the respective callbacks. No trace files nor postprocessing. - FChE