From: p2@debian.org (Peter 'p2' De Schrijver)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] cpuidle: allow per cpu latencies
Date: Thu, 5 Apr 2012 15:03:53 +0300 [thread overview]
Message-ID: <20120405120352.GL6489@apfelkorn> (raw)
In-Reply-To: <1333625136-22630-1-git-send-email-pdeschrijver@nvidia.com>
On 2012-04-05 14:25:23 (+0300), Peter De Schrijver <pdeschrijver@nvidia.com> wrote:
> On some systems (eg Tegra30) latencies for a given C state are not equal for
> all CPUs. Therefore we introduce a new per CPU structure which contains
> those parameters.
Sorry for sending this several times.
Cheers,
Peter.
next prev parent reply other threads:[~2012-04-05 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 11:25 [RFC PATCH] cpuidle: allow per cpu latencies Peter De Schrijver
2012-04-05 12:03 ` Peter 'p2' De Schrijver [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-05 10:44 Peter De Schrijver
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
2012-04-19 9:14 ` Daniel Lezcano
2012-04-19 10:23 ` Peter De Schrijver
2012-04-10 10:31 ` Peter 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=20120405120352.GL6489@apfelkorn \
--to=p2@debian.org \
--cc=linux-arm-kernel@lists.infradead.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).