All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: 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 - fix v2
Date: Tue, 18 Nov 2008 22:14:13 +0100	[thread overview]
Message-ID: <20081118211413.GE11490@elte.hu> (raw)
In-Reply-To: <4922E99B.8090604@kernel.org>


* Yinghai Lu <yinghai@kernel.org> wrote:

> 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.

thanks - this patch and the next one did the trick to stabilize the 
tip/x86/quirks topic tree - no more hotplug crashes and no more build 
failures either. The lineup is:

 b5fe363: x86: use update_genapic to get rid of ES7000_CLUSTERED_APIC v2
 f632ddc: x86: fix wakeup_cpu with numaq/es7000, v2, fix #2
 54ac14a: x86: fix wakeup_cpu with numaq/es7000, v2, fix
 569712b: x86: fix wakeup_cpu with numaq/es7000, v2

and i've merged them into tip/master as well.

	Ingo

  parent reply	other threads:[~2008-11-18 21:14 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               ` Ingo Molnar [this message]
2008-11-20  4:50                 ` [PATCH] x86: fix wakeup_cpu with numaq/es7000 v2 - fix v2 Yinghai Lu
2008-11-20  4:00         ` [PATCH] x86: fix wakeup_cpu with numaq/es7000 v2 Hiroshi Shimamoto
2008-11-20  9:46           ` 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=20081118211413.GE11490@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.