linux-kernel - Re: [PATCH] fix boot breakage caused by x86: boot secondary cpus through initial

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] [day] [month] [year] [list]

Message-ID: <20081030212259.GB30303@elte.hu>
Date:	Thu, 30 Oct 2008 22:22:59 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Glauber Costa <gcosta@...hat.com>
Subject: Re: [PATCH] fix boot breakage caused by x86: boot secondary cpus
	through initial_code


* James Bottomley <James.Bottomley@...senPartnership.com> wrote:

> >From 01d1cd30acbcdab745ebc90c73d5fa4a27ce1d5c Mon Sep 17 00:00:00 2001
> From: James Bottomley <James.Bottomley@...senPartnership.com>
> Date: Wed, 29 Oct 2008 14:50:04 -0500
> Subject: [VOYAGER] make non boot CPUs work again
> 
> This commit:
> 
> commit 3e9704739daf46a8ba6593d749c67b5f7cd633d2
> Author: Glauber Costa <gcosta@...hat.com>
> Date:   Wed May 28 13:01:54 2008 -0300
> 
>     x86: boot secondary cpus through initial_code
> 
> removed the use of initialize_secondary.  However, it didn't update
> voyager, so the secondary cpus no longer boot.  Fix this by adding the
> initial_code switch to voyager as well.
> 
> Signed-off-by: James Bottomley <James.Bottomley@...senPartnership.com>
> ---
>  arch/x86/mach-voyager/voyager_smp.c |    5 ++++-
>  1 files changed, 4 insertions(+), 1 deletions(-)

applied to tip/x86/urgent, thanks James!

	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/