Re: [PATCH] Double x86 initialise fix.

From: Zwane Mwaikambo (zwane@linuxpower.ca)
Date: Mon Oct 28 2002 - 14:57:18 EST

Next message: Dipankar Sarma: "Re: [PATCH]updated ipc lock patch"
Previous message: chrisl@vmware.com: "Re: writepage return value check in vmscan.c"
In reply to: Alan Cox: "Re: [PATCH] Double x86 initialise fix."
Next in thread: Eric W. Biederman: "Re: [PATCH] Double x86 initialise fix."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 26 Oct 2002, Alan Cox wrote:

> > Eh? I don't understand this, and I think Dave is right for all the
> > IBM monsters I know of ;-) The *apicid* may not be 0 but the CPU
> > numbers are dynamically assigned as we boot, so the boot CPU will
> > always get 0, surely?
>
> Ok its a logical ID - so yes

<pedantic> kernel logical ID ;) </pedantic>

-- function.linuxpower.ca

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

Next message: Dipankar Sarma: "Re: [PATCH]updated ipc lock patch"
Previous message: chrisl@vmware.com: "Re: writepage return value check in vmscan.c"
In reply to: Alan Cox: "Re: [PATCH] Double x86 initialise fix."
Next in thread: Eric W. Biederman: "Re: [PATCH] Double x86 initialise fix."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Oct 31 2002 - 22:00:39 EST