linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Doug Smythies <doug.smythies@gmail.com>,
	len.brown@intel.com, dsmythies@telus.net,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2] tools/power/x86: Debug utility for intel_pstate driver
Date: Tue, 14 Feb 2017 06:36:22 -0800	[thread overview]
Message-ID: <1487082982.21310.0.camel@linux.intel.com> (raw)
In-Reply-To: <4440842.OSZWjPAjve@aspire.rjw.lan>

On Tue, 2017-02-14 at 12:15 +0100, Rafael J. Wysocki wrote:
> On Monday, February 13, 2017 08:19:00 PM Srinivas Pandruvada wrote:
> > On Mon, 2017-02-13 at 15:19 -0800, Doug Smythies wrote:
> > > This utility can be used to debug and tune the performance of the
> > > intel_pstate driver.
> > > This utility can be used in two ways:
> > > - If there is Linux trace file with pstate_sample events enabled,
> > > then
> > > this utility can parse the trace file and generate performance
> > > plots.
> > > - If user has not specified a trace file as input via command
> > > line
> > > parameters, then this utility enables and collects trace data for
> > > a
> > > user
> > > specified interval and generates performance plots.
> > > 
> > > Signed-off-by: Doug Smythies <dsmythies@telus.net>
> > 
> > I am fine with this version. But since Rafael may have already
> > prepared
> > for pull request, so it is up to him.
> 
> I can replace your version with this one if that's OK.
Please do that.

Thanks,
Srinivas

      reply	other threads:[~2017-02-14 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 23:19 [PATCH v2] tools/power/x86: Debug utility for intel_pstate driver Doug Smythies
2017-02-14  4:19 ` Srinivas Pandruvada
2017-02-14 11:15   ` Rafael J. Wysocki
2017-02-14 14:36     ` Srinivas Pandruvada [this message]

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=1487082982.21310.0.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=doug.smythies@gmail.com \
    --cc=dsmythies@telus.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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).