From: David Ahern <dsahern@gmail.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Joseph Schuchart <joseph.schuchart@tu-dresden.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
thomas.ilsche@tu-dresden.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Perf: Correct Assumptions about Sample Timestamps in Passes
Date: Mon, 23 Dec 2013 09:44:25 -0500 [thread overview]
Message-ID: <52B84C49.70001@gmail.com> (raw)
In-Reply-To: <20131223131051.GB585@localhost.localdomain>
On 12/23/13, 8:10 AM, Frederic Weisbecker wrote:
> On Fri, Dec 20, 2013 at 10:09:53AM -0700, David Ahern wrote:
>> On 12/20/13, 5:27 AM, Joseph Schuchart wrote:
>>> I know this comes late, but: As far as I can see, your change does not
>>> preserve the logic of the code I suggested. The idea was to first gather
>>> all the maximum timestamps of all cpus (that is, the last timestamp seen
>>> on each cpu) and then determine the minimum of these maxima. These are
>>> two distinct steps that I think cannot be combined in one update. Your
>>
>> A number of people have reported similar problems -- timestamps
>> below last flush time. This approach would solve that problem for
>> data processed from files, so it would be a good improvement.
>
> Could it be near what you're looking for?
>
> https://lkml.org/lkml/2012/2/18/53
>
Forgot about that patch. It is similar to what Joseph wants for
analyzing a file.
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.
David
next prev parent reply other threads:[~2013-12-23 14:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 8:07 [PATCH] Perf: Correct Assumptions about Sample Timestamps in Passes Joseph Schuchart
2013-11-14 8:39 ` Ingo Molnar
2013-11-14 8:59 ` Joseph Schuchart
2013-11-14 10:05 ` Ingo Molnar
2013-11-14 14:26 ` David Ahern
2013-11-14 14:44 ` Peter Zijlstra
2013-11-14 15:02 ` David Ahern
2013-11-14 15:25 ` Peter Zijlstra
2013-11-21 14:55 ` Joseph Schuchart
2013-11-27 13:51 ` Ingo Molnar
2013-12-20 12:27 ` Joseph Schuchart
2013-12-20 17:09 ` David Ahern
2013-12-23 13:10 ` Frederic Weisbecker
2013-12-23 14:44 ` David Ahern [this message]
2013-12-26 15:14 ` Frederic Weisbecker
2013-12-26 15:24 ` David Ahern
2013-12-26 15:30 ` Frederic Weisbecker
2014-01-01 18:37 ` David Ahern
2014-01-03 22:07 ` Frederic Weisbecker
2014-01-03 22:45 ` David Ahern
2014-01-04 15:05 ` Frederic Weisbecker
2014-01-08 21:48 ` David Ahern
2014-01-09 15:19 ` Frederic Weisbecker
2014-01-12 15:46 ` David Ahern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52B84C49.70001@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=joseph.schuchart@tu-dresden.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=thomas.ilsche@tu-dresden.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.