From: Adrian Bunk <bunk@stusta.de>
To: James.Bottomley@HansenPartnership.com
Cc: linux-kernel@vger.kernel.org
Subject: [2.6 patch] Voyager: remove smp_tune_scheduling() FIXME
Date: Tue, 28 Nov 2006 02:28:42 +0100 [thread overview]
Message-ID: <20061128012842.GV15364@stusta.de> (raw)
smp_tune_scheduling() does no longer do anything that is required
for Voyager.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.19-rc6-mm1/arch/i386/mach-voyager/voyager_smp.c.old 2006-11-27 23:51:54.000000000 +0100
+++ linux-2.6.19-rc6-mm1/arch/i386/mach-voyager/voyager_smp.c 2006-11-27 23:52:03.000000000 +0100
@@ -709,10 +709,6 @@
* schedule at the moment */
//global_irq_holder = boot_cpu_id;
- /* FIXME: Need to do something about this but currently only works
- * on CPUs with a tsc which none of mine have.
- smp_tune_scheduling();
- */
smp_store_cpu_info(boot_cpu_id);
printk("CPU%d: ", boot_cpu_id);
print_cpu_info(&cpu_data[boot_cpu_id]);
next reply other threads:[~2006-11-28 1:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 1:28 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-11 13:49 [2.6 patch] Voyager: remove smp_tune_scheduling() FIXME Adrian Bunk
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=20061128012842.GV15364@stusta.de \
--to=bunk@stusta.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@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