From: Ingo Molnar <mingo@elte.hu>
To: Avi Kivity <avi@qumranet.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] KVM, hotplug: export register_cpu_notifier
Date: Wed, 7 Feb 2007 10:19:13 +0100 [thread overview]
Message-ID: <20070207091913.GA15384@elte.hu> (raw)
In-Reply-To: <45C997F1.9060102@qumranet.com>
* Avi Kivity <avi@qumranet.com> wrote:
> >-#ifdef CONFIG_HOTPLUG_CPU
> >-
> > EXPORT_SYMBOL(register_cpu_notifier);
> >
> >+#ifdef CONFIG_HOTPLUG_CPU
> >+
> > void unregister_cpu_notifier(struct notifier_block *nb)
> > {
> > mutex_lock(&cpu_add_remove_lock);
> >
>
> This is broken: register_cpu_notifier() is __cpuinit, which means it
> disappears at module time if !CONFIG_CPU_HOTPLUG.
>
> I submitted a hackaround to Andrew some time ago with the suspend
> patchset.
ok. What does your patch do - turns it into an inline? I fixed it up in
-rt via the patch below.
Ingo
---------------------->
Subject: [patch] KVM: export register_cpu_notifier
From: Ingo Molnar <mingo@elte.hu>
KVM-trunk uses register_cpu_notifier() but it's not exported
on CONFIG_HOTPLUG_CPU. Make it a nop inline.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
include/linux/cpu.h | 6 +++++-
kernel/cpu.c | 4 ----
2 files changed, 5 insertions(+), 5 deletions(-)
Index: linux/include/linux/cpu.h
===================================================================
--- linux.orig/include/linux/cpu.h
+++ linux/include/linux/cpu.h
@@ -49,10 +49,14 @@ struct notifier_block;
#ifdef CONFIG_SMP
/* Need to know about CPUs going up/down? */
-extern int register_cpu_notifier(struct notifier_block *nb);
#ifdef CONFIG_HOTPLUG_CPU
+extern int register_cpu_notifier(struct notifier_block *nb);
extern void unregister_cpu_notifier(struct notifier_block *nb);
#else
+static inline int register_cpu_notifier(struct notifier_block *nb)
+{
+ return 0;
+}
static inline void unregister_cpu_notifier(struct notifier_block *nb)
{
}
Index: linux/kernel/cpu.c
===================================================================
--- linux.orig/kernel/cpu.c
+++ linux/kernel/cpu.c
@@ -63,8 +63,6 @@ void unlock_cpu_hotplug(void)
}
EXPORT_SYMBOL_GPL(unlock_cpu_hotplug);
-#endif /* CONFIG_HOTPLUG_CPU */
-
/* Need to know about CPUs going up/down? */
int __cpuinit register_cpu_notifier(struct notifier_block *nb)
{
@@ -75,8 +73,6 @@ int __cpuinit register_cpu_notifier(stru
return ret;
}
-#ifdef CONFIG_HOTPLUG_CPU
-
EXPORT_SYMBOL(register_cpu_notifier);
void unregister_cpu_notifier(struct notifier_block *nb)
next prev parent reply other threads:[~2007-02-07 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 8:16 [patch] KVM, hotplug: export register_cpu_notifier Ingo Molnar
2007-02-07 9:12 ` Avi Kivity
2007-02-07 9:19 ` Ingo Molnar [this message]
2007-02-07 9:34 ` Avi Kivity
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=20070207091913.GA15384@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=avi@qumranet.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