From: zhanzhenbo@gmail.com (Steve zhan)
To: linux-arm-kernel@lists.infradead.org
Subject: Question: ARM: local timers: add num_possible_cpus() in local_timer_register()
Date: Mon, 14 Jan 2013 21:33:45 +0800 [thread overview]
Message-ID: <20130114133345.GA26701@android11.spreadtrum.com> (raw)
Hi Marc,
Do you think we should add num_possible_cpus() in
local_timer_register() function, When core number is
> 1, then reutrn TRUE? Enable the local timer only if
we have more than one CPU, if the current config is
SMP and setup_max_cpus >= 1, but if smp_init_cpus in
platform code have set cpu possible value to One(that
maybe read number from scu or other hardware), then
percpu_timer_setup in smp_prepare_cpus have no chance
to be called.
For local timer, because local_timer_register have
return 1, that will miss global timer register.
Could you pls check it?
Regards,
Steve.
next reply other threads:[~2013-01-14 13:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 13:33 Steve zhan [this message]
2013-01-14 13:35 ` Question: ARM: local timers: add num_possible_cpus() in local_timer_register() Russell King - ARM Linux
2013-01-14 14:19 ` Marc Zyngier
2013-01-14 14:31 ` steve.zhan
2013-01-14 15:21 ` Marc Zyngier
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=20130114133345.GA26701@android11.spreadtrum.com \
--to=zhanzhenbo@gmail.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).