From: Dave Jones <davej@redhat.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Steven Finney (Palm GBU)" <Steven.Finney@palm.com>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>
Subject: Re: Request for DIscussion: Cpufreq logging, and frequency floors
Date: Sun, 23 Oct 2011 20:01:59 -0400 [thread overview]
Message-ID: <20111024000158.GA19078@redhat.com> (raw)
In-Reply-To: <20111023114802.GA15272@sirena.org.uk>
On Sun, Oct 23, 2011 at 12:48:03PM +0100, Mark Brown wrote:
> On Fri, Oct 21, 2011 at 02:31:57PM -0700, Steven Finney (Palm GBU) wrote:
>
> > 2) The ability to keep a diagnostic log of all the frequency changes so,
> > e.g., it's possible to determine if bad behavior (e.g. dropouts) is
> > correlated with a low frequency.
>
> This is a really good and useful idea but it seems to me like it would
> be better done with the standard trace subsystem - that provides good
> facilities for enabling and disabling the trace as needed and would make
> it easy to tie in with the other subsystems that are in play.
Indeed. This sounds like the direction to go towards. Having played a little
with Steven Rostedt's kernelshark tool, I could see interesting things coming
from being able to correlate transitions with other system events graphically.
Dave
next prev parent reply other threads:[~2011-10-24 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 21:31 Request for DIscussion: Cpufreq logging, and frequency floors Steven Finney (Palm GBU)
2011-10-23 11:48 ` Mark Brown
2011-10-24 0:01 ` Dave Jones [this message]
2011-10-28 16:45 ` Steven Finney (Palm GBU)
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=20111024000158.GA19078@redhat.com \
--to=davej@redhat.com \
--cc=Steven.Finney@palm.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cpufreq@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox