From: Vivek Goyal <vgoyal@redhat.com>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: hpa@linux.intel.com, ebiederm@xmission.com,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
bp@alien8.de, akpm@linux-foundation.org, fengguang.wu@intel.com,
jingbai.ma@hp.com
Subject: Re: [PATCH v2 1/2] x86, apic: Add boot_cpu_is_bsp() to check if boot cpu is BSP
Date: Tue, 15 Oct 2013 15:12:17 -0400 [thread overview]
Message-ID: <20131015191217.GN31215@redhat.com> (raw)
In-Reply-To: <20131015054322.13666.31465.stgit@localhost6.localdomain6>
On Tue, Oct 15, 2013 at 02:43:22PM +0900, HATAYAMA Daisuke wrote:
> Kexec can enter the kdump 2nd kernel on AP if crash happens on AP. To
> check if boot cpu is BSP, introduce a helper function
> boot_cpu_is_bsp().
>
> Signed-off-by: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
> ---
> arch/x86/include/asm/mpspec.h | 7 +++++++
> arch/x86/kernel/apic/apic.c | 16 ++++++++++++++++
> arch/x86/kernel/setup.c | 2 ++
> 3 files changed, 25 insertions(+)
>
> diff --git a/arch/x86/include/asm/mpspec.h b/arch/x86/include/asm/mpspec.h
> index 626cf70..54d5f98 100644
> --- a/arch/x86/include/asm/mpspec.h
> +++ b/arch/x86/include/asm/mpspec.h
> @@ -47,11 +47,18 @@ extern int mp_bus_id_to_type[MAX_MP_BUSSES];
> extern DECLARE_BITMAP(mp_bus_not_pci, MAX_MP_BUSSES);
>
> extern unsigned int boot_cpu_physical_apicid;
> +extern bool boot_cpu_is_bsp;
> extern unsigned int max_physical_apicid;
> extern int mpc_default_type;
> extern unsigned long mp_lapic_addr;
>
> #ifdef CONFIG_X86_LOCAL_APIC
> +extern void boot_cpu_is_bsp_init(void);
> +#else
> +static inline void boot_cpu_is_bsp_init(void) { };
> +#endif
> +
> +#ifdef CONFIG_X86_LOCAL_APIC
> extern int smp_found_config;
> #else
> # define smp_found_config 0
> diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
> index a7eb82d..62ee365 100644
> --- a/arch/x86/kernel/apic/apic.c
> +++ b/arch/x86/kernel/apic/apic.c
> @@ -64,6 +64,12 @@ unsigned disabled_cpus;
> unsigned int boot_cpu_physical_apicid = -1U;
>
> /*
[..]
> + * Indicates whether the processor that is doing the boot up, is BSP
> + * processor or not.
> + */
> +bool boot_cpu_is_bsp;
Should we set it to true by default? I think in most of the cases boot cpu
is going to be bsp too?
> +
> +/*
> * The highest APIC ID seen during enumeration.
> */
> unsigned int max_physical_apicid;
> @@ -2589,3 +2595,13 @@ static int __init lapic_insert_resource(void)
> * that is using request_resource
> */
> late_initcall(lapic_insert_resource);
> +
> +void __init boot_cpu_is_bsp_init(void)
> +{
> + if (cpu_has_apic) {
> + u32 l, h;
> +
> + rdmsr_safe(MSR_IA32_APICBASE, &l, &h);
> + boot_cpu_is_bsp = (l & MSR_IA32_APICBASE_BSP) ? true : false;
I came across following thread.
https://lkml.org/lkml/2012/4/18/370
Can we hit above read msr on old P5 class machines? Or is it safe to
call unconditionally.
Thanks
Vivek
next prev parent reply other threads:[~2013-10-15 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 5:43 [PATCH v2 0/2] x86, apic, kdump: Disable BSP if boot cpu is AP HATAYAMA Daisuke
2013-10-15 5:43 ` [PATCH v2 1/2] x86, apic: Add boot_cpu_is_bsp() to check if boot cpu is BSP HATAYAMA Daisuke
2013-10-15 19:12 ` Vivek Goyal [this message]
2013-10-16 0:52 ` HATAYAMA Daisuke
2013-10-15 5:43 ` [PATCH v2 2/2] x86, apic: Disable BSP if boot cpu is AP HATAYAMA Daisuke
2013-10-15 19:30 ` Vivek Goyal
2013-10-16 1:26 ` HATAYAMA Daisuke
2013-10-18 17:36 ` Vivek Goyal
2013-10-22 11:02 ` HATAYAMA Daisuke
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=20131015191217.GN31215@redhat.com \
--to=vgoyal@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=d.hatayama@jp.fujitsu.com \
--cc=ebiederm@xmission.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@linux.intel.com \
--cc=jingbai.ma@hp.com \
--cc=kexec@lists.infradead.org \
--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