Notice: The Second Generation Intel® Xeon® Scalable Processors 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.
Reference Number: 338848-001US
Legal Lines and Disclaimers
Intel technologies’ features and benefits depend on system configuration and may require enabled hardware, software or service
activation. Learn more at Intel.com, or from the OEM or retailer.
No computer system can be absolutely secure. Intel does not assume any liability for lost or stolen data or systems or any
damages resulting from such losses.
You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel
products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted
which includes subject matter disclosed herein.
No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document.
The products described 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.
Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for
a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or
usage in trade.
Copies of documents which have an order number and are referenced in this document may be obtained by calling 1-800-5484725 or by visiting www.intel.com/design/literature.htm.
Intel, Intel Core, Intel
or other countries.
®
Core™ i7, Pentium®, Pentium® Pro, and the Intel logo are trademarks of Intel Corporation in the U.S. and/
*Other names and brands may be claimed as the property of others.
Second Generation Intel
Specification Update
April 2019
®
Xeon® Scalable Processors 3
Revision History
DateRevisionDescription
April 2019001Initial Release (Intel Public).
Revision History
®
4Second Generation Intel
April 2019
Xeon® Scalable Processors
Specification Update
Preface
Preface
This document is an update to the specifications contained in the next table: Affected
Documents. 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
Second Generation Intel
Electrical
Second Generation Intel
Registers
Related Documents
®
Intel
64 and IA-32 Architecture Software Developer Manual, Volume 1: Basic
Architecture
Volume 2A: Instruction Set Reference, A-M253666
Volume 2B: Instruction Set Reference, N-Z253667
756BVolume 3A: System Programming Guide, Part 1253668
Volume 3B: System Programming Guide, Part 2253669
ACPI Specificationswww.acpi.info
1. Document is available publicly at http://developer.intel.com.
2. Document available at www.acpi.info.
Document Title
®
Xeon® Scalable Processors Datasheet: Volume 1 -
®
Xeon® Scalable Processors Datasheet: Volume 2 -
Document Title
Document Number/
Location
338845
338846
Document Number/
Location
1
253665
1
1
1
1
2
Second Generation Intel® Xeon® Scalable Processors5
Specification Update
April 2019
Preface
Nomenclature
Errata are design defects or errors. These may cause the Product Name’s 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.
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.).
®
6Second Generation Intel
April 2019
Xeon® Scalable Processors
Specification Update
Summary Tables of Changes
Summary Tables of Changes
The following tables indicate the errata, specification changes, specification
clarifications, or documentation changes which apply to the Product Name product.
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 table row indicates this erratum is either
new or modified from the previous version of the document.
Second Generation Intel® Xeon® Scalable Processors7
Specification Update
April 2019
Errata
Summary Tables of Changes
Number
CLX1.xxx No Fix
CLX2.xxx No FixIntel
CLX3.xxx No FixIDI_MISC Performance Monitoring Events May be Inaccurate
CLX4.xxx No FixIntel
CLX5.xxx No FixIntel
CLX6.xxx No Fix
CLX7.xxx No Fix
CLX8.xxx No Fix
CLX9.xxx No FixIntel
CLX10.xxx No FixNon-Zero Values May Appear in ZMM Upper Bits After SSE Instructions
CLX11.xxx No FixZMM/YMM Registers May Contain Incorrect Values
CLX12.xxx No Fix
CLX13.xxx No Fix
CLX14.xxx No FixPerforming an XACQUIRE to an Intel
CLX15.xxx No FixUsing Intel
CLX16.xxx No Fix
CLX17.xxx No FixPerformance in an 8sg System May Be Lower Than Expected
Steppings
B-1L-1R-1
StatusErrata
Cache Allocation Technology (CAT)/CDP Might Not Restrict Cacheline
Allocation Under Certain Conditions (Intel
® PT PSB+ Packets May be Omitted on a C6 Transition
® PT CYC Packets Can be Dropped When Immediately Preceding PSB
® PT VM-entry Indication Depends on The Incorrect VMCS Control Field
Memory Bandwidth Allocation (MBA) Read After MSR Write May Return
Incorrect Value
In eMCA2 Mode, When The Retirement Watchdog Timeout Occurs
CATERR# May be Asserted
VCVTPS2PH To Memory May Update MXCSR in The Case of a Fault on The
Store
® PT May Drop All Packets After an Internal Buffer Overflow
When Virtualization Exceptions are Enabled, EPT Violations May Generate
Erroneous Virtualization Exceptions
® PT ToPA Tables Read From Non-Cacheable Memory During an Intel® Transactional
Intel
Synchronization Extensions (Intel® TSX) Transaction May Lead to Processor Hang
® PT ToPA Table May Lead to Processor Hang
® TSX Instructions May Lead to Unpredictable System Behavior
Reading Some C-state Residency MSRs May Result in Unpredictable
System Behavior
® Xeon® Processor Scalable Family)
Specification Changes
NumberSpecification Changes
1None for this revision of this specification update.
Specification Clarifications
No.Specification Clarifications
1None for this revision of this specification update.
Documentation Changes
No.Documentation Changes
1None for this revision of this specification update.
®
8Second Generation Intel
April 2019
Xeon® Scalable Processors
Specification Update
Identification Information
Identification Information
Component Identification via Programming Interface
The Second Generation Intel® Xeon® Scalable Processors stepping can be identified by
the following register contents:
Reserved
Extended
Family
1
Extended
2
Model
Reserved
31:2827:2019:1615:131211.87:43.0
00000000b0101b0b0110b0101b
1. The Extended Family, bits [27:20] are used in conjunction with the Family Code, specified in bits [11:8], to
indicate whether the processor belongs to the Intel386™, Intel486™, Pentium
®
Core™ processor family, or Intel® Core™ i7 family.
Intel
2. The Extended Model, bits [19:16] in conjunction with the Model Number, specified in bits [7:4], are used to
identify the model of the processor within the processor’s family.
3. The Processor Type, specified in bit [12] indicates whether the processor is an original OEM processor, an Over
Drive processor, or a dual processor (capable of being used in a dual processor system).
4. The Family Code corresponds to bits [11:8] of the EDX register after RESET, bits [11:8] of the EAX 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.
5. The Model Number corresponds to bits [7:4] of the EDX register after RESET, bits [7:4] of the EAX 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.
6. The Stepping ID in bits [3:0] indicates the revision number of that model. See Table 1, “Component
Identification via registers” on page 9 for the processor stepping ID number in the CPUID information.
When EAX is set to a value of one, the CPUID instruction returns the Extended Family,
Extended Model, Processor Type, Family Code, Model Number, and Stepping ID in the
EAX register. Note that after reset, the EDX processor signature value equals 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.
Table 1.Component Identification via registers
Processor
3
Type
Family
Code
4
Model
Number
Stepping ID
5
Varies per
®
, Pentium® Pro, Pentium® 4,
6
stepping
CAPID0 (Segment)
Physical
Chop
XCC
HCC
LCCR-1Server, 2S0x506571110100
Second Generation Intel® Xeon® Scalable Processors9
Specification Update
April 2019
• 8280, 8276, 8260 and 6240 have 2TB/socket and 4.5TB/socket memory capacity
versions (8280M, 8280L, 8276M, 8276L, 8260M, 8260L, 6240M and 6240L) with
identical frequencies.
• 8260, 6248 and 6230 have single socket versions (6212U, 6210U and 6209U) with
identical frequencies.
• The 8280, 8276, 8260 and 6240 have 2TB/socket and 4.5TB/socket memory
capacity versions (8280M, 8280L, 8276M, 8276L, 8260M, 8260L, 6240M and
6240L) with identical frequencies.
• The 8260, 6248 and 6230 have single socket versions (6212U, 6210U and 6209U)
with identical frequencies.
Second Generation Intel® Xeon® Scalable Processors17
Specification Update
April 2019
Errata
Errata
CLX1.Cache Allocation Technology (CAT)/CDP Might Not Restrict Cacheline
Allocation Under Certain Conditions (Intel
®
Xeon® Processor Scalable
Family)
Problem:Under certain microarchitectural conditions involving heavy memory traffic, cache lines
might fill outside the allocated L3 capacity bitmask (CBM) associated with the current
Class of Service (CLOS).
Implication:Cache Allocation Technology/Code and Data Prioritization (CAT/CDP) might see
Workaround: None identified.
Status:No Fix.
performance side effects and a reduction in the effectiveness of the CAT feature for
certain classes of applications, including cache-sensitive workloads than seen on
previous platforms.
CLX2.Intel® PT PSB+ Packets May be Omitted on a C6 Transition
Problem:An Intel® Processor Trace (Intel® PT) PSB+ (Packet Stream Boundary+) set of packets
Implication:After a logical processor enters C6, Intel® PT output may be missing PSB+ sets of
Workaround: None identified.
Status:No Fix.
may not be generated as expected when IA32_RTIT_STATUS.PacketByteCnt[48:32]
(MSR 0x571) reaches the PSB threshold and a logical processor C6 entry occurs within
the following one KByte of trace output.
packets.
CLX3.IDI_MISC Performance Monitoring Events May be Inaccurate
Problem:The IDI_MISC.WB_UPGRADE and IDI_MISC.WB_DOWNGRADE performance
monitoring events (Event FEH; UMask 02H and 04H) counts cache lines evicted from
the L2 cache. Due to this erratum, the per logical processor count may be incorrect
when both logical processors on the same physical core are active. The aggregate
count of both logical processors is not affected by this erratum.
Implication:IDI_MISC performance monitoring events may be inaccurate.
Workaround: None identified.
Status:No fix.
CLX4.Intel® PT CYC Packets Can be Dropped When Immediately Preceding
PSB
Problem:Due to a rare microarchitectural condition, generation of an Intel® PT (Intel Processor
Trace) PSB (Packet Stream Boundary) packet can cause a single CYC (Cycle Count)
packet, possibly along with an associated MTC (Mini Time Counter) packet, to be
dropped.
Implication:An Intel® PT decoder that is using CYCs to track time or frequency will get an improper
value due to the lost CYC packet.
Workaround: If an Intel
MTC following a PSB shows that an MTC was dropped, or the CYC value appears to be
4095 cycles short of what is expected, the CYC value associated with that MTC should
not be used. The decoder should wait for the next MTC before measuring frequency
again.
Status:No fix.
18Second Generation Intel
April 2019
®
PT decoder is using CYCs and MTCs to track frequency, and either the first
®
Xeon® Scalable Processors
Specification Update
Errata
CLX5.Intel® PT VM-entry Indication Depends on The Incorrect VMCS Control
Field
Problem:An Intel® Processor Trace PIP (Paging Information Packet), which includes indication of
entry into non-root operation, will be generated on VM-entry as long as the “Conceal
VMX in Intel® PT” field (bit 19) in Secondary Execution Control register
(IA32_VMX_PROCBASED_CTLS2, MSR 048BH) is clear. This diverges from expected
behavior, since this PIP should instead be generated only with a zero value of the
“Conceal VMX entries from Intel
®
PT” field (Bit 17) in the Entry Control register
(IA32_VMX_ENTRY_CTLS MSR 0484H).
®
Implication:An Intel
PT trace may incorrectly expose entry to non-root operation.
Workaround: A VMM (virtual machine monitor) should always set both the “Conceal VMX entries from
Intel® PT” field in the Entry Control register and the “Conceal VMX in Intel® PT” in the
Secondary Execution Control register to the same value.
Status:No fix.
CLX6.Memory Bandwidth Allocation (MBA) Read After MSR Write May
Return Incorrect Value
Problem:The Memory Bandwidth Allocation (MBA) feature defines a series of MSRs (0xD50-
Implication:The values written to the registers will be applied; however, software should be aware
Workaround: None identified.
Status:No fix.
0xD57) to specify MBA Delay Values per Class of Service (CLOS), in the
IA32_L2_QoS_Ext_BW_Thrtl_n MSR range. Certain values when written then read back
may return an incorrect value in the MSR. Specifically, values greater than or equal to
10 (decimal) and less than 39 (decimal) written to the MBA Delay Value (Bits [15:0])
may be read back as 10%.
that an incorrect value may be returned.
CLX7.In eMCA2 Mode, When The Retirement Watchdog Timeout Occurs
mode will cause the CATERR# pin to be pulsed in addition to an MSMI# pin assertion.
In addition, a Machine Check Abort (#MC) will be pended in the cores along with the
MSMI.
Implication:Due to this erratum, systems that expect to only see MSMI# will also see CATERR#
pulse when a Retirement Watchdog Timeout occurs. The CATERR# pulse can be safely
ignored.
Workaround: None identified.
Status:No fix.
CLX8.VCVTPS2PH To Memory May Update MXCSR in The Case of a Fault on
The Store
Problem:Execution of the VCVTPS2PH instruction with a memory destination may update the
Implication:Software may see exceptions flags set in MXCSR, although the instruction has not
Workaround: None identified.
Status:No fix.
MXCSR exceptions flags (bits [5:0]) if the store to memory causes a fault (e.g., #PF) or
VM exit. The value written to the MXCSR exceptions flags is what would have been
written if there were no fault.
successfully completed due to a fault on the memory operation. Intel has not observed
this erratum to affect any commercially available software.
Second Generation Intel® Xeon® Scalable Processors19
Specification Update
April 2019
Errata
CLX9.Intel® PT May Drop All Packets After an Internal Buffer Overflow
Problem:Due to a rare microarchitectural condition, an Intel® PT (Processor Trace) ToPA (Table
Implication:When this erratum occurs, all trace data will be lost until either PT is disabled and re-
Workaround: None identified.
Status:No fix.
of Physical Addresses) entry transition can cause an internal buffer overflow that may
result in all trace packets, including the OVF (Overflow) packet, being dropped.
enabled via IA32_RTIT_CTL.TraceEn [bit 0] (MSR 0570H) or the processor enters and
exits a C6 or deeper C state.
CLX10.Non-Zero Values May Appear in ZMM Upper Bits After SSE Instructions
Problem:Under complex microarchitectural conditions, a VGATHER instruction with ZMM16-31
Implication:Due to this erratum, an unexpected value may appear in a ZMM register aliased to an
Workaround: None identified.
Status:No fix.
destination register followed by an SSE instruction in the next 4 instructions, may
cause the ZMM register that is aliased to the SSE destination register to have non-zero
values in bits 256-511. This may happen only when ZMM0-15 bits 256-511 are all zero,
and there are no other instructions that write to ZMM0-15 in between the VGATHER
and the SSE instruction. Subsequent SSE instructions that write to the same register
will reset the affected upper ZMM bits and XSAVE will not expose these ZMM values as
long as no other AVX512 instruction writes to ZMM0-15. This erratum will not occur in
software that uses VZEROUPPER between AVX instructions and SSE instructions as
recommended in the SDM.
SSE destination. Software may observe this value only if the ZMM register aliased to
the SSE instruction destination is used and VZEROUPPER is not used between AVX and
SSE instructions. Intel has not observed this erratum with any commercially available
software.
CLX11.ZMM/YMM Registers May Contain Incorrect Values
Problem:Under complex microarchitectural conditions values stored in ZMM and YMM registers
may be incorrect.
Implication:Due to this erratum, YMM and ZMM registers may contain an incorrect value. Intel® has
not observed this erratum with any commercially available software.
Workaround: It is possible for BIOS to contain a workaround for this erratum.
Status:No fix.
CLX12.When Virtualization Exceptions are Enabled, EPT Violations May
Generate Erroneous Virtualization Exceptions
Problem:An access to a GPA (guest-physical address) may cause an EPT-violation VM exit. When
the “EPT-violation #VE” VM-execution control is 1, an EPT violation may cause a #VE
(virtualization exception) instead of a VM exit. Due to this erratum, an EPT violation
may erroneously cause a #VE when the “suppress #VE” bit is set in the EPT pagingstructure entry used to map the GPA being accessed. This erratum does not apply when
the “EPT-violation #VE” VM-execution control is 0 or when delivering an event through
the IDT. This erratum applies only when the GPA in CR3 is used to access the root of
the guest paging-structure hierarchy (or, with PAE paging, when the GPA in a PDPTE is
used to access a page directory).
Implication:When using PAE paging mode, an EPT violation that should cause an VMexit in the VMM
may instead cause a VE# in the guest. In other paging modes, in addition to delivery of
the erroneous #VE, the #VE may itself cause an EPT violation, but this EPT violation
will be correctly delivered to the VMM.
®
20Second Generation Intel
April 2019
Xeon® Scalable Processors
Specification Update
Errata
Workaround: A VMM may support an interface that guest software can invoke with the VMCALL
instruction when it detects an erroneous #VE.
Status:No fix.
CLX13.Intel® PT ToPA Tables Read From Non-Cacheable Memory During an
Intel® Transactional Synchronization Extensions (Intel® TSX)
Transaction May Lead to Processor Hang
Problem:If an Intel® PT (Intel Processor Trace) ToPA (Table of Physical Addresses) table is placed
Implication:Placing Intel
Workaround: None identified. Intel
Status:No fix.
in UC (Uncacheable) or USWC (Uncacheable Speculative Write Combining) memory,
and a ToPA output region is filled during an Intel® TSX (Intel Transaction
Synchronization) transaction, the resulting ToPA table read may cause a processor
hang.
®
PT ToPA tables in non-cacheable memory when Intel® TSX is in use may
lead to a processor hang.
®
PT ToPA tables should be located in WB memory if Intel® TSX is
in use.
CLX14.Performing an XACQUIRE to an Intel® PT ToPA Table May Lead to
Processor Hang
Problem:If an XACQUIRE lock is performed to the address of an Intel® PT (Intel Processor Trace)
ToPA (Table of Physical Addresses) table, and that table is later read by the CPU during
the HLE (Hardware Lock Elision) transaction, the processor may hang.
Implication:Accessing ToPA tables with XACQUIRE may result in a processor hang.
Workaround: None identified. Software should not access ToPA tables using XACQUIRE. An OS or
Status:No fix.
hypervisor may wish to ensure all application or guest writes to ToPA tables to take
page faults or EPT violations.
CLX15.Using Intel® TSX Instructions May Lead to Unpredictable System
Behavior
Problem:Under complex microarchitectural conditions, software using Intel® Transactional
Synchronization Extensions (Intel
Intel has only seen this under synthetic testing conditions. Intel is not aware of any
commercially available software exhibiting this behavior.
Implication:Due to this erratum, unpredictable system behavior may occur.
Workaround: It is possible for BIOS to contain a workaround for this erratum.
Status:No fix.
®
TSX) may result in unpredictable system behavior.
CLX16.Reading Some C-state Residency MSRs May Result in Unpredictable
System Behavior
Problem:Under complex microarchitectural conditions, an MSR read of
MSR_CORE_C3_RESIDENCY MSR (3FCh), MSR_CORE_C6_RESIDENCY MSR (3FDh), or
MSR_CORE_C7_RESIDENCY MSR (3FEh) may result in unpredictable system behavior.
Implication:Unexpected exceptions or other unpredictable system behavior may occur.
Workaround: It is possible for the BIOS to contain a workaround for this erratum.
Status:No Fix.
Second Generation Intel® Xeon® Scalable Processors21
Specification Update
April 2019
Errata
CLX17.Performance in an 8sg System May Be Lower Than Expected
Problem:In 8sg (8-socket glueless) systems, certain workloads may generate a significant
Implication:Due to this erratum, 8sg system performance may be lower than expected.
Workaround: A BIOS code change has been identified and may be implemented as a workaround for
Status:No fix.
stream of accesses to remote nodes, leading to unexpected congestion in the
processor's snoop responses.
this erratum
®
22Second Generation Intel
April 2019
Xeon® Scalable Processors
Specification Update
Specification Changes
Specification Changes
There are no Specification Changes in this Specification Update revision.
Second Generation Intel® Xeon® Scalable Processors23
Specification Update
April 2019
Specification Clarifications
There are no Specification Clarifications in this Specification Update revision.
Specification Clarifications
®
24Second Generation Intel
April 2019
Xeon® Scalable Processors
Specification Update
Documentation Changes
Documentation Changes
There are no Documentation Changes in this Specification Update revision.
§
Second Generation Intel® Xeon® Scalable Processors25
Specification Update
April 2019
Documentation Changes
®
26Second Generation Intel
April 2019
Xeon® Scalable Processors
Specification Update
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.