From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: John Stultz <john.stultz@linaro.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linaro-dev >> Lists Linaro-dev" <linaro-dev@lists.linaro.org>
Subject: [resend] Timer broadcast question
Date: Tue, 19 Feb 2013 19:02:29 +0100 [thread overview]
Message-ID: <5123BE35.8070902@linaro.org> (raw)
Hi,
I am working on identifying the different wakeup sources from the
interrupts and I have a question regarding the timer broadcast.
The broadcast timer is setup to the next event and that will wake up any
idle cpu belonging to the "broadcast cpumask", right ?
The cpu which has been woken up will look for each cpu the next-event
and send an IPI to wake it up.
Although, it is possible the sender of this IPI may not be concerned by
the timer expiration and has been woken up just for sending the IPI, right ?
If this is correct, is it possible to setup the timer irq affinity to a
cpu which will be concerned by the timer expiration ? so we prevent an
unnecessary wake up for a cpu.
For example, let's say we have a 2 cpus system.
cpu0, cpu1 are idle
The next event is for cpu1 but cpu0 is wake up by the broadcast timer,
after checking it has nothing to do except send a IPI_TIMER to cpu1 and
then goes to idle again.
Wouldn't be worth to set the broadcast timer affinity to cpu1, so cpu0
is not wake up ?
Did I missed something or does it sound correct ?
Thanks
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next reply other threads:[~2013-02-19 18:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 18:02 Daniel Lezcano [this message]
2013-02-19 18:10 ` [resend] Timer broadcast question Thomas Gleixner
2013-02-19 18:21 ` Daniel Lezcano
2013-02-19 22:46 ` Andy Lutomirski
2013-02-20 10:09 ` Thomas Gleixner
2013-02-21 6:19 ` Santosh Shilimkar
2013-02-21 6:19 ` Santosh Shilimkar
2013-02-21 9:01 ` Daniel Lezcano
2013-02-21 9:01 ` Daniel Lezcano
2013-02-21 9:14 ` Santosh Shilimkar
2013-02-21 9:14 ` Santosh Shilimkar
2013-02-21 22:01 ` [PATCH 1/2] time : pass broadcast device parameter Daniel Lezcano
2013-02-21 22:01 ` Daniel Lezcano
2013-02-21 22:01 ` [PATCH 2/2][RFC] time : set broadcast irq affinity Daniel Lezcano
2013-02-21 22:01 ` Daniel Lezcano
2013-02-22 17:55 ` Jacob Pan
2013-02-22 17:55 ` Jacob Pan
2013-02-22 18:45 ` Thomas Gleixner
2013-02-22 18:45 ` Thomas Gleixner
2013-02-25 22:50 ` Daniel Lezcano
2013-02-25 22:50 ` Daniel Lezcano
2013-02-25 23:00 ` Jacob Pan
2013-02-25 23:00 ` Jacob Pan
2013-02-26 8:45 ` [PATCH 1/2] time : pass broadcast device parameter Viresh Kumar
2013-02-26 8:45 ` Viresh Kumar
2013-02-26 11:30 ` Daniel Lezcano
2013-02-26 11:30 ` Daniel Lezcano
2013-02-26 11:31 ` Daniel Lezcano
2013-02-26 11:31 ` Daniel Lezcano
2013-02-26 12:14 ` Viresh Kumar
2013-02-26 12:14 ` Viresh Kumar
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=5123BE35.8070902@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=fweisbec@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.