[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131226153033.GC15303@localhost.localdomain>
Date: Thu, 26 Dec 2013 16:30:35 +0100
From: Frederic Weisbecker <fweisbec@...il.com>
To: David Ahern <dsahern@...il.com>
Cc: Joseph Schuchart <joseph.schuchart@...dresden.de>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
thomas.ilsche@...dresden.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Perf: Correct Assumptions about Sample Timestamps in
Passes
On Thu, Dec 26, 2013 at 10:24:03AM -0500, David Ahern wrote:
> On 12/26/13, 10:14 AM, Frederic Weisbecker wrote:
> >>I was carrying that patch while working on perf-kvm-stat-live last
> >>Fall. It does not solve the problem for live commands, so ended up
> >>dropping it and going with local (to the command) hacks. I still
> >>think for live commands getting a perf_clock timestamp at the start
> >>of a round and using that as the flush time will work best.
> >
> >Ok, but how would you fetch this perf clock timestamp, with an explicit read?
>
> One option is exporting perf_clock to userspace.
>
> Preferably a built-in option, https://lkml.org/lkml/2013/12/10/781,
> but I can go the module route if I have to:
> https://github.com/dsahern/linux/blob/perf-full-monty/README.ahern
I see, that's one of the very verbose threads I've seen lately ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists