From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-pm@lists.linux-foundation.org
Cc: Thomas Renninger <trenn@suse.de>,
jean.pihet@newoldbits.com, linux-trace-users@vger.kernel.org,
linux-omap@vger.kernel.org, arjan@linux.intel.com, mingo@elte.hu
Subject: Re: [linux-pm] [PATCH 2/3] PERF(kernel): Cleanup power events
Date: Thu, 28 Oct 2010 13:31:19 +0200 [thread overview]
Message-ID: <201010281331.19503.rjw@sisk.pl> (raw)
In-Reply-To: <201010281317.55502.rjw@sisk.pl>
On Thursday, October 28, 2010, Rafael J. Wysocki wrote:
> On Thursday, October 28, 2010, Thomas Renninger wrote:
> > Recent changes:
> > - Enable EVENT_POWER_TRACING_DEPRECATED by default
> >
> > New power trace events:
> > power:cpu_idle
> > power:cpu_frequency
> > power:machine_suspend
> >
> >
> > C-state/idle accounting events:
> > power:power_start
> > power:power_end
> > are replaced with:
> > power:cpu_idle
> >
> > and
> > power:power_frequency
> > is replaced with:
> > power:cpu_frequency
> >
> > power:machine_suspend
> > is newly introduced, a first implementation
> > comes from the ARM side, but it's easy to add these events
> > in X86 as well if needed.
>
> Can you please check that changelog, please?
Sorry s/check/modify/
In fact, there won't be any ARM implementation, because it's going to be
added at the core level.
> I've asked you for that already once.
Thanks,
Rafael
next prev parent reply other threads:[~2010-10-28 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 9:02 Cleanup and enhance power trace events Thomas Renninger
2010-10-28 9:02 ` [PATCH 1/3] PERF: Do not export power_frequency, but power_start event Thomas Renninger
2010-10-28 9:02 ` [PATCH 2/3] PERF(kernel): Cleanup power events Thomas Renninger
2010-10-28 11:17 ` Rafael J. Wysocki
2010-10-28 11:31 ` Rafael J. Wysocki [this message]
2010-10-28 11:37 ` Thomas Renninger
2010-10-28 9:02 ` [PATCH 3/3] PERF(userspace): Adjust perf timechart to the new " Thomas Renninger
2010-10-28 9:19 ` 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=201010281331.19503.rjw@sisk.pl \
--to=rjw@sisk.pl \
--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=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