Re: [git-pull -tip] x86: Basic AMD Support for performance counters

From: Ingo Molnar
Date: Sun Mar 01 2009 - 03:36:50 EST



* Ingo Molnar <mingo@xxxxxxx> wrote:

> Seems to be working fine, here's the output from an Athlon 64
> 3200+ (Sempron) box:
>
> Performance counter stats for 'ls':
>
> 17.420811 task clock ticks (msecs)
>
> 0 CPU migrations (events)
> 12 context switches (events)
> 583 pagefaults (events)
> 29760299 CPU cycles (events)
> 29401642 instructions (events)
> 12698498 cache references (events)
> 66269 cache misses (events)
>
> Wall-clock time elapsed: 687.999988 msecs

The patches cause a crash on another system - an Opteron system
spontaneous reboots at this point during early bootup:

CPU 0/0x4 -> Node 0
tseg: 00cfe00000
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
using C1E aware idle routine
AMD Performance Monitoring support detected.
... num counters: 4
... value mask: 0000000000000000
... fixed counters: 0
... counter mask: 000000000000000f
ACPI: Core revision 20081204
ftrace: converting mcount calls to 0f 1f 44 00 00
ftrace: allocating 16365 entries in 129 pages
Setting APIC routing to physical flat
masked ExtINT on CPU#0
ENABLING IO
[reboot]

this is the CPU type:

processor : 15
vendor_id : AuthenticAMD
cpu family : 16
model : 2
model name : Quad-Core AMD Opteron(tm) Processor 8356
stepping : 3
cpu MHz : 2300.000
cache size : 512 KB
physical id : 4
siblings : 4
core id : 3
cpu cores : 4
fpu : yes
fpu_exception : yes
cpuid level : 5
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 pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc
rep_good pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs
bogomips : 4622.47
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

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