From: Viresh Kumar <viresh.linux at gmail.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [PATCH] Fix timer and work perf events timestamp tracing
Date: Wed, 05 Sep 2012 16:58:50 +0530 [thread overview]
Message-ID: <CAOh2x=m_KLU9rho-DvT5sz0MW5ZRswxTuTQt2=+i4brd1OyjjA@mail.gmail.com> (raw)
In-Reply-To: 1346840555-18457-1-git-send-email-rajagopal.venkat@linaro.org
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
On Wed, Sep 5, 2012 at 3:52 PM, Rajagopal Venkat
<rajagopal.venkat(a)linaro.org> wrote:
> Incorrect timer and work perf events timestamp tracing is one
> of the reason for reporting usage over 100%. This patch will
> resolve the issue by
> - rejecting the events for which entry timestamp is not recorded.
> Currently these events exit timestamp itself is considered as
> usage period resulting in over 100% usage.
> - clearing event timestamps from global map at the end of each
> measurement to avoid collision with earlier recorded timestamps.
Tried it few times on Panda Board.
Tested-by: Viresh Kumar <viresh.kumar(a)linaro.org>
next reply other threads:[~2012-09-05 11:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 11:28 Viresh Kumar [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-06 13:51 [Powertop] [PATCH] Fix timer and work perf events timestamp tracing Arjan van de Ven
2012-09-06 13:42 Rajagopal Venkat
2012-09-05 18:06 Arjan van de Ven
2012-09-05 17:45 Rajagopal Venkat
2012-09-05 17:22 Arjan van de Ven
2012-09-05 17:19 Rajagopal Venkat
2012-09-05 17:09 Arjan van de Ven
2012-09-05 16:56 Rajagopal Venkat
2012-09-05 15:12 Chris Ferron
2012-09-05 12:44 Sergey Senozhatsky
2012-09-05 10:22 Rajagopal Venkat
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='CAOh2x=m_KLU9rho-DvT5sz0MW5ZRswxTuTQt2=+i4brd1OyjjA@mail.gmail.com' \
--to=powertop@lists.01.org \
/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.