From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: linux-next@vger.kernel.org, Mike Travis <travis@sgi.com>,
Alex Nixon <alex.nixon@citrix.com>
Subject: linux-next: manual merge of the cpus4096 tree
Date: Fri, 12 Sep 2008 15:18:19 +1000 [thread overview]
Message-ID: <20080912151819.c6e8fdfe.sfr@canb.auug.org.au> (raw)
Hi all,
Today's linux-next merge of the cpus4096 tree got a conflict in
include/asm-x86/smp.h between commit
93be71b672f167b1e8c23725114f86305354f0ac ("x86: add cpu hotplug hooks
into smp_ops") from the x86 tree and commit
ae74da38ccdad1c0d724fc9343b917bc63ed6fc3 ("x86: reduce stack requirements
for send_call_func_ipi") from the cpus4096 tree.
Just overlapping context. I fixed it up (see below) and can carry the
fix.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
diff --cc include/asm-x86/smp.h
index 6df2615,8eee4ef..0000000
--- a/include/asm-x86/smp.h
+++ b/include/asm-x86/smp.h
@@@ -55,12 -53,7 +55,12 @@@ struct smp_ops
void (*smp_send_stop)(void);
void (*smp_send_reschedule)(int cpu);
+ int (*cpu_up)(unsigned cpu);
+ int (*cpu_disable)(void);
+ void (*cpu_die)(unsigned int cpu);
+ void (*play_dead)(void);
+
- void (*send_call_func_ipi)(cpumask_t mask);
+ void (*send_call_func_ipi)(const cpumask_t *mask);
void (*send_call_func_single_ipi)(int cpu);
};
@@@ -125,22 -103,19 +125,22 @@@ static inline void arch_send_call_funct
static inline void arch_send_call_function_ipi(cpumask_t mask)
{
- smp_ops.send_call_func_ipi(mask);
+ smp_ops.send_call_func_ipi(&mask);
}
+void cpu_disable_common(void);
void native_smp_prepare_boot_cpu(void);
void native_smp_prepare_cpus(unsigned int max_cpus);
void native_smp_cpus_done(unsigned int max_cpus);
int native_cpu_up(unsigned int cpunum);
+int native_cpu_disable(void);
+void native_cpu_die(unsigned int cpu);
+void native_play_dead(void);
+void play_dead_common(void);
+
- void native_send_call_func_ipi(cpumask_t mask);
+ void native_send_call_func_ipi(const cpumask_t *mask);
void native_send_call_func_single_ipi(int cpu);
-extern int __cpu_disable(void);
-extern void __cpu_die(unsigned int cpu);
-
void smp_store_cpu_info(int id);
#define cpu_physical_id(cpu) per_cpu(x86_cpu_to_apicid, cpu)
next reply other threads:[~2008-09-12 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 5:18 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-19 1:08 linux-next: manual merge of the cpus4096 tree Stephen Rothwell
2008-07-16 2:47 Stephen Rothwell
2008-07-07 6:20 Stephen Rothwell
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=20080912151819.c6e8fdfe.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alex.nixon@citrix.com \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
/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