From: Chris Ferron <chris.e.ferron at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] hrtimer events are not properly added -- is this bug or feature?
Date: Tue, 31 Jul 2012 13:08:42 -0700 [thread overview]
Message-ID: <54176.10.255.82.41.1343765322.squirrel@linux.jf.intel.com> (raw)
In-Reply-To: 500E4D97.5040902@samsung.com
[-- Attachment #1: Type: text/plain, Size: 1993 bytes --]
> Hello!
>
> In the function start_process_measurement() in the file
> src/process/do_process.cpp
> events are added to perf_bundle:
> perf_events->add_event("irq:softirq_entry");
> perf_events->add_event("irq:softirq_exit");
> perf_events->add_event("timer:timer_expire_entry");
> perf_events->add_event("timer:timer_expire_exit");
> perf_events->add_event("hrtimer_expire_entry"); /* !!! */
> perf_events->add_event("hrtimer_expire_exit"); /* !!! */
> if (!perf_events->add_event("power:cpu_idle")){
> perf_events->add_event("power:power_start");
> perf_events->add_event("power:power_end");
> }
>
> As you may see all events are prefixed with the subsystem name.
> All but hrtimer_expire_entry and hrtimer_expire_exit. And without "timer:"
> prefix
> these events are never catched.
>
> So I have added this prefix and see that events are intercepted as needed.
> But event parser complains about wrong event format:
> unknown op '{'
> failed to read event print fmt for hrtimer_expire_entry
>
> It seems that event parser can't handle square bracket in print format for
> the event:
> print fmt: "hrtimer=%p function=%pf now=%llu", REC->hrtimer,
> REC->function, (unsigned long long)(((ktime_t) { .tv64 = REC->now }).tv64)
>
> So is the absence of "timer:" prefix a bug or a commenting of non-working
> case?
I sent a note to Steve for a consult, seems its a bug. Steve sent a fix it
in the traceevent lib. Thanks for the report, please let me know if you
find something else.
>
> Thank you.
>
> --
> Best regards,
> Igor Zhbanov,
> Expert Software Engineer,
> phone: +7 (495) 797 25 00 ext 3806
> e-mail: i.zhbanov(a)samsung.com
>
> ASWG, Moscow R&D center, Samsung Electronics
> 12 Dvintsev street, building 1
> 127018, Moscow, Russian Federation
>
> _______________________________________________
> PowerTop mailing list
> PowerTop(a)lists.01.org
> https://lists.01.org/mailman/listinfo/powertop
>
next reply other threads:[~2012-07-31 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 20:08 Chris Ferron [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-25 17:45 [Powertop] hrtimer events are not properly added -- is this bug or feature? Chris Ferron
2012-07-24 7:24 Igor Zhbanov
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=54176.10.255.82.41.1343765322.squirrel@linux.jf.intel.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.