Jesper Juhl <[email protected]> writes:
>
> 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?
In theory it could be an uninitialized phys_proc_id (0xff >> 1),
but it could be also the BIOS just setting the local APIC of CPU 1
to 0xff for some reason.
If you add a printk("PHYSCPU %d %x\n", smp_processor_id(), phys_proc_id[smp_processor_id()])
at the end of arch/x86_64/kernel/setup.c:early_identify_cpu() what does
dmesg | grep PHYSCPU output?
>
> Second thing I find slightly odd is the lack of "sse3" in the "flags" list.
> I was under the impression that all AMD Athlon 64 X2 CPU's featured SSE3?
> Is it a case of:
> a) Me being wrong, not all Athlon 64 X2's feature SSE3?
> b) The CPU actually featuring SSE3 but Linux not taking advantage of it?
> c) The CPU features SSE3 and it's being utilized, but /proc/cpuinfo
> doesn't show that fact?
> d) Something else?
It's called pni (prescott new instructions) for historical reasons. We added
the bit too early before Intel's marketing department could make up its
mind fully, so Linux is stuck with the old codename.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[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]
