public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
	d.hatayama@jp.fujitsu.com, hpa@linux.intel.com,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/bsp-hotplug] x86, apic: Disable BSP if boot cpu is AP
Date: Mon, 11 Nov 2013 11:54:00 -0800	[thread overview]
Message-ID: <528135D8.3040205@zytor.com> (raw)
In-Reply-To: <20131012174206.GD18437@gmail.com>

On 10/12/2013 10:42 AM, Ingo Molnar wrote:
> 
> * H. Peter Anvin <hpa@zytor.com> wrote:
> 
>> On 10/09/2013 04:16 PM, tip-bot for HATAYAMA Daisuke wrote:
>>> Commit-ID:  1d79e607332d67d9132c176d99b5e7fabe1b6b7f
>>> Gitweb:     http://git.kernel.org/tip/1d79e607332d67d9132c176d99b5e7fabe1b6b7f
>>> Author:     HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
>>> AuthorDate: Thu, 29 Aug 2013 18:28:04 +0900
>>> Committer:  H. Peter Anvin <hpa@linux.intel.com>
>>> CommitDate: Wed, 9 Oct 2013 15:41:11 -0700
>>>
>>> x86, apic: Disable BSP if boot cpu is AP
>>
>> This patch seems to trigger build failures in some configurations.
>> Specifically:
>>
>> (.init.text+0x1307): undefined reference to `boot_cpu_is_bsp_init'
>>
>> Unfortunately I don't have the specific configuration which triggers the 
>> failure, as this was discovered by Fengguang's robot.
> 
> I have triggered that too and have such a config, it's attached.

Okay, thinking about this again, this patchset is in fact broken on:

1. Any configuration which has CONFIG_SMP=n and CONFIG_X86_UP_APIC=n.

This is a built-time problem.

2. Any CPU which is old enough that MSR_IA32_APICBASE doesn't exist.

This is a fatal runtime bug.

3. Any clustered solution which involves a third-party cluster
controller such that MSR_IA32_APICBASE may not reflect the reality of
the system.

This is a less critical issue as "all" it ought to make happen is to
disable some CPUs which didn't need it.

Hatayama-san, you got this build bug report almost a month ago.  It
looks like it is going to need a fair bit of cleanup, so I fear this is
going to be dropped for v3.13.

	-hpa


  reply	other threads:[~2013-11-11 19:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  9:27 [PATCH 0/2] x86, apic: Disable BSP if boot cpu is AP HATAYAMA Daisuke
2013-08-29  9:27 ` [PATCH 1/2] x86, apic: Add boot_cpu_is_bsp() to check if boot cpu is BSP HATAYAMA Daisuke
2013-10-09 23:15   ` [tip:x86/bsp-hotplug] " tip-bot for HATAYAMA Daisuke
2013-08-29  9:28 ` [PATCH 2/2] x86, apic: Disable BSP if boot cpu is AP HATAYAMA Daisuke
2013-08-31  5:22   ` Borislav Petkov
2013-09-02  2:32     ` HATAYAMA Daisuke
2013-09-02  7:13       ` Borislav Petkov
2013-09-02  9:42         ` HATAYAMA Daisuke
2013-09-04  6:12           ` Borislav Petkov
2013-09-09  6:18             ` HATAYAMA Daisuke
2013-10-09 23:16   ` [tip:x86/bsp-hotplug] " tip-bot for HATAYAMA Daisuke
2013-10-12 17:31     ` H. Peter Anvin
2013-10-12 17:42       ` Ingo Molnar
2013-11-11 19:54         ` H. Peter Anvin [this message]
2013-11-12 10:20           ` HATAYAMA Daisuke
2013-11-12 15:35             ` H. Peter Anvin
2013-08-29 13:54 ` [PATCH 0/2] " H. Peter Anvin
2013-08-29 23:37   ` Eric W. Biederman
2013-08-30 12:48     ` Vivek Goyal
2013-08-29 23:51   ` HATAYAMA Daisuke
2013-08-30 15:43     ` H. Peter Anvin
2013-10-09 20:20       ` Vivek Goyal
2013-10-14  9:03         ` Petr Tesarik

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=528135D8.3040205@zytor.com \
    --to=hpa@zytor.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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