From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: fix wakeup_cpu with numaq/es7000 v2
Date: Wed, 19 Nov 2008 20:00:07 -0800 [thread overview]
Message-ID: <4924E0C7.8000003@ct.jp.nec.com> (raw)
In-Reply-To: <4921FC19.1080803@kernel.org>
Yinghai Lu wrote:
> Ingo Molnar wrote:
>> hm, one of my testboxes is rather unhappy about your patch:
>
>
> please check
>
> if you agree, will update update_genapic to autodetect other functions or etc.
>
> YH
>
> ---
>
> [PATCH] x86: fix wakeup_cpu with numaq/es7000 v2 - fix
>
> Impact: fix wakeup_secondary_cpu with hotplug
>
> We can not put that in x86_quirks, because that is __initdata.
> So try to move that to genapic, and add update_genapic in x86_quirks.
>
> later we even could use that stub to
> 1. autodetect CONFIG_ES7000_CLUSTERED_APIC
> 2. more correct inquire_remote_apic with apic_verbosity setting.
Hi,
I encountered boot failure on x86_32 box.
I think setting wakeup_cpu is missing.
--------
From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
Subject: [PATCH] x86: genapic: fix missing wakeup_cpu setup
Impact: fix boot failure
There is no way to setup wakeup_cpu when boot parameter apic= is not passed.
Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
---
arch/x86/mach-generic/probe.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/x86/mach-generic/probe.c b/arch/x86/mach-generic/probe.c
index 90b134f..bde6e36 100644
--- a/arch/x86/mach-generic/probe.c
+++ b/arch/x86/mach-generic/probe.c
@@ -98,6 +98,9 @@ void __init generic_apic_probe(void)
/* Not visible without early console */
if (!apic_probe[i])
panic("Didn't find an APIC driver");
+
+ if (x86_quirks->update_genapic)
+ x86_quirks->update_genapic();
}
printk(KERN_INFO "Using APIC driver %s\n", genapic->name);
}
--
1.5.6
next prev parent reply other threads:[~2008-11-20 4:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 8:47 [PATCH] x86: fix wakeup_cpu with numaq/es7000 Yinghai Lu
2008-11-16 11:12 ` [PATCH] x86: fix wakeup_cpu with numaq/es7000 v2 Yinghai Lu
2008-11-17 16:52 ` Ingo Molnar
2008-11-17 17:11 ` Cyrill Gorcunov
2008-11-17 17:35 ` Ingo Molnar
2008-11-17 17:52 ` Cyrill Gorcunov
2008-11-17 17:37 ` Ingo Molnar
2008-11-17 17:38 ` Ingo Molnar
2008-11-17 18:18 ` Yinghai Lu
2008-11-17 17:38 ` Ingo Molnar
2008-11-17 21:06 ` Yinghai Lu
2008-11-17 23:19 ` Yinghai Lu
2008-11-17 23:28 ` Ingo Molnar
2008-11-18 2:49 ` Yinghai Lu
2008-11-18 2:51 ` Yinghai Lu
2008-11-18 7:43 ` Ingo Molnar
2008-11-18 16:13 ` [PATCH] x86: fix wakeup_cpu with numaq/es7000 v2 - fix v2 Yinghai Lu
2008-11-18 16:14 ` [PATCH] x86: use update_genapic to get rid of ES7000_CLUSTERED_APIC v2 Yinghai Lu
2008-11-18 21:14 ` [PATCH] x86: fix wakeup_cpu with numaq/es7000 v2 - fix v2 Ingo Molnar
2008-11-20 4:50 ` Yinghai Lu
2008-11-20 4:00 ` Hiroshi Shimamoto [this message]
2008-11-20 9:46 ` [PATCH] x86: fix wakeup_cpu with numaq/es7000 v2 Ingo Molnar
2008-11-20 18:15 ` Hiroshi Shimamoto
2008-11-17 17:54 ` Yinghai Lu
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=4924E0C7.8000003@ct.jp.nec.com \
--to=h-shimamoto@ct.jp.nec.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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
Powered by JetHome