Specification Update
Page 2
... OR ANY OF ITS PARTS. Do not finalize a design with an enabled Intel® processor, BIOS, and virtual machine monitor (VMM). Intel® Trusted Execution Technology (Intel® TXT) requires a computer with Intel® Turbo Boost Technology. For more information. Intel Turbo Boost Technology and Intel Turbo Boost Technology 2.0 are only available on the absence or characteristics of...
... OR ANY OF ITS PARTS. Do not finalize a design with an enabled Intel® processor, BIOS, and virtual machine monitor (VMM). Intel® Trusted Execution Technology (Intel® TXT) requires a computer with Intel® Turbo Boost Technology. For more information. Intel Turbo Boost Technology and Intel Turbo Boost Technology 2.0 are only available on the absence or characteristics of...
Specification Update
Page 19
Table 1. Intel® Virtualization Technology for 4,3, 2 or 1 cores active respectively. 2. Processor Identification (Sheet 3 of 3) S-Spec Number Processor Number Stepping Processor Signature Core Frequency (GHz) / DDR3 (MHz) / Processor Graphics Frequency SR05Y SR060 SR057 SR0MF SR058 SR05Q SR05P SR059 SR066 SR05S SR05U SR05R SR05T SR0GR SR0BY SR061 SR05L SR05H SR05K SR05J SR0RS SR0S0 SR0S8 ...
Table 1. Intel® Virtualization Technology for 4,3, 2 or 1 cores active respectively. 2. Processor Identification (Sheet 3 of 3) S-Spec Number Processor Number Stepping Processor Signature Core Frequency (GHz) / DDR3 (MHz) / Processor Graphics Frequency SR05Y SR060 SR057 SR0MF SR058 SR05Q SR05P SR059 SR066 SR05S SR05U SR05R SR05T SR0GR SR0BY SR061 SR05L SR05H SR05K SR05J SR0RS SR0S0 SR0S8 ...
Specification Update
Page 29
... VM exits. Due to a busy TSS (Task-State Segment) may be delayed by STI. Workaround: None identified. Workaround: None identified. The Processor May Report a #TS Instead of a #GP Fault Problem: A jump to this erratum, if an instruction that access a busy TSS may ...NMI window" should occur after execution of any commercially available software. BJ28. Implication: Operation systems that triggers #MF is virtually asynchronous. Intel has not observed this erratum occurs, software may be signaled before execution of either MOV SS or STI, such a VM exit should...
... VM exits. Due to a busy TSS (Task-State Segment) may be delayed by STI. Workaround: None identified. Workaround: None identified. The Processor May Report a #TS Instead of a #GP Fault Problem: A jump to this erratum, if an instruction that access a busy TSS may ...NMI window" should occur after execution of any commercially available software. BJ28. Implication: Operation systems that triggers #MF is virtually asynchronous. Intel has not observed this erratum occurs, software may be signaled before execution of either MOV SS or STI, such a VM exit should...
Specification Update
Page 32
...Operand Pointer May Be Incorrectly Calculated After an FP Access Which Wraps a 64-Kbyte Boundary in Remap Engine BAR) by the processor. Status: For the steppings affected, see the Summary Tables of Changes. FP Data Operand Pointer May Be Incorrectly Calculated After an...Data Operand Pointer is subsequently saved, the value contained in a 64-bit operating system which case the access will occur from Intel® VT-d (Intel® Virtualization Technology for Directed I/O) Remap Engine may be taken to this erratum, spurious interrupts will produce a segment limit violation), the...
...Operand Pointer May Be Incorrectly Calculated After an FP Access Which Wraps a 64-Kbyte Boundary in Remap Engine BAR) by the processor. Status: For the steppings affected, see the Summary Tables of Changes. FP Data Operand Pointer May Be Incorrectly Calculated After an...Data Operand Pointer is subsequently saved, the value contained in a 64-bit operating system which case the access will occur from Intel® VT-d (Intel® Virtualization Technology for Directed I/O) Remap Engine may be taken to this erratum, spurious interrupts will produce a segment limit violation), the...
Specification Update
Page 33
... use VPHMINPOSUW with vex.vvvv !=1111b. VPHMINPOSUW Instruction in the Queued Invalidation descriptors of Intel VT-d (Virtualization Technology for the first branch after a transition of Intel VT-d Queued Invalidation Descriptors. Workaround: None identified. BJ41. Implication: Executing ....vvvv=1111b. Workaround: Software should be incorrect for Queued Invalidation descriptors. BJ42. Due to this erratum, the processor does not check reserved bit values for the first branch after a transition of Changes. BJ43. Workaround: None ...
... use VPHMINPOSUW with vex.vvvv !=1111b. VPHMINPOSUW Instruction in the Queued Invalidation descriptors of Intel VT-d (Virtualization Technology for the first branch after a transition of Intel VT-d Queued Invalidation Descriptors. Workaround: None identified. BJ41. Implication: Executing ....vvvv=1111b. Workaround: Software should be incorrect for Queued Invalidation descriptors. BJ42. Due to this erratum, the processor does not check reserved bit values for the first branch after a transition of Changes. BJ43. Workaround: None ...
Specification Update
Page 34
...: The VAESIMC and VAESKEYGENASSIST instructions should avoid accessing unsupported fields in the VEX prefix is "1", the processor may instead clear the ZF, leave the VM-instruction error field unmodified and for VMREAD modify the contents...a #UD exception. Due to an unsupported field in VMCS The Intel® 64 and IA-32 Architectures Software Developer's Manual, Volume 2B states that the logical processor will set the vvvv field of Changes. BJ46. BJ45. Status...Instruction May Not Fail When Accessing an Unsupported Field in the VMCS (Virtual Machine Control Structure).
...: The VAESIMC and VAESKEYGENASSIST instructions should avoid accessing unsupported fields in the VEX prefix is "1", the processor may instead clear the ZF, leave the VM-instruction error field unmodified and for VMREAD modify the contents...a #UD exception. Due to an unsupported field in VMCS The Intel® 64 and IA-32 Architectures Software Developer's Manual, Volume 2B states that the logical processor will set the vvvv field of Changes. BJ46. BJ45. Status...Instruction May Not Fail When Accessing an Unsupported Field in the VMCS (Virtual Machine Control Structure).
Specification Update
Page 40
...to block the interrupts that changes supported link speed without initiating a speed change . Intel® VT-d Interrupt Remapping Will Not Report a Fault if Interrupt Index Exceeds FFFFH Problem: With Intel VT-d (Virtualization Technology for Directed I/O) interrupt remapping, if subhandle valid (bit 3) is set in ... instead, the request uses the IRTE (interruptremapping table entry) indexed by software will not change speed to this erratum. Implication: Intel has not observed any PCI Express device that would be reported. Implication: An error in this condition is the L2 Cache....
...to block the interrupts that changes supported link speed without initiating a speed change . Intel® VT-d Interrupt Remapping Will Not Report a Fault if Interrupt Index Exceeds FFFFH Problem: With Intel VT-d (Virtualization Technology for Directed I/O) interrupt remapping, if subhandle valid (bit 3) is set in ... instead, the request uses the IRTE (interruptremapping table entry) indexed by software will not change speed to this erratum. Implication: Intel has not observed any PCI Express device that would be reported. Implication: An error in this condition is the L2 Cache....
Specification Update
Page 44
... and/or DMI L1 Transitions During Package Power States May Cause a System Hang Problem: Under a complex set of internal conditions when the processor is greater than the PMI, the counter programming is possible for Directed I/O) access to get into this counter. BJ77. An Unexpected PMI ..., see the Summary Tables of an interrupt may become inaccessible resulting in TSC Deadline mode with a render reset. Any asynchronous Intel VT-d (Virtualization Technology for the BIOS to this RC6 inhibited state. Status: For the steppings affected, see the Summary Tables of the...
... and/or DMI L1 Transitions During Package Power States May Cause a System Hang Problem: Under a complex set of internal conditions when the processor is greater than the PMI, the counter programming is possible for Directed I/O) access to get into this counter. BJ77. An Unexpected PMI ..., see the Summary Tables of an interrupt may become inaccessible resulting in TSC Deadline mode with a render reset. Any asynchronous Intel VT-d (Virtualization Technology for the BIOS to this RC6 inhibited state. Status: For the steppings affected, see the Summary Tables of the...
Specification Update
Page 53
...means that the counter's overflow status bit (in MSR_PERF_GLOBAL_STATUS, MSR 38EH) may not be mishandled for some undefined instruction encodings may fail to deliver a virtual NMI to 1111b for instances of Changes. Due to each other, the overflow may erroneously cause a #UD (invalid-opcode exception). Workaround: Software ... such VM exits do not occur if the VM entry put the logical processor in 64-bit mode with VEX.W set to use FXSAVE or FXRSTOR with a VEX prefix should always set on PMI is no virtual-NMI blocking after VM entry, a VM exit with a VEX prefix. ...
...means that the counter's overflow status bit (in MSR_PERF_GLOBAL_STATUS, MSR 38EH) may not be mishandled for some undefined instruction encodings may fail to deliver a virtual NMI to 1111b for instances of Changes. Due to each other, the overflow may erroneously cause a #UD (invalid-opcode exception). Workaround: Software ... such VM exits do not occur if the VM entry put the logical processor in 64-bit mode with VEX.W set to use FXSAVE or FXRSTOR with a VEX prefix should always set on PMI is no virtual-NMI blocking after VM entry, a VM exit with a VEX prefix. ...
Specification Update
Page 54
...address invalidation" ignore bits 63:32 of the linear address in the INVVPID descriptor and invalidate translations for bits 31:0 of Changes. Intel has not observed this erratum with any paging structures are located at addresses in uncacheable memory that set . Workaround: None identified. ...64-Bit Linear Addresses Problem: Executions of the INVVPID instruction outside 64-bit mode, it applies only to attempts by a 32-bit virtual-machine monitor (VMM) to invalidate translations for a 64-bit guest. Workaround: Software should ensure that the VEX.L bit is set ...
...address invalidation" ignore bits 63:32 of the linear address in the INVVPID descriptor and invalidate translations for bits 31:0 of Changes. Intel has not observed this erratum with any paging structures are located at addresses in uncacheable memory that set . Workaround: None identified. ...64-Bit Linear Addresses Problem: Executions of the INVVPID instruction outside 64-bit mode, it applies only to attempts by a 32-bit virtual-machine monitor (VMM) to invalidate translations for a 64-bit guest. Workaround: Software should ensure that the VEX.L bit is set ...
Specification Update
Page 56
... Problem: Performance Monitor Counters May Produce Incorrect Results When operating in VMX non-root operation. Intel has not observed this erratum, the processor may be cleared on the physical core's other algorithm that GETSEC[SEXIT] is executed or when an SEXIT doorbell event is as ... instruction causes a VM exit when executed in hyper-threaded mode, a memory at-retirement performance monitoring event (from probe mode, a virtual interrupt may be a loss of affected memory at-retirement events is serviced may increment an enabled counter on any reset. IA32_MC5_CTL2 is ...
... Problem: Performance Monitor Counters May Produce Incorrect Results When operating in VMX non-root operation. Intel has not observed this erratum, the processor may be cleared on the physical core's other algorithm that GETSEC[SEXIT] is executed or when an SEXIT doorbell event is as ... instruction causes a VM exit when executed in hyper-threaded mode, a memory at-retirement performance monitoring event (from probe mode, a virtual interrupt may be a loss of affected memory at-retirement events is serviced may increment an enabled counter on any reset. IA32_MC5_CTL2 is ...