From: ccross@google.com (Colin Cross)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: formalize an IPI for CPU wake-ups
Date: Mon, 6 Aug 2012 13:41:06 -0700 [thread overview]
Message-ID: <CAMbhsRRp429Fkk2-vEixt8OPW699ftVCaG+C83NWLvM2_jkOVw@mail.gmail.com> (raw)
In-Reply-To: <037601cd6fc9$f6e5fe30$e4b1fa90$%kim@samsung.com>
On Wed, Aug 1, 2012 at 2:42 AM, Kukjin Kim <kgene.kim@samsung.com> wrote:
> Stephen Boyd wrote:
>>
>> On 07/10/12 23:34, Kukjin Kim wrote:
>> > Stephen Boyd wrote:
>> >> Great. Kukjin Kim, can exynos use SGI0? It looks like exynos is the
>> only
>> >> one left to move to SGI0.
>> >>
>> > Yeah, EXYNOS can use SGI0 instead of SGI1 :)
>> >
>> >
>>
>> Russell, can we apply something like this?
>>
> Please feel free to add my ack on following change.
>
> Acked-by: Kukjin Kim <kgene.kim@samsung.com>
>
When testing coupled cpuidle on Exynos5, I found that sending an IPI
does not successfully wake up CPU1. CPU1 is in a wfe with interrupts
masked, not a wfi, so an interrupt is not able to wake it up. It
tends to wake up anyways because the next time a spin lock is
unlocked, often during a timer interrupt on CPU0, CPU0 executes an sev
which wakes up CPU1. You can see that the IPI is unnecessary by
removing the gic_raise_softirq and replacing it with dsb_sev().
next prev parent reply other threads:[~2012-08-06 20:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 15:54 [PATCH] ARM: formalize an IPI for CPU wake-ups Nicolas Pitre
2012-06-11 15:57 ` Russell King - ARM Linux
2012-06-11 16:44 ` Nicolas Pitre
2012-06-11 16:51 ` Russell King - ARM Linux
2012-06-11 17:18 ` Nicolas Pitre
2012-06-11 17:41 ` Stephen Boyd
2012-06-11 19:25 ` Russell King - ARM Linux
2012-06-20 16:32 ` Stephen Boyd
2012-07-11 6:34 ` Kukjin Kim
2012-07-30 18:19 ` Stephen Boyd
2012-08-01 9:42 ` Kukjin Kim
2012-08-06 20:41 ` Colin Cross [this message]
2012-08-07 17:00 ` Russell King - ARM Linux
2012-08-08 7:04 ` Shilimkar, Santosh
2012-08-08 10:39 ` Kukjin Kim
2012-08-08 6:52 ` Magnus Damm
2012-08-13 22:09 ` Stephen Boyd
2012-08-22 19:05 ` Stephen Boyd
2012-08-22 21:23 ` Magnus Damm
2012-08-29 7:21 ` Stephen Boyd
2012-09-08 14:47 ` Nicolas Pitre
2012-06-11 18:26 ` Russell King - ARM Linux
2012-06-11 18:40 ` Nicolas Pitre
2012-06-11 18:41 ` Russell King - ARM Linux
2012-06-11 19:11 ` Nicolas Pitre
2012-06-11 19:20 ` Russell King - ARM Linux
2012-06-11 19:56 ` Nicolas Pitre
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=CAMbhsRRp429Fkk2-vEixt8OPW699ftVCaG+C83NWLvM2_jkOVw@mail.gmail.com \
--to=ccross@google.com \
--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).