mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	Kevin Hilman <khilman@ti.com>, Len Brown <len.brown@intel.com>,
	Trinabh Gupta <g.trinabh@gmail.com>,
	Russell King <linux@arm.linux.org.uk>,
	Stephen Warren <swarren@wwwdotorg.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Deepthi Dharwar <deepthi@linux.vnet.ibm.com>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	Colin Cross <ccross@android.com>, Olof Johansson <olof@lixom.net>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Arjan van de Ven <arjan@linux.intel.com>
Subject: Re: [RFC PATCH] cpuidle: allow per cpu latencies
Date: Mon, 16 Apr 2012 18:34:56 +0300	[thread overview]
Message-ID: <20120416153456.GB514@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <20120410102857.GA22721@tbergstrom-lnx.Nvidia.com>

> 
> Maybe we also want to make the 'disabled' flag per CPU then or provide some
> other way the number of C states can be different per CPU?

What do you think about this? Do we also want to make the disabled flag per
CPU? Or how should we deal with a different number of C states per CPU?

Thanks,

Peter.

  reply	other threads:[~2012-04-16 15:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  9:53 Peter De Schrijver
2012-04-05 13:37 ` Arjan van de Ven
2012-04-06 10:32   ` Shilimkar, Santosh
2012-04-06 15:35     ` Daniel Lezcano
2012-04-10 10:28       ` Peter De Schrijver
2012-04-16 15:34         ` Peter De Schrijver [this message]
2012-04-19  9:14           ` Daniel Lezcano
2012-04-19 10:23             ` Peter De Schrijver
2012-04-10 10:31   ` Peter De Schrijver
2012-04-05 10:44 Peter De Schrijver
2012-04-05 11:25 Peter De Schrijver
2012-04-05 12:03 ` Peter 'p2' De Schrijver

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=20120416153456.GB514@tbergstrom-lnx.Nvidia.com \
    --to=pdeschrijver@nvidia.com \
    --cc=arjan@linux.intel.com \
    --cc=ccross@android.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=deepthi@linux.vnet.ibm.com \
    --cc=g.trinabh@gmail.com \
    --cc=khilman@ti.com \
    --cc=len.brown@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=olof@lixom.net \
    --cc=santosh.shilimkar@ti.com \
    --cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®