From: Dave Dillow <dave@thedillows.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: LKML List <linux-kernel@vger.kernel.org>
Subject: Re: Athlon 64 X2 cpuinfo oddities
Date: Mon, 09 Jan 2006 15:29:07 -0500 [thread overview]
Message-ID: <1136838548.6029.4.camel@dillow.idleaire.com> (raw)
In-Reply-To: <9a8748490601091218m1ff0607h79207cfafe630864@mail.gmail.com>
On Mon, 2006-01-09 at 21:18 +0100, Jesper Juhl wrote:
> 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?
Can't help you with the rest, but SSE3 is called "pni" in cpuinfo for
historical reasons, IIRC.
--
Dave Dillow <dave@thedillows.org>
next prev parent reply other threads:[~2006-01-09 20:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 20:18 Athlon 64 X2 cpuinfo oddities Jesper Juhl
2006-01-09 20:29 ` Dave Dillow [this message]
2006-01-09 22:49 ` Jesper Juhl
2006-01-09 21:10 ` Rafael J. Wysocki
2006-01-09 22:32 ` Edmondo Tommasina
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=1136838548.6029.4.camel@dillow.idleaire.com \
--to=dave@thedillows.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.