From: slash.tmp@free•fr (Mason)
To: linux-arm-kernel@lists•infradead.org
Subject: Dropping "depends on SMP" for HAVE_ARM_TWD
Date: Thu, 26 Mar 2015 14:57:29 +0100 [thread overview]
Message-ID: <55141049.3040706@free.fr> (raw)
Hello everyone,
In http://thread.gmane.org/gmane.linux.ports.arm.kernel/389931/focus=392348
Stephen Boyd wrote:
> I don't see any problem with the TWD dropping the dependency on SMP.
> The code should work the same on a UP configuration [...]
However, this commit seems to imply some kind of limitation:
commit 904464b91eca8c665acea033489225af02eeb75a
Author: Shawn Guo <shawn.guo@linaro•org>
Date: Fri Feb 22 14:01:42 2013 +0100
ARM: 7655/1: smp_twd: make twd_local_timer_of_register() no-op for nosmp
When booting a SMP build kernel with nosmp on kernel cmdline, the
following fat warning will be hit.
------------[ cut here ]------------
WARNING: at arch/arm/kernel/smp_twd.c:345
twd_local_timer_of_register+0x7c/0x90()
twd_local_timer_of_register failed (-6)
Modules linked in:
Backtrace: [snip]
I would like to be able to use the TWD on a UP system (Cortex A9 MPcore
with a single core).
Is it possible to revert commit 904464b9, and drop "depends on SMP"
from the "config HAVE_ARM_TWD" definition?
Are there UP systems that simply don't have a TWD?
Regards.
reply other threads:[~2015-03-26 13:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55141049.3040706@free.fr \
--to=slash.tmp@free$(echo .)fr \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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