From: "Robert Schöne" <robert.schoene@tu-dresden.de>
To: Thomas Renninger <trenn@suse.de>
Cc: arjan@linux.intel.com, jean.pihet@newoldbits.com, mingo@elte.hu,
rjw@sisk.pl, linux-omap@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
linux-trace-users@vger.kernel.org
Subject: Re: [PATCH 4/4] PERF: fix power:cpu_idle double end events
Date: Mon, 01 Nov 2010 09:11:28 +0100 [thread overview]
Message-ID: <1288599088.2712.47.camel@localhost> (raw)
In-Reply-To: <201010271742.04545.trenn@suse.de>
Am Mittwoch, den 27.10.2010, 17:42 +0200 schrieb Thomas Renninger:
> Robert: I expect you tested this on a machine with no cpuidle
> driver registered?
You're right, there was no idle driver, but the idle process from
process_64.c which called the idle routine.
I reported my thoughts on this on 14th of May this year 2010, mostly
claiming for a standard on where to report these events.
You're also missing the other idle routines from x86/kernel/process.c
mwait_idle_with_hints and mwait_idle only throw start events, so they
should behave like default_idle. poll_idle on the other hand reports the
end event itself.
Robert
next prev parent reply other threads:[~2010-11-01 8:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 23:43 Cleanup and fixes for power trace events Thomas Renninger
2010-10-26 23:43 ` [PATCH 1/4] PERF: Do not export power_frequency, but power_start event Thomas Renninger
2010-10-26 23:43 ` [PATCH 2/4] PERF(kernel): Cleanup power events V3 Thomas Renninger
2010-10-26 23:43 ` [PATCH 3/4] PERF(userspace): Adjust perf timechart to the new " Thomas Renninger
2010-10-26 23:43 ` [PATCH 4/4] PERF: fix power:cpu_idle double end events Thomas Renninger
2010-10-27 15:42 ` Thomas Renninger
2010-11-01 8:11 ` Robert Schöne [this message]
2010-11-04 8:57 ` Thomas Renninger
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=1288599088.2712.47.camel@localhost \
--to=robert.schoene@tu-dresden.de \
--cc=arjan@linux.intel.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=trenn@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox