Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Sohil Mehta <sohil.mehta@intel.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: <acme@kernel.org>, <adrian.hunter@intel.com>,
	<alexander.shishkin@linux.intel.com>, <bp@alien8.de>,
	<dave.hansen@linux.intel.com>, <fenghua.yu@intel.com>,
	<hpa@zytor.com>, <irogers@google.com>, <jdelvare@suse.com>,
	<jolsa@kernel.org>, <kan.liang@linux.intel.com>,
	<lenb@kernel.org>, <linux-acpi@vger.kernel.org>,
	<linux-hwmon@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-perf-users@vger.kernel.org>, <linux-pm@vger.kernel.org>,
	<linux@roeck-us.net>, <luto@kernel.org>, <mark.rutland@arm.com>,
	<mingo@redhat.com>, <namhyung@kernel.org>, <peterz@infradead.org>,
	<rafael@kernel.org>, <rui.zhang@intel.com>, <tglx@linutronix.de>,
	<tony.luck@intel.com>, <viresh.kumar@linaro.org>,
	<x86@kernel.org>
Subject: Re: [RFC PATCH 00/15] Prepare for new Intel family models
Date: Mon, 23 Dec 2024 11:43:44 -0800	[thread overview]
Message-ID: <e2d01538-f2b7-4f0d-8688-124531530c59@intel.com> (raw)
In-Reply-To: <f97c1228-7fca-4487-814c-6dd6ba581721@citrix.com>

On 12/20/2024 4:29 PM, Andrew Cooper wrote:
>>
>>   A dump of the microcode file 06-03-02 shows:
>>     001/001: sig 0x00001632, pf_mask 0x00, 1998-06-10, rev 0x0002, size 2048
>>   An archived CPUID dump [3] also says:
>>     CPUID 00000001: 00001632-00000000-00000000-0183FBFF
>>
>>   That would translate to a family number of 22 (0x16). This aberration is 
>>   not explicitly handled anywhere in the kernel so the platform might already 
>>   be broken. This series might make it worse for the platform if the latest 
>>   kernel works on it by chance.
> 
> Are you sure?  Bits 13:12 are the type field, and the 0x1 you've got is
> for an OverDrive processor.
> 

You are right. This is indeed the processor type field. I should have
spent more time reading the specification than Wikipedia :)


> x86_family() will consider this to be family 6 as far as I can see.
> 

On the bright side, we don't have to worry about breaking this CPU.

Sohil

      reply	other threads:[~2024-12-23 19:44 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 21:36 [RFC PATCH 00/15] Prepare for new Intel family models Sohil Mehta
2024-12-20 21:36 ` [RFC PATCH 01/15] x86/apic: Fix 32-bit APIC initialization for extended Intel families Sohil Mehta
2024-12-20 23:13   ` Dave Hansen
2024-12-23 20:40     ` Sohil Mehta
2024-12-20 21:36 ` [RFC PATCH 02/15] x86/apic: Fix smp init delay " Sohil Mehta
2024-12-20 23:20   ` Dave Hansen
2024-12-23 21:55     ` Sohil Mehta
2024-12-20 21:36 ` [RFC PATCH 03/15] x86/cpu/intel: Fix init_intel() checks for extended family numbers Sohil Mehta
2024-12-20 23:27   ` Dave Hansen
2024-12-23 23:41     ` Sohil Mehta
2024-12-20 21:36 ` [RFC PATCH 04/15] cpufreq: Fix the efficient idle check for Intel extended families Sohil Mehta
2024-12-20 21:37 ` [RFC PATCH 05/15] hwmon: Fix Intel family checks to include extended family numbers Sohil Mehta
2024-12-21 17:27   ` Guenter Roeck
2024-12-23 18:13     ` Sohil Mehta
2024-12-20 21:37 ` [RFC PATCH 06/15] x86/microcode: Update the Intel processor flag scan check Sohil Mehta
2024-12-21  9:11   ` Borislav Petkov
2024-12-23 19:52     ` Sohil Mehta
2024-12-21 15:46   ` Dave Hansen
2024-12-20 21:37 ` [RFC PATCH 07/15] x86/mtrr: Modify a x86_model check to an Intel VFM check Sohil Mehta
2024-12-20 21:37 ` [RFC PATCH 08/15] x86/cpu/intel: Replace early family 6 checks with VFM ones Sohil Mehta
2024-12-21 10:35   ` David Laight
2024-12-21 15:57     ` Dave Hansen
2024-12-21 16:48       ` David Laight
2024-12-21 18:30         ` Dave Hansen
2024-12-23 20:13       ` Sohil Mehta
2024-12-20 21:37 ` [RFC PATCH 09/15] x86/cpu/intel: Replace family 15 " Sohil Mehta
2024-12-20 21:37 ` [RFC PATCH 10/15] x86/cpu/intel: Replace family 5 model " Sohil Mehta
2024-12-20 21:37 ` [RFC PATCH 11/15] x86/pat: Replace Intel " Sohil Mehta
2024-12-20 21:37 ` [RFC PATCH 12/15] x86/acpi/cstate: Improve Intel family model checks Sohil Mehta
2024-12-20 21:37 ` [RFC PATCH 13/15] x86/cpu/intel: Bound the non-architectural constant_tsc " Sohil Mehta
2024-12-20 21:37 ` [RFC PATCH 14/15] perf/x86: Simplify p6_pmu_init() Sohil Mehta
2024-12-20 21:37 ` [RFC PATCH 15/15] perf/x86/p4: Replace Pentium 4 model checks with VFM ones Sohil Mehta
2024-12-21  0:29 ` [RFC PATCH 00/15] Prepare for new Intel family models Andrew Cooper
2024-12-23 19:43   ` Sohil Mehta [this message]

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=e2d01538-f2b7-4f0d-8688-124531530c59@intel.com \
    --to=sohil.mehta@intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=irogers@google.com \
    --cc=jdelvare@suse.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=luto@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=viresh.kumar@linaro.org \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox