linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anup Chenthamarakshan <anupc@chromium.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Dirk Brandewie <dirk.brandewie@gmail.com>,
	Sameer Nanda <snanda@chromium.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] intel_pstate: track and export frequency residency stats via sysfs.
Date: Wed, 10 Sep 2014 16:39:05 -0700	[thread overview]
Message-ID: <20140910233905.GA2439@google.com> (raw)
In-Reply-To: <1610826.tK4V65ABJD@vostro.rjw.lan>

On Thu, Sep 11, 2014 at 12:49:48AM +0200, Rafael J. Wysocki wrote:
> On Wednesday, September 10, 2014 03:15:08 PM Anup Chenthamarakshan wrote:
> > 
> > Tools like powertop and turbostat are not present by default on all systems,
> > so it is not always possible to use them :(
> 
> Which systems are you referring to in particular?

We're testing on Chrome OS devices (Chromebooks).

> 
> -- 
> I speak only for myself.
> Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2014-09-10 23:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09  0:10 [PATCH] intel_pstate: track and export frequency residency stats via sysfs Anup Chenthamarakshan
2014-09-09  5:03 ` Viresh Kumar
2014-09-09  5:32   ` Anup Chenthamarakshan
2014-09-09  6:26     ` Viresh Kumar
2014-09-09 23:31       ` Anup Chenthamarakshan
2014-09-10  6:49         ` Viresh Kumar
2014-09-09 15:15 ` Dirk Brandewie
2014-09-09 23:22   ` Anup Chenthamarakshan
2014-09-10 16:39     ` Dirk Brandewie
2014-09-10 22:15       ` Anup Chenthamarakshan
2014-09-10 22:49         ` Rafael J. Wysocki
2014-09-10 23:39           ` Anup Chenthamarakshan [this message]
2014-09-11  0:04             ` Rafael J. Wysocki
2014-09-11  1:04               ` Sameer Nanda
2014-09-11 15:37                 ` Dirk Brandewie

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=20140910233905.GA2439@google.com \
    --to=anupc@chromium.org \
    --cc=dirk.brandewie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=snanda@chromium.org \
    --cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).