From: Dirk Behme <dirk.behme@googlemail.com>
To: linux-rt-users@vger.kernel.org
Cc: tglx@linutronix.de, David Brownell <david-b@pacbell.net>,
Daniel Walker <dwalker@mvista.com>,
Kevin Hilman <khilman@mvista.com>
Subject: [patch 2/4] ARM: NO_HZ support
Date: Wed, 20 Dec 2006 10:20:56 +0100 [thread overview]
Message-ID: <45890078.4070606@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 150 bytes --]
ARM: NO_HZ support
This is an update of the initial patch from Daniel Walker
and Kevin Hilman.
Signed-off-by: Dirk Behme <dirk.behme_at_gmail.com>
[-- Attachment #2: arm-no-hz-patch.txt --]
[-- Type: text/plain, Size: 469 bytes --]
Index: linux-2.6.20-rc1/arch/arm/Kconfig
===================================================================
--- linux-2.6.20-rc1.orig/arch/arm/Kconfig
+++ linux-2.6.20-rc1/arch/arm/Kconfig
@@ -529,6 +529,7 @@ source kernel/Kconfig.preempt
config NO_IDLE_HZ
bool "Dynamic tick timer"
+ depends on !GENERIC_CLOCKEVENTS
help
Select this option if you want to disable continuous timer ticks
and have them programmed to occur as required. This option saves
reply other threads:[~2006-12-20 9:20 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=45890078.4070606@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=david-b@pacbell.net \
--cc=dwalker@mvista.com \
--cc=khilman@mvista.com \
--cc=linux-rt-users@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.