RE: 2.6.12-rc5 is broken in nvidia Ck804 Opteron MB/with dual cor e dual way

[YhLu <YhLu@tyan.com>]

So core1 is not the sibling of core0?

YH 

> -----Original Message-----
> From: Andi Kleen [mailto:ak@muc.de] 
> Sent: Thursday, June 02, 2005 11:52 AM
> To: YhLu
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: 2.6.12-rc5 is broken in nvidia Ck804 Opteron 
> MB/with dual cor e dual way
> 
> On Wed, Jun 01, 2005 at 08:26:00PM -0700, YhLu wrote:
> > Brought up 4 CPUs
> >     CPU 0, cpu_sibling_map[0]= 1 
> >     CPU 0, cpu_core_map[0]= 3 
> >     CPU 1, cpu_sibling_map[1]= 2 
> >     CPU 1, cpu_core_map[1]= 3 
> >     CPU 2, cpu_sibling_map[2]= 4 
> >     CPU 2, cpu_core_map[2]= c 
> >     CPU 3, cpu_sibling_map[3]= 8 
> >     CPU 3, cpu_core_map[3]= c
> > are the cpu_sibling_map[] right? 
> 
> Yes it is correct. A CPU is always a sibling of itself.
> 
> -Andi
> 
-
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/