From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 0/2] ARM: MPIDR linearization
Date: Wed, 12 Jun 2013 09:55:49 -0600 [thread overview]
Message-ID: <51B89A05.6020503@wwwdotorg.org> (raw)
In-Reply-To: <20130612090729.GA20236@e102568-lin.cambridge.arm.com>
On 06/12/2013 03:07 AM, Lorenzo Pieralisi wrote:
> On Tue, Jun 11, 2013 at 05:48:53PM +0100, Stephen Warren wrote:
>> On 06/11/2013 10:22 AM, Lorenzo Pieralisi wrote:
>>> Hi Stephen,
>>>
>>> On Tue, Jun 11, 2013 at 04:56:43PM +0100, Stephen Warren wrote:
>>>> On 06/11/2013 03:58 AM, Lorenzo Pieralisi wrote:
>>>>> Hi Russell, all,
>>>>>
>>>>> even though I think this set is ready to get merged, it would be great
>>>>> if we can test it on as many platforms as possible since it touches core
>>>>> suspend/resume operations on ARM platforms relying on CONFIG_ARM_CPU_SUSPEND,
>>>>> and there are many.
>>>>
>>>> FWIW, I booted a Tegra system with these patches applied and didn't see
>>>> any issue in very brief testing. I'm not sure what targeted testing
>>>> would be useful?
>>>
>>> That's great thanks. CPUidle deep C-states (when CPUs resume from reset
>>> through cpu_resume) are the main triggers of this code, so you should be
>>> running with them enabled to test it.
>>
>> OK, in that case I believe I tested that; I had our "LP2" CPU
>> power-management mode enabled as always, and that powers off the CPUs
>> and resumes them, and didn't see any issue.
>
> Great, thanks, I guess this also means you did not notice any suspicious
> warnings at boot (ie "Large number of MPIDR hash buckets detected").
I didn't, although I didn't look that hard for them!
> Can I add your tested-by please ?
Sure.
next prev parent reply other threads:[~2013-06-12 15:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 15:22 [RFC PATCH v2 0/2] ARM: MPIDR linearization Lorenzo Pieralisi
2013-06-06 15:22 ` [RFC PATCH v2 1/2] ARM: kernel: build MPIDR hash function data structure Lorenzo Pieralisi
2013-06-06 15:22 ` [RFC PATCH v2 2/2] ARM: kernel: implement stack pointer save array through MPIDR hashing Lorenzo Pieralisi
2013-06-11 9:58 ` [RFC PATCH v2 0/2] ARM: MPIDR linearization Lorenzo Pieralisi
2013-06-11 15:56 ` Stephen Warren
2013-06-11 16:12 ` Nicolas Pitre
2013-06-11 16:22 ` Lorenzo Pieralisi
2013-06-11 16:48 ` Stephen Warren
2013-06-12 9:07 ` Lorenzo Pieralisi
2013-06-12 15:55 ` Stephen Warren [this message]
2013-06-11 15:58 ` Nicolas Pitre
2013-06-19 15:59 ` Lorenzo Pieralisi
2013-06-19 16:05 ` Nicolas Pitre
2013-06-12 8:36 ` Shawn Guo
2013-06-12 9:13 ` Lorenzo Pieralisi
2013-06-12 11:33 ` Shawn Guo
2013-06-19 16:43 ` Lorenzo Pieralisi
2013-06-20 0:43 ` Shawn Guo
2013-06-20 14:57 ` Lorenzo Pieralisi
2013-06-19 20:41 ` Kevin Hilman
2013-06-20 10:19 ` Lorenzo Pieralisi
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=51B89A05.6020503@wwwdotorg.org \
--to=swarren@wwwdotorg.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 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.