All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: David Rientjes <rientjes@google.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"x86@kernel.org" <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jerry Hoemann <jerry.hoemann@hp.com>
Subject: Re: [PATCH] x86, apic: clean up handling of boot_cpu_physical_apicid in boot process
Date: Wed, 5 Feb 2014 11:38:24 -0500	[thread overview]
Message-ID: <20140205163824.GF6042@redhat.com> (raw)
In-Reply-To: <52E5CA8D.7000602@jp.fujitsu.com>

On Mon, Jan 27, 2014 at 11:55:09AM +0900, HATAYAMA Daisuke wrote:

[..]
> ``bsp'' and ``boot cpu'' are different, but certainly they are close
> for most of people who don't need to focus the difference.

I agree. Especially this difference is becoming visible in kdump
context where we skip BIOS and can trigger a fresh boot on an AP.

Hatayama, I think distinguishing BSP and boot cpu makes sense and
we also need to find a way to export this information to user
space. So that we can figure out who is BSP and tell second kernel
not to bring up that cpu.

Initially we thought that cpu with "initial apicid" 0 is BSP. But
Jerry from HP is reporting that on some of the machines he has, BSP
does not have to have apic id 0.

If that's the case, we don't have a reliable way to figure out which is
BSP in the system. Or am I missing something?

Thanks
Vivek

  parent reply	other threads:[~2014-02-05 16:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16  9:40 [PATCH] x86, apic: clean up handling of boot_cpu_physical_apicid in boot process HATAYAMA Daisuke
2014-01-26  4:02 ` David Rientjes
2014-01-27  2:55   ` HATAYAMA Daisuke
2014-01-27 23:58     ` David Rientjes
2014-02-05 16:38     ` Vivek Goyal [this message]
2014-02-05 17:09       ` Vivek Goyal
2014-02-05 16:40 ` Vivek Goyal

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=20140205163824.GF6042@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=hpa@zytor.com \
    --cc=jerry.hoemann@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rientjes@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.