From: Edmondo Tommasina <edmondo@eriadon.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
LKML List <linux-kernel@vger.kernel.org>,
"Discuss x86-64" <discuss@x86-64.org>
Subject: Re: Athlon 64 X2 cpuinfo oddities
Date: Mon, 9 Jan 2006 23:32:32 +0100 [thread overview]
Message-ID: <200601092332.32681.edmondo@eriadon.com> (raw)
In-Reply-To: <200601092210.04186.rjw@sisk.pl>
On Monday 09-January-2006 22:10, Rafael J. Wysocki wrote:
> Hi,
>
> On Monday, 9 January 2006 21:18, Jesper Juhl wrote:
> > I recently bought a Dual Core AMD Athlon 64 X2 4400+ CPU and dropped a
> > 2.6.15 kernel on the box and it runs very nice, but /proc/cpuinfo
> > shows a few things that seem slightly odd to me (haven't tried earlier
> > kernels on this so I don't know if cpuinfo looked different
> > previously).
> > It may be that it's absolutely correct and not odd at all, but I
> > thought I'd just ask :)
> >
> > Here's what cat /proc/cpuinfo shows :
> >
> > juhl@dragon:~$ cat /proc/cpuinfo
> > processor : 0
> > vendor_id : AuthenticAMD
> > cpu family : 15
> > model : 35
> > model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
> > stepping : 2
> > cpu MHz : 2200.260
> > cache size : 1024 KB
> > physical id : 0
> > siblings : 1
> > core id : 0
> > cpu cores : 1
> > fdiv_bug : no
> > hlt_bug : no
> > f00f_bug : no
> > coma_bug : no
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 1
> > wp : yes
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
> > fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy
> > bogomips : 4403.36
> >
> > processor : 1
> > vendor_id : AuthenticAMD
> > cpu family : 15
> > model : 35
> > model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
> > stepping : 2
> > cpu MHz : 2200.260
> > cache size : 1024 KB
> > physical id : 127
> > siblings : 1
> > core id : 1
> > cpu cores : 1
> > fdiv_bug : no
> > hlt_bug : no
> > f00f_bug : no
> > coma_bug : no
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 1
> > wp : yes
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
> > fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy
> > bogomips : 4399.53
> >
> >
> > So, what's odd with that?
> >
> > Well, first of all you'll notice that the second core shows a
> > "physical id" of 127 while the first core shows an id of 0. Shouldn't
> > the second core be id 1, just like the "core id" fields are 0 & 1?
>
> FWIW, I'm running 2.6.15 on Athlon X2 4200 and the second core's
> physical id is 0 (ie. same as of the frist one), the number of siblings
> for each core is 2, and the "cpu cores" value is 2 as well (yours is 1,
> apparently ;-)).
Same here. cpu cores is 2.
Random try: Do you have CONFIG_NR_CPUS=2 in your config?
edmondo@balrog ~ $ uname -a
Linux balrog 2.6.15 #1 SMP Tue Jan 3 19:44:52 CET 2006 x86_64
AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ AuthenticAMD GNU/Linux
edmondo@balrog ~ $ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 35
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
stepping : 2
cpu MHz : 1005.170
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy
bogomips : 2012.38
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp
processor : 1
vendor_id : AuthenticAMD
cpu family : 15
model : 35
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
stepping : 2
cpu MHz : 1005.170
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy
bogomips : 2012.38
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp
ciao
edmondo
next prev parent reply other threads:[~2006-01-09 22:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 20:18 Jesper Juhl
2006-01-09 20:29 ` Dave Dillow
2006-01-09 22:49 ` Jesper Juhl
2006-01-09 21:10 ` Rafael J. Wysocki
2006-01-09 22:32 ` Edmondo Tommasina [this message]
2006-01-09 22:41 ` Jesper Juhl
2006-01-09 22:49 ` Edmondo Tommasina
2006-01-10 1:49 ` Andi Kleen
2006-01-10 2:12 ` Jesper Juhl
2006-01-10 2:36 ` Andi Kleen
2006-01-10 9:29 ` Jesper Juhl
2006-01-10 20:23 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: " Jeffrey Hundstad
2006-01-10 20:34 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfooddities David Lang
2006-01-10 20:50 ` Jeffrey Hundstad
2006-01-10 20:53 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2cpuinfooddities David Lang
2006-01-10 20:55 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfo oddities Andi Kleen
2006-01-11 0:15 ` Ken Moffat
2006-02-13 2:53 ` Brandon Low
2006-02-13 3:00 ` Alistair John Strachan
2006-02-13 9:20 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200601092332.32681.edmondo@eriadon.com \
--to=edmondo@eriadon.com \
--cc=discuss@x86-64.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome