All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
	"Brown, Len" <len.brown@intel.com>,
	"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
	Arjan van de Ven <arjan@linux.intel.com>,
	LKP ML <lkp@linux.intel.com>
Subject: Re: bltk-game regressions on snb laptop
Date: Fri, 19 Apr 2013 22:43:32 +0800	[thread overview]
Message-ID: <51715814.4080209@intel.com> (raw)
In-Reply-To: <CAKohpongtqt0Sdc95TTrJ+s5A3Xt7df+SmtBZNyHzQKtARLxKA@mail.gmail.com>

On 04/19/2013 08:23 PM, Viresh Kumar wrote:
> So you get better performance without my patch because we don't allocate
> any struct cpufreq_policy for any of the cpus leaving first one. And so only
> manage freq change for it and all other cpus stay at max power..
> 
> So, we clearly need to know why don't we want to have all cpus set in
> policy->cpus, when they actually share clock line?

AFAIK, That because our p-state is HW coordinated. For further info,
Maybe Arjan and Len can explain more.

-- 
Thanks
    Alex

  reply	other threads:[~2013-04-19 14:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16  7:14 bltk-game regressions on snb laptop Alex Shi
2013-04-17 16:34 ` Rafael J. Wysocki
2013-04-18  0:23   ` Alex Shi
2013-04-17 16:46 ` Viresh Kumar
2013-04-18  0:48   ` Alex Shi
2013-04-18  4:26     ` Viresh Kumar
2013-04-18  4:36       ` Viresh Kumar
2013-04-18  5:24         ` Alex Shi
2013-04-18  5:16       ` Alex Shi
2013-04-18  5:37         ` Viresh Kumar
2013-04-18  6:16           ` Alex Shi
2013-04-18  8:54           ` Alex Shi
2013-04-18 10:01             ` Viresh Kumar
2013-04-19 10:00               ` Alex Shi
2013-04-19 12:23                 ` Viresh Kumar
2013-04-19 14:43                   ` Alex Shi [this message]
2013-04-19 15:44                   ` Arjan van de Ven

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=51715814.4080209@intel.com \
    --to=alex.shi@intel.com \
    --cc=arjan@linux.intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=lkp@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.