Intel® Core™ i5-600, i3-500
Desktop Processor Series and
Intel® Pentium Desktop
Processor 6000 Series
Specification Update
January 2011
Reference Number: 322911-013
Legal Lines and Disclaimers
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY
ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PRO PERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN
INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEV ER, AND INTEL DISCLAIMS
ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES
RELATING T O FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER
INTELLECTUAL PROPERTY RIGHT. Intel products are not intended for use in medical, life saving, life sust aining, critical control or safety systems, or
in nuclear facility applications.
Intel may make changes to specifications and product descriptions at any time, without notice.
Designers must not rely on the absence or characteristics of any features or instructions marked “reserved” or “un defined.” Intel reserves these for
future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them.
The processor may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current
characterized errata are available on request. Contact your local I ntel sales office or your distributor to obtain the latest specifications and before
placing your product order.
Intel processor numbers are not a measure of performance. Processor numbers differentiat e features within each processor family, not across
different processor families. See http://www.intel.com/products/processor_number for details. Over time processor numbers will increment based on
changes in clock, speed, cache, or other features, an d increment s are not inte nded to r epresent pro portional or quantit ative increases in a ny particular
feature. Current roadmap processor number progression is not necessarily representative of future roadmaps. See www.intel.com/products/
processor_number for details.
®
Active Management Technology requires the computer system to have an Intel(R) AMT-enabled chipset, network hardware and software, as
Intel
well as connection with a power source and a corporate network connection . Setu p req uires configu rat ion b y the purchaser and may require scripting
with the management console or further integration into existing security frameworks to enable certain functionality . I t may also require modifications
of implementation of new business processes. With regard to notebooks, Intel AMT may not be available or certain capabilities may be limited over a
host OS-based VPN or when connecting wirelessly, on battery power, sleeping, hibernating or powered off. For more information, see www.intel.com/
technology/platform-technology/intel-amt/
®
Trusted Execution Technology (Intel® TXT) requires a computer system with Intel® Virtualization Technology (Intel® Virtualization Technology
Intel
®
VT-x) and Intel® Virtualization Technology for Directed I/O (Intel® VT-d)), a Intel TXT-enabled processor, chipset, BIOS, Authenticated Code
(Intel
Modules and an Intel TXT-compatible measured launched environment (MLE). The MLE could consist of a virtual machine monitor, an OS or an
application. In addition, Intel TXT requires the system to contain a TPM v1.2, as defined by the Trusted Computing Group and specific software for
some uses. For more information, see http://www.intel.com/technology/security
®
Intel
Virtualization Technology requires a computer system with an enabled Intel® processor, BIOS, virtual machine monitor (VMM) and, for some
uses, certain computer system software enabled for it. Functionality, performance or other benefits will vary depending on hardware and software
configurations and may require a BIOS update. Software applications may not be compatible with all operating systems. Please check with your
application vendor.
®
* Intel
Turbo Boost Technology requires a PC with a processor with Intel Turbo Boost Technology capability. Intel Turbo Boost Technology
performance varies depending on hardware, software and overall system configuration. Check with your PC manufacturer on whether your system
delivers Intel Turbo Boost Technology. For more information, see http://www.intel.com/technology/turboboost
®
Intel
Hyper-threading Technology requires a computer system with a processor supporting HT Technology and an HT Technology-enabled chipset,
BIOS, and operating system. Performance will vary depending on the specific hardware and software you use. For more information including details
on which processors support HT Technology, see http://www.intel.com/info/hyperthreading.
64-bit computing on Intel architecture requires a computer system with a processor, chipset, BIOS, operating system, device drivers and applications
enabled for Intel
®
64 architecture. Performance will vary depending on your hardware and software confi gurations. Consult with your system vendor
for more information.
Copies of documents which have an order number and are referenced in this document, or other Intel literatur e may be obt ained by cal ling 1-8 00-548-
4725 or by visiting Intel's website at http://www.intel.com.
Intel, Intel Core, Celeron, Pentium, Intel Xeon, Intel Atom, Intel SpeedStep, and the Intel logo are trademarks or registered trademarks of Intel
Added Errata AAU85-AAU87.
Corrected Extended Model and Model Number register values in Component Identification
table.
Added Errata AAU88-AAU91.
Added Documentation Changes AAU1-AAU3.
Updated Processor Identification table to include the SKU information for the Intel® Core™
i5-680 processor.
Added processor K-0 stepping information.
Updated Processor Identification table to include the SKU information for the Intel® Core™
i5-655K and i3-550 processor.
Erratum AAU32 added to this product Specification Update in error, all erratum details
removed from the specification update doc ument.
Updated Processor Identification table to include the SKU information for the Intel® Core™
i3-560 processor.
Added Errata AAU106 - AAU108
Updated problem statement for erratum AAU36
Changed document title to reflect introduction of G6960 processor
Added Errata AAU109-AAU110
Erratum AAU98 added to this specification Update in error; all erratum
details removed from the specification update document.
February 2010
March 2010
April 2010
June 2010
August 2010
August 2010
November 2010
January 2011
Specification Update
5
Preface
This document is an update to the specifications contained in the Affected Documents
table below. This document is a compilation of device and documentation errata,
specification clarifications and changes. It is intended for hardware system
manufacturers and software developers of applications, operating systems, or tools.
Information types defined in Nomenclature are consolidated into the specification
update and are no longer published in other documents.
This document may also contain information that was not previously published.
Affected Documents
®
Core™ i5-600, i3-500 Desktop Processor Series and Intel® Pentium® Desktop
Intel
Processor 6000 Series Datasheet, Volume 1
®
Core™ i5-600, i3-500 Desktop Processor Series and Intel® Pentium® Processor
Intel
G6950 Datasheet, Volume 2
Related Documents
AP-485, Intel® Processor Identification and the CPUID Instructionhttp://www.intel.com/
®
Intel
64 and IA-32 Architectures Software Developer’s Manual,
Volume 1: Basic Architecture
®
64 and IA-32 Architectures Software Developer’s Manual,
Intel
Volume 2A: Instruction Set Reference Manual A-M
®
64 and IA-32 Architectures Software Developer’s Manual,
Intel
Volume 2B: Instruction Se t Reference Manual N-Z
®
64 and IA-32 Architectures Software Developer’s Manual,
Intel
Volume 3A: System Programming Guide
®
64 and IA-32 Architectures Software Developer’s Manual,
Intel
Volume 3B: System Programming Guide
®
64 and IA-32 Intel Architecture Optimization Reference
Intel
Manual
®
Intel
64 and IA-32 Architectures Software Developer’s Manual
Errata are design defects or errors. These may cause the processor behavior to
deviate from published specifications. Hardware and software designed to be used with
any given stepping must assume that all errata documented for that stepping are
present on all devices.
S-Spec Number is a five-digit code used to identify products. Products are
differentiated by their unique characteristics such as, core speed, L2 cache size,
package type, etc. as described in the processor identification information table. Read
all notes associated with each S-Spec number.
Specification Changes are modifications to the current published specifications.
These changes will be incorporated in any new release of the specification.
Specification Clarifications describe a specification in greater detail or further
highlight a specification’s impact to a complex design situation. These clarifications will
be incorporated in any new release of the specification.
Documentation Changes include typos, errors, or omissions from the current
published specifications. These will be incorporated in any new release of the
specification.
Note:Errata remain in the specification update throughout the product’s lifecycle, or until a
particular stepping is no longer commercially available. Under these circumstances,
errata removed from the specification update are archived and available upon request.
Specification changes, specification clarifications and documentation changes are
removed from the specification update when the appropriate changes are made to the
appropriate product specification or user documentation (datasheets, manuals, etc.).
Specification Update
7
Summary Tables of Changes
The following tables indicate the errata, specification changes, specification
clarifications, or documentation changes which apply to the processor. Intel may fix
some of the errata in a future stepping of the component, and account for the other
outstanding issues through documentation or specification changes as noted. These
tables uses the following notations:
Codes Used in Summary Tables
Stepping
Page
Status
Row
X:Errata exists in the stepping indicated. Specification Change or
Clarification that applies to this stepping.
(No mark)
or (Blank box):This erratum is fixed in listed stepping or specification change
does not apply to listed stepping.
(Page):Page location of item in this document.
Doc:Document change or update will be implemented.
Plan Fix:This erratum may be fixed in a future stepping of the product.
Fixed:This erratum has been previously fixed.
No Fix:There are no plans to fix this erratum.
Change bar to left of a table row indicates this erratum is either new or modified from
the previous version of the document.
8
Specification Update
Errata (Sheet 1 of 5)
Number
AAU1
AAU2
AAU3
AAU4
AAU5
AAU6
AAU7
AAU8
AAU9
AAU10
AAU11
AAU12
AAU13
AAU14
AAU15
AAU16
AAU17
AAU18
AAU19
AAU20
AAU21
AAU22
AAU23
AAU24
AAU25
Steppings
C-2K-0
StatusERRATA
XXNo FixThe Processor May Report a #TS Instead of a #GP Fault
REP MOVS/STOS Executing with Fast Strings Enabled and Crossing Page
XXNo Fix
Boundaries with Inconsistent Memory Types may use an Incorrect Data Size or
Lead to Memory-Ordering Violations
XXNo Fix
Code Segment Limit/Canonical Faults on RSM May Be Serviced before Higher
Priority Interrupts/Exceptions and May Push the Wrong Address onto the Stack
XXNo FixPerformance Monitor SSE Retired Instructions May Return Incorrect Values
XXNo FixPremature Execution of a Load Operation Prior to Exception Handler Invocation
XXNo FixMOV To/From Debug Registers Causes Debug Exception
XXNo Fix
Incorrect Address Computed for Last Byte of FXSAVE/FXRSTOR Image Leads
to Partial Memory Update
XXNo FixValues for LBR/BTS/BTM Will Be Incorrect after an Exit from SMM
XXNo FixSingle Step Interrupts with Floating Point Exception Pending May Be Mishandled
XXNo FixFault on ENTER Instruction May Result in Unexpected Values on Stack Frame
XXNo Fix
XXNo Fix
XXNo Fix
XXNo Fix
XXNo Fix
XXNo Fix
IRET under Certain Conditions May Cause an Unexpected Alignment Check
Exception
General Protection Fault (#GP) for Instructions Greater than 15 Bytes May be
Preempted
General Protection (#GP) Fault May Not Be Signaled on Data Segment Limit
Violation above 4-G Limit
LBR, BTS, BTM May Report a Wrong Address when an Exception/Interrupt
Occurs in 64-bit Mode
MCi_Status Overflow Bit May Be Incorrectly Set on a Single Instance of a DTLB
Error
Debug Exception Flags DR6.B0-B3 Flags May be Incorrect for Disabled
Breakpoints
XXNo FixMONITOR or CLFLUSH on the Local XAPIC's Address Space Results in Hang
XXNo Fix
XXNo Fix
Corruption of CS Segment Register During RSM While Transitioning From Real
Mode to Protected Mode
Performance Monitoring Events for Read Miss to Level 3 Cache Fill Occupancy
Counter may be Incorrect
XXNo FixA VM Exit on MWAIT May Incorrectly Report the Monitoring Hardware as Armed
XXNo FixPerformance Monitor Event SEGMENT_REG_LOADS Counts Inaccurately
XXNo Fix
XXNo Fix
#GP on Segment Selector Descriptor that Straddles Canonical Boundary May
Not Provide Correct Exception Error Code
Improper Parity Error Signaled in the IQ Following Reset When a Code
Breakpoint is Set on a #GP Instruction
An Enabled Debug Breakpoint or Single Step Trap May Be Taken after MOV SS/
XXNo Fix
POP SS Instruction if it is Followed by an Instruction That Signals a Floating
Point Exception
XXNo FixIA32_MPERF Counter Stops Counting During On-Demand TM1
XXNo Fix
XXNo FixAPIC Error “Received Illegal Vector” May be Lost
XXNo Fix
XXNo Fix
XXNo FixIA32_PERF_GLOBAL_CTRL MSR May Be Incorrectly Initialized
XXNo Fix
XXNo Fix
XXNo FixFaulting Executions of FXRSTOR May Update State Inconsistently
XXNo Fix
XXNo FixMemory Aliasing of Code Pages May Cause Unpredictable System Behavior
XXNo FixPerformance Monitor Counters May Count Incorrectly
XXNo Fix
XXNo Fix
XXNo Fix
Synchronous Reset of IA32_APERF/IA32_MPERF Counters on Overflow Does
Not Work
Disabling Thermal Monitor While Processor is Hot, Then Re-enabling, May
Result in Stuck Core Operating Ratio
Writing the Local Vector Table (LVT) when an Interrupt is Pending May Cause an
Unexpected Interrupt
xAPIC Timer May Decrement Too Quickly Following an Automatic Reload While
in Periodic Mode
Reported Memory Type May Not Be Used to Access the VMCS and Referenced
Data Structures
Changing the Memory Type for an In-Use Page Translation May Lead to
Memory-Ordering Violations
Erratum AAU32 added to this specification Update in error; all erratum details
removed from the specification update document.
Delivery of Certain Events Immediately Following a VM Exit May Push a
Corrupted RIP onto the Stack
Infinite Stream of Interrupts May Occur if an ExtINT Delivery Mode Interrupt is
Received while All Cores in C6
EOI Transaction May Not be Sent if Software Enters Core C6 During an Interrupt
Service Routine
FREEZE_WHILE_SMM Does Not Prevent Event From Pending PEBS During
SMM
DR6 May Contain Incorrect Information When the First Instruction After a MOV
SS,r/m or POP SS is a Store
An Uncorrectable Error Logged in IA32_CR_MC2_STATUS May Also Result in a
System Hang
Performance Monitor Counter INST_RETIRED.STORES May Count Higher than
Expected
Sleeping Cores May Not be Woken Up on Logical Cluster Mode Broadcast IPI
Using Destination Field Instead of Shorthand
Performance Monitor Event EPT.EPDPE_MISS May be Counted While EPT is
Disable
Performance Monitor Event Offcore_response_0 (B7H) Does Not Count NT
Stores to Local DRAM Correctly
EFLAGS Discrepancy on Page Faults and on EPT-Induced VM Exits after a
Translation Change
Back to Back Uncorrected Machine Check Errors May Overwrite
IA32_MC3_STATUS.MSCOD
10
Specification Update
Errata (Sheet 3 of 5)
Number
AAU51
AAU52
AAU53
AAU54
AAU55
AAU56
AAU57
AAU58
AAU59
AAU60
AAU61
AAU62
AAU63
AAU64
AAU65
AAU66
AAU67
AAU68
AAU69
AAU70
AAU71
AAU72
AAU73
AAU74
AAU75
AAU76
Steppings
C-2K-0
XXNo Fix
XXNo Fix
StatusERRATA
Corrected Errors With a Yellow Error Indication May be Overwritten by Other
Corrected Errors
Performance Monitor Events DCACHE_CACHE_LD and DCACHE_CACHE_ST
May Overcount
XXNo FixRapid Core C3/C6 Transitions May Cause Unpredictable System Behavior
XXNo FixAPIC Timer CCR May Report 0 in Periodic Mode
XXNo Fix
XXNo Fix
XXNo Fix
Performance Monitor Events INSTR_RETIRED and MEM_INST_RETIRED May
Count Inaccurately
A Page Fault May Not be Generated When the PS bit is set to "1" in a PML4E or
PDPTE
BIST Results May be Additionally Reported After a GETSEC[WAKEUP] or INIT-
SIPI Sequence
XXNo FixPending x87 FPU Exceptions (#MF) May be Signaled Earlier Than Expected
XXNo FixVM Exits Due to "NMI-Window Exiting" May Be Delayed by One Instruction
XXNo Fix
XXNo Fix
XXNo Fix
The Memory Controller tTHROT_OPREF Timings May be Violated During Self
Refresh Entry
VM Exits Due to EPT Violations Do Not Record Information About Pre-IRET NMI
Blocking
Multiple Performance Monitor Interrupts are Possible on Overflow of
IA32_FIXED_CTR2
XXNo FixLBRs May Not be Initialized During Power-On Reset of the Processor
XXNo Fix
LBR, BTM or BTS Records May have Incorrect Branch From Information After an
EIST Transition, T-states, C1E, or Adaptive Thermal Throttling
XXNo FixVMX-Preemption Timer Does Not Count Down at the Rate Specified
XXNo Fix
Multiple Performance Monitor Interrupts are Possible on Overflow of Fixed
Counter 0
XXNo FixVM Exits Due to LIDT/LGDT/SIDT/SGDT Do Not Report Correct Operand Size
XXNo Fix
Performance Monitoring Events STORE_BLOCKS.NOT_STA and
STORE_BLOCKS.STA May Not Count Events Correctly
XXNo FixStorage of PEBS Record Delayed Following Execution of MOV SS or STI
XXNo Fix
XXNo Fix
XXNo Fix
XXNo Fix
XXNo Fix
Performance Monitoring Event FP_MMX_TRANS_TO_MMX May Not Count
Some Transitions
INVLPG Following INVEPT or INVVPID May Fail to Flush All Translations for a
Large Page
Logical Processor May Use Incorrect VPID after VM Entry That Returns From
SMM
The Memory Controller May Hang Due to Uncorrectable ECC Errors or Parity
Errors Occurring on Both Channels in Mirror Channel Mode
MSR_TURBO_RATIO_LIMIT MSR May Return Intel® Turbo Boost Technology
Core Ratio Multipliers for Non-Existent Core Configurations
XFixedInternal Parity Error May Be Incorrectly Signaled during C6 Exit
XXNo FixPMIs during Core C6 Transitions May Cause the System to Hang
Specification Update
11
Errata (Sheet 4 of 5)
Number
AAU77
AAU78
AAU79
AAU80
AAU82
AAU83
AAU84
AAU85
AAU86
AAU87
AAU88
AAU89
AAU90
AAU91
AAU92
AAU93
AAU94
AAU95
AAU96
AAU97
AAU98
AAU99
AAU100
AAU101
AAU102
AAU103
Steppings
C-2K-0
XXNo Fix
StatusERRATA
2MB Page Split Lock Accesses Combined With Complex Internal Events May
Cause Unpredictable System Behavior
If the APIC timer Divide Configuration Register (Offset 03E0H) is written at the
XXNo Fix
same time that the APIC timer Current Count Register (Offset 0390H) reads 1H,
it is possible that the APIC timer will deliver two interrupts.
XFixedTXT.PUBLIC.KEY is Not Reliable
XFixed
XXNo Fix
8259 Virtual Wire B Mode Interrupt May Be Dropped When it Collides With
Interrupt Acknowledge Cycle From the Preceding Interrupt
The APIC Timer Current Count Register May Prematurely Read 0x0 While the
Timer is Still Running
XXNo FixSecondary PCIe Port May Not Train After A Warm Reset
XXNo FixThe PECI Bus May Be Tri-stated after System Reset
XXNo Fix
The Combination of a Page-Split Lock Access And Data Accesses That Are Split
Across Cacheline Boundaries May Lead to Processor Livelock
XXNo FixProcessor Hangs on Package C6 State Exit
XXNo FixA Synchronous SMI May be Delayed
FP Data Operand Pointer May Be Incorrectly Calculated After an FP Access
XXNo Fix
Which Wraps a 4-Gbyte Boundary in Code That Uses 32-Bit Address Size in 64-
bit Mode
XXPlan Fix
PCI Express x16 Port Links May Fail to Dynamically Switch From 5.0GT/s to
2.5GT/s
XXNo FixPCI Express Cards May Not Train to x16 Link Width
XXNo Fix
Unexpected Graphics VID Transition During Warm Reset May Cause the System
to Hang
XXNo FixIO_SMI Indication in SMRAM State Save Area May Be Lost
XFixedVM Entry to 64-Bit Mode May Fail if Bits 48 And 47 of Guest RIP Are Different
XFixedVM Entry Loading an Unusable SS Might Not Set SS.B to 1
XFixed
XXNo Fix
FSW May Be Corrupted If an x87 Store Instruction Causes a Page Fault in VMX
Non-Root Operation
Under Certain Low Temperature Conditions, Some Uncore Performance
Monitoring Events May Report Incorrect Results
XXNo FixCKE May go Low Within tRFC(min) After a PD Exit
XXNo Fix
XXNo Fix
Erratum AAU98 added to this specification Update in error; all erratum details
removed from the specification update document.
Performance Monitor Events for Hardware Prefetches Which Miss The L1 Data
Cache May be Over-Counted
XXNo FixVM Exit May Incorrectly Clear IA32_PERF_GLOBAL_CTRL [34:32]
XFixed
XXNo Fix
XXNo Fix
Correctable and Uncorrectable Cache Errors May be Reported Until the First
Core C6 Transition
Accesses to a VMCS May Not Operate Correctly If CR0.CD is Set on Any Logical
Processor of a Core
PCIe Port’s LTSSM May Not Transition Properly in the Presence of TS1 or TS2
Ordered Sets That Have Unexpected Symbols Within those Sets
12
Specification Update
Errata (Sheet 5 of 5)
Number
AAU104
AAU105
Steppings
C-2K-0
StatusERRATA
XXNo FixNTB/RP Link Will Send Extra TS2 Ordered Set During Link Training
XXNo Fix
PCIe Ports May Not Enter Slave Loopback Mode From the Configuration LTSSM
State
USB Devices May Not Function Properly With Integrated Graphics While
AAU106
XXNo Fix
Running Targeted Stress Graphics Workloads With Non-Matching Memory
Configurations
AAU107
AAU108
AAU109
AAU110
XXNo Fix
XNo Fix
XFixedExecution of VMPTRLD May Corrupt Memory If Current-VMCS Pointer is Invalid
XXNo Fix
VM Entry May Omit Consistency Checks Related to Bit 14 (BS) of the Pending
Debug Exception Field in Guest-State Area of the VMCS
Intel Turbo Boost Technology Ratio Changes May Cause Unpredictable System
Behavior
PerfMon Overflow Status Can Not be Cleared After Certain Conditions Have
Occurred
Specification Changes
NumberSPECIFICATION CHANGES
None for this revision of this specification update.
Specification Clarifications
NumberSPECIFICATION CLARIFICATIONS
None for this revision of this specification update.
Documentation Changes
NumberDOCUMENTATION CHANGES
None for this revision of this specification update.
Specification Update
13
Identification Information
Component Identification using Programming Interface
The Intel® Core™ i5-600, i3-500 Desktop Processor Series and Intel® Pentium®
Desktop Processor 6000 Series stepping can be identified by the following register
contents:
1
Extended
2
Model
Reserved
Reserved
31:2827:2019:1615:1413:1211:87:43:0
Note:
1.The Extended Family , bits [27:20] are used in con junction with the F amily Code, specif ied in bits [11:8],
2.The Extended Model, bits [19:16] in conjunction with the Model Number, specified in bits [7:4], are
3.The Processor Type, specified in bits [13:12] indicates whether the processor is an original OEM
4.The Family Code corresponds to bits [11:8] of the EDX register after RESET, bits [11:8] of the EAX
5.The Model Number corresponds to bits [7:4] of the EDX register after RESET, bits [7:4] of the EAX
6.The Stepping ID in bits [3:0] indicates the revision number of that model. See Table 1 for the processor
Extended
Family
00000000b0010b00b01100101bxxxxb
to indicate whether the processor belongs to the Intel386, Intel486, Pentium, Pentium Pro, Pentium 4,
®
or Intel
used to identify the model of the processor within the processor’s family.
processor, an OverDrive processor, or a dual processor (capable of being used in a dual processor
system).
register after the CPUID instruction is executed with a 1 in the EAX register, and the generation field of
the Device ID register accessible through Boundary Scan.
register after the CPUID instruction is executed with a 1 in the EAX register, and the model field of the
Device ID register accessible through Boundary Scan.
stepping ID number in the CPUID information.
Core™ processor family.
Processor
Type
Family
3
Code
4
Model
Number
Stepping
5
ID
6
When EAX is initialized to a value of ‘1’, the CPUID instruction returns the Extended
Family, Extended Model, Processor Type, Family C ode, Mode l Number and Step ping ID
value in the EAX register. Note that the EDX processor signature value after reset is
equivalent to the processor signature output value in the EAX register.
Cache and TLB descriptor parameters are provided in the EAX, EBX, ECX and EDX
registers after the CPUID instruction is executed with a 2 in the EAX register.
14
The Intel® Core™ i5-600, i3-500 Desktop Processor Series and Intel® Pentium®
Desktop Processor 6000 Series can be identified by the following register contents:
SteppingVendor ID
C-28086h0040h12h
Notes:
1.The Vendor ID corresponds to bits 15:0 of the Vendor ID Register located at offset 00–01h in the PCI
2.The Device ID corresponds to bits 15:0 of the Device ID Register located at Device 0 offset 02–03h in
3.The Revision Number corresponds to bits 7:0 of the Revision ID Register located at offset 08h in the PCI
function 0 configuration space.
the PCI function 0 configuration space.
function 0 configuration space.