linux-kernel - Re: [PATCH] x86: fix wakeup_cpu with numaq/es7000 v2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081118211413.GE11490@elte.hu>
Date:	Tue, 18 Nov 2008 22:14:13 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: fix wakeup_cpu with numaq/es7000 v2 - fix v2


* Yinghai Lu <yinghai@...nel.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/