From: "K.R. Foley" <kr@cybsft.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.13-rc6-rt15 won't compile without HR-Timers
Date: Wed, 24 Aug 2005 12:05:47 -0500 [thread overview]
Message-ID: <430CA8EB.3070105@cybsft.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 128 bytes --]
Ingo,
Without the attached patch 2.6.13-rc6-rt15 won't compile for me with
CONFIG_HIGH_RES_TIMERS not configured.
--
kr
[-- Attachment #2: nohrtfix.patch --]
[-- Type: text/x-patch, Size: 1291 bytes --]
--- linux-2.6.13/include/linux/timer.h.orig 2005-08-24 11:15:22.000000000 -0500
+++ linux-2.6.13/include/linux/timer.h 2005-08-24 11:15:35.000000000 -0500
@@ -76,6 +76,7 @@
#ifdef CONFIG_HIGH_RES_TIMERS
extern void add_hres_timer_us(struct timer_list *timer, unsigned long usec);
+extern void init_hrtimers(void);
#else
#define add_hres_timer_us(t,exp) mod_timer(t,(exp*HZ)/1000000)
#endif
@@ -125,7 +126,6 @@
#define del_singleshot_timer_sync(t) del_timer_sync(t)
extern void init_timers(void);
-extern void init_hrtimers(void);
extern void run_local_timers(void);
extern void it_real_fn(unsigned long);
--- linux-2.6.13/kernel/timer.c.orig 2005-08-24 11:16:04.000000000 -0500
+++ linux-2.6.13/kernel/timer.c 2005-08-24 11:06:32.000000000 -0500
@@ -1920,9 +1920,9 @@
.notifier_call = timer_cpu_notify,
};
+#ifdef CONFIG_HIGH_RES_TIMERS
void __init init_hrtimers(void)
{
-#ifdef CONFIG_HIGH_RES_TIMERS
open_softirq(HRTIMER_SOFTIRQ,
(void (*)(struct softirq_action*))hrtimers_expire_timers,
NULL);
@@ -1931,8 +1931,8 @@
printk("arch_cycles_per_jiffy: %ld\n", arch_cycles_per_jiffy);
printk("hr_max_jiffies_expiry: %d\n", hr_max_jiffies_expiry);
printk("hr_max_expiry: %d\n", hr_max_expiry);
-#endif
}
+#endif
void __init init_timers(void)
{
next reply other threads:[~2005-08-24 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 17:05 K.R. Foley [this message]
2005-08-25 5:53 ` 2.6.13-rc6-rt15 won't compile without HR-Timers Ingo Molnar
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=430CA8EB.3070105@cybsft.com \
--to=kr@cybsft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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