On Tue, 20 Nov 2007, Mathieu Desnoyers wrote:
> > Convert one loop to NR_CPUS to use the cpu_possible map instead.
> >
>
> I'm just wondering how broken this is. Is there any assumption that
> there is no holes in the online cpu map in this code ?
Yeah, I saw only one loop in there and so I thi
On Tue, 20 Nov 2007, Andi Kleen wrote:
> I would suggest to separate that one and fast-track it, possibly even for
> 2.6.24
I already did. Andrew has the patch in his tree.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Mor
On Tuesday 20 November 2007 02:11:33 [EMAIL PROTECTED] wrote:
> ACPI uses NR_CPUS in various loops and in some it accesses per cpu
> data of processors that are not present(!) and that will never be present.
> The pointers to per cpu data are typically not initialized for processors
> that are not
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> ACPI uses NR_CPUS in various loops and in some it accesses per cpu
> data of processors that are not present(!) and that will never be present.
> The pointers to per cpu data are typically not initialized for processors
> that are not present. So we
ACPI uses NR_CPUS in various loops and in some it accesses per cpu
data of processors that are not present(!) and that will never be present.
The pointers to per cpu data are typically not initialized for processors
that are not present. So we seem to be reading something here from offset 0
in memo
ACPI uses NR_CPUS in various loops and in some it accesses per cpu
data of processors that are not present(!) and that will never be present.
The pointers to per cpu data are typically not initialized for processors
that are not present. So we seem to be reading something here from offset 0
in mem
6 matches
Mail list logo
