From: Cyrill Gorcunov <gorcunov@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 01/14] [VOYAGER] x86: add {safe,hard}_smp_processor_id to smp_ops
Date: Tue, 14 Apr 2009 20:31:43 +0400 [thread overview]
Message-ID: <20090414163143.GB12888@lenovo> (raw)
In-Reply-To: <1239724300-16371-2-git-send-email-James.Bottomley@HansenPartnership.com>
[James Bottomley - Tue, Apr 14, 2009 at 10:51:27AM -0500]
| Not having apics, Voyager can't use the default apic implementation of
| these, it has to read from a special port in the VIC to get the
| processor ID, so abstract these functions in smp_ops to allow voyager
| to live simultaneously with the apic code.
|
| Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
| ---
| arch/x86/include/asm/smp.h | 13 +++++++++++--
| arch/x86/kernel/apic/apic.c | 5 -----
| arch/x86/kernel/apic/ipi.c | 2 +-
| arch/x86/kernel/smp.c | 7 +++++++
| arch/x86/xen/smp.c | 7 +++++++
| 5 files changed, 26 insertions(+), 8 deletions(-)
|
| diff --git a/arch/x86/include/asm/smp.h b/arch/x86/include/asm/smp.h
| index 19e0d88..aac866f 100644
| --- a/arch/x86/include/asm/smp.h
| +++ b/arch/x86/include/asm/smp.h
| @@ -60,6 +60,8 @@ struct smp_ops {
|
| void (*send_call_func_ipi)(const struct cpumask *mask);
| void (*send_call_func_single_ipi)(int cpu);
| + int (*hard_smp_processor_id)(void);
| + int (*safe_smp_processor_id)(void);
| };
|
| /* Globals due to paravirt */
| @@ -159,7 +161,11 @@ extern unsigned disabled_cpus __cpuinitdata;
| * so this is correct in the x86 case.
| */
| #define raw_smp_processor_id() (percpu_read(cpu_number))
| -extern int safe_smp_processor_id(void);
| +int apic_safe_smp_processor_id(void);
| +static inline int safe_smp_processor_id(void)
| +{
| + return smp_ops.safe_smp_processor_id();
| +}
|
| #elif defined(CONFIG_X86_64_SMP)
| #define raw_smp_processor_id() (percpu_read(cpu_number))
| @@ -185,7 +191,10 @@ static inline int logical_smp_processor_id(void)
|
| #endif
|
| -extern int hard_smp_processor_id(void);
| +static inline int hard_smp_processor_id(void)
| +{
| + return smp_ops.hard_smp_processor_id();
| +}
|
Hi James, wouldn't it break summit32 platform?
This snippet from summit_32.c
static void summit_init_apic_ldr(void)
{
unsigned long val, id;
int count = 0;
---> u8 my_id = (u8)hard_smp_processor_id();
u8 my_cluster = APIC_CLUSTER(my_id);
if we have CONFIG_SMP _not_ set smp_ops.hard_smp_processor_id
would be plain NULL deref (or linker warning)? I could be missing something...
Cyrill
next prev parent reply other threads:[~2009-04-14 16:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 15:51 [PATCH 00/14] convert voyager over to the x86 quirks model James Bottomley
2009-04-14 15:51 ` [PATCH 01/14] [VOYAGER] x86: add {safe,hard}_smp_processor_id to smp_ops James Bottomley
2009-04-14 15:51 ` [PATCH 02/14] [VOYAGER] x86/mca: make mca_nmi_hook external James Bottomley
2009-04-14 15:51 ` [PATCH 03/14] [VOYAGER] x86: add prefill_possible_map to x86_quirks James Bottomley
2009-04-14 15:51 ` [PATCH 04/14] [VOYAGER] x86: use boot_cpu_id instead of zero for checking boot processor James Bottomley
2009-04-14 15:51 ` [PATCH 05/14] [VOYAGER] x86/voyager: Move voyager detection to a new bootparam area James Bottomley
2009-04-14 15:51 ` [PATCH 06/14] [VOYAGER] x86: eliminate subarchitecture file setup_arch.h James Bottomley
2009-04-14 15:51 ` [PATCH 07/14] [VOYAGER] x86: eliminate subarchitecture file entry_arch.h James Bottomley
2009-04-14 15:51 ` [PATCH 08/14] [VOYAGER] x86: eliminate subarchitecture file do_timer.h James Bottomley
2009-04-14 15:51 ` [PATCH 09/14] [VOYAGER] x86: redo irq2 cascade setup James Bottomley
2009-04-14 15:51 ` [PATCH 10/14] [VOYAGER] x86: make disabling the apics functional instead of a flag James Bottomley
2009-04-14 15:51 ` [PATCH 11/14] [VOYAGER] x86/Voyager: add missing QIC call function single gate James Bottomley
2009-04-14 15:51 ` [PATCH 12/14] [VOYAGER] x86/Voyager: replace inline io area reads with readX accessors James Bottomley
2009-04-14 15:51 ` [PATCH 13/14] [VOYAGER] x86/voyager: remove direct use of pg0 in favour of early_ioremap() James Bottomley
2009-04-14 15:51 ` [PATCH 14/14] [VOYAGER] x86/Voyager: Plumb voyager back into the build James Bottomley
2009-04-14 17:09 ` [PATCH 10/14] [VOYAGER] x86: make disabling the apics functional instead of a flag Cyrill Gorcunov
2009-04-14 17:44 ` Cyrill Gorcunov
2009-04-15 12:51 ` James Bottomley
2009-04-15 14:12 ` Cyrill Gorcunov
2009-04-14 16:31 ` Cyrill Gorcunov [this message]
2009-04-14 16:54 ` [PATCH 01/14] [VOYAGER] x86: add {safe,hard}_smp_processor_id to smp_ops James Bottomley
2009-04-14 16:35 ` Jeremy Fitzhardinge
2009-04-14 16:57 ` James Bottomley
2009-04-14 16:27 ` [PATCH 00/14] convert voyager over to the x86 quirks model Joe Perches
2009-04-14 16:57 ` Ingo Molnar
2009-04-14 18:08 ` Ingo Molnar
2009-04-14 23:12 ` James Bottomley
2009-04-15 15:35 ` Ingo Molnar
2009-04-16 21:06 ` James Bottomley
2009-04-16 20:54 ` Jeff Garzik
2009-04-19 23:35 ` Ingo Molnar
2009-04-19 23:54 ` Jeff Garzik
2009-04-20 0:38 ` Ingo Molnar
2009-04-20 16:59 ` James Bottomley
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=20090414163143.GB12888@lenovo \
--to=gorcunov@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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®