RE: x86-64 dual core mapping

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm using LinuxBIOS and there is no acpi in that. Also I have tried Normal
BIOS, it also produce that.

Did you check my patch? It fixed that.

regards

YH 

> -----Original Message-----
> From: Andi Kleen [mailto:[email protected]] 
> Sent: Monday, May 02, 2005 10:02 AM
> To: YhLu
> Cc: Andi Kleen; [email protected]
> Subject: Re: x86-64 dual core mapping
> 
> On Thu, Apr 21, 2005 at 07:38:07PM -0700, YhLu wrote:
> > Andi,
> > 
> > I tried 2.6.12-rc3 with dual way dual cpus.
> > 
> > It seems right mapping should be
> > CPU 0(2) -> Node 0 -> Core 0
> > CPU 1(2) -> Node 0 -> Core 1
> > CPU 2(2) -> Node 1 -> Core 0
> > CPU 3(2) -> Node 1 -> Core 1
> > 
> > instead of
> > 
> > CPU 0(2) -> Node 0 -> Core 0
> > CPU 1(2) -> Node 0 -> Core 0
> > CPU 2(2) -> Node 1 -> Core 1
> > CPU 3(2) -> Node 1 -> Core 1
> 
> Hmm, yes, something seems wrong. The last time I tested it 
> worked this way, but maybe the latest merge has broken it 
> again. I will check it later.
> 
> Are you sure you dont have a broken SRAT table? The SRAT 
> table will overwrite the mappings, so if it is wrong the one 
> Linux reports will be too.
> 
> -Andi
> > 
> > YH
> > 
> > 
> > 
> > 
> > CPU 0(2) -> Node 0 -> Core 0
> > Using local APIC NMI watchdog using perfctr0 enabled ExtINT 
> on CPU#0 
> > ENABLING IO-APIC IRQs Using IO-APIC 4 ...changing IO-APIC physical 
> > APIC ID to 4 ... ok.
> > Using IO-APIC 5
> > ...changing IO-APIC physical APIC ID to 5 ... ok.
> > Using IO-APIC 6
> > ...changing IO-APIC physical APIC ID to 6 ... ok.
> > Using IO-APIC 7
> > ...changing IO-APIC physical APIC ID to 7 ... ok.
> > Synchronizing Arb IDs.
> > ..TIMER: vector=0x31 pin1=0 pin2=2
> > testing the IO APIC.......................
> > 
> > 
> > 
> > 
> > .................................... done.
> > Using local APIC timer interrupts.
> > Detected 12.564 MHz APIC timer.
> > Booting processor 1/1 rip 6000 rsp ffff81007ff99f58 
> Initializing CPU#1 
> > masked ExtINT on CPU#1
> > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> > CPU: L2 Cache: 1024K (64 bytes/line)
> > CPU 1(2) -> Node 0 -> Core 0
> >  stepping 00
> > Synced TSC of CPU 1 difference 30064769976 Booting 
> processor 2/2 rip 
> > 6000 rsp ffff81013ffa3f58 Initializing CPU#2 masked ExtINT on CPU#2
> > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> > CPU: L2 Cache: 1024K (64 bytes/line)
> > CPU 2(2) -> Node 1 -> Core 1
> >  stepping 00
> > Synced TSC of CPU 2 difference 30064770021 Booting 
> processor 3/3 rip 
> > 6000 rsp ffff81007ff49f58 Initializing CPU#3 masked ExtINT on CPU#3
> > CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> > CPU: L2 Cache: 1024K (64 bytes/line)
> > CPU 3(2) -> Node 1 -> Core 1
> >  stepping 00
> > Synced TSC of CPU 3 difference 30064770021 Brought up 4 CPUs
> 

Attachment: amd_dual_core_id.diff
Description: Binary data


[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux