From: Jes Sorensen <jes@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] [patch] 2.4 arch/ia64/kernel/smpboot.c
Date: Wed, 26 Mar 2003 16:27:55 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705320@msgid-missing> (raw)
Hi,
A small patch for 2.4 that stops the kernel from trying to syncrhonize
ITC clocks between CPUs if we know that the ITC isn't synchronized
across the backplane.
The patch is relative to 2.4.21-pre5-bjorn, but I believe it should
apply directly to 2.5.x as well.
Cheers,
Jes
--- ../linux-2.4.20-021210/arch/ia64/kernel/smpboot.c Tue Mar 11 11:23:49 2003
+++ arch/ia64/kernel/smpboot.c Wed Mar 26 06:19:17 2003
@@ -334,12 +334,15 @@
smp_setup_percpu_timer();
- /*
- * Synchronize the ITC with the BP
- */
- Dprintk("Going to syncup ITC with BP.\n");
+ if (!(sal_platform_features & IA64_SAL_PLATFORM_FEATURE_ITC_DRIFT)) {
+ /*
+ * Synchronize the ITC with the BP
+ */
+ Dprintk("Going to syncup ITC with BP.\n");
+
+ ia64_sync_itc(0);
+ }
- ia64_sync_itc(0);
/*
* Get our bogomips.
*/
next reply other threads:[~2003-03-26 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 16:27 Jes Sorensen [this message]
2003-03-27 20:39 ` [Linux-ia64] [patch] 2.4 arch/ia64/kernel/smpboot.c David Mosberger
2003-04-16 22:49 ` Bjorn Helgaas
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=marc-linux-ia64-105590723705320@msgid-missing \
--to=jes@wildopensource.com \
--cc=linux-ia64@vger.kernel.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