From: Dave Jones <davej@redhat.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: cpufreq@lists.linux.org.uk,
Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: new p4-clockmod capable CPUs
Date: Sat, 7 Oct 2006 14:44:49 -0400 [thread overview]
Message-ID: <20061007184449.GD3732@redhat.com> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A8454B2E6AC@scsmsx413.amr.corp.intel.com>
On Sat, Oct 07, 2006 at 06:46:12AM -0700, Pallipadi, Venkatesh wrote:
> >Ah. Thanks. Now only the new Celerons and Xeons confuse me -- they're
> >family 6, model 14, stepping 8. Is Ap B1 still valid, as they're called
> >Xeons (and Celerons)?
> >
> >I am confused by all these marketing names being re-used and
> >re-used and
> >re-used and re-used.... sorry ;)
> >
>
> Hmm... That above doc gives MSR details but doesn't seem to say how to
> identify a Core/Core 2 processor. I had to look for another ref here.
> http://download.intel.com/design/mobile/SPECUPDT/30922205.pdf
> Which says as long as family is 0xf and model 0xe, you can assume it to
> be Core microarch. And model 0xf will be core 2 in a similar way.
> Irrespective of final marketing name that they may acquire.
It's usually handy to look at the x86info source[1], as most of the
time, I've done the head-scratching to figure out stuff like this
already :)
Dave
[1] http://www.codemonkey.org.uk/projects/x86info/
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-10-07 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-07 13:46 new p4-clockmod capable CPUs Pallipadi, Venkatesh
2006-10-07 18:44 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-03 18:44 Pallipadi, Venkatesh
2006-10-07 0:27 ` Dominik Brodowski
2006-10-02 23:23 Pallipadi, Venkatesh
2006-10-03 1:28 ` Dominik Brodowski
2006-10-02 2:06 Dominik Brodowski
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=20061007184449.GD3732@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=linux@dominikbrodowski.net \
--cc=venkatesh.pallipadi@intel.com \
/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.