From: Ashok Raj <ashok.raj@intel.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, nickpiggin@yahoo.com.au
Subject: recent sched.c broke cpu hotplug
Date: Thu, 23 Jun 2005 14:30:03 -0700 [thread overview]
Message-ID: <20050623143003.A25031@unix-os.sc.intel.com> (raw)
Hi Andrew
trivial fix, this is required for getting cpu hotplug to work. These
functions are called during cpu down, but marked __init instead of __devinit.
--
Cheers,
Ashok Raj
- Open Source Technology Center
Some functions should be devinit for cpu hotplug purpose.
Signed-off-by: Ashok Raj <ashok.raj@intel.com>
-----------------------------------------------------
kernel/sched.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
Index: linux-2.6.12-mm1/kernel/sched.c
===================================================================
--- linux-2.6.12-mm1.orig/kernel/sched.c
+++ linux-2.6.12-mm1/kernel/sched.c
@@ -5207,7 +5207,7 @@ __setup("migration_factor=", setup_migra
* Estimated distance of two CPUs, measured via the number of domains
* we have to pass for the two CPUs to be in the same span:
*/
-__init static unsigned long domain_distance(int cpu1, int cpu2)
+__devinit static unsigned long domain_distance(int cpu1, int cpu2)
{
unsigned long distance = 0;
struct sched_domain *sd;
@@ -5417,7 +5417,7 @@ measure_cost(int cpu1, int cpu2, void *c
return cost1 - cost2;
}
-__init static unsigned long long measure_migration_cost(int cpu1, int cpu2)
+__devinit static unsigned long long measure_migration_cost(int cpu1, int cpu2)
{
unsigned long long max_cost = 0, fluct = 0, avg_fluct = 0;
unsigned int max_size, size, size_found = 0;
next reply other threads:[~2005-06-23 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 21:30 Ashok Raj [this message]
2005-06-24 7:00 ` 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=20050623143003.A25031@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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
all inboxes | Powered by JetHome®