Re: [PATCH] x86: fix missing cpu_index initialisation

[Ingo Molnar]

* James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> wrote:

> >From f49bbb826d8ec87609a63fb014af6aacb16aac38 Mon Sep 17 00:00:00 2001
> From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
> Date: Wed, 29 Oct 2008 15:13:09 -0500
> Subject: [VOYAGER] x86: fix missing cpu_index initialisation
> 
> Ever since
> 
> commit 92cb7612aee39642d109b8d935ad265e602c0563
> Author: Mike Travis <travis@xxxxxxx>
> Date:   Fri Oct 19 20:35:04 2007 +0200
> 
>     x86: convert cpuinfo_x86 array to a per_cpu array
> 
> We've had an extra field in cpuinfo_x86 which is cpu_index.
> Unfortunately, voyager has never initialised this, although the only
> noticeable impact seems to be that /proc/cpuinfo shows all zeros for
> the processor ids.
> 
> Anyway, fix this by initialising the boot CPU properly and setting the
> index when the secondaries update.
> 
> Signed-off-by: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
> ---
> 
> Depends on [VOYAGER] x86: add ability to test for boot CPU

applied both to tip/x86/urgent:

 6b5496e: x86/voyager: fix missing cpu_index initialisation
 3b25aec: x86/voyager: fix compile breakage caused by dc1e35c6e95e8923cf1d35104

thanks James,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/