
Summary Tables of Changes
34 Specification Update
Performance Monitoring Event BR_INST_RETIRED May Count
CPUID Instructions as Branches
Performance Monitoring Event MISALIGN_MEM_REF May Over
Count
A REP STOS/MOVS to a MONITOR/MWAIT Address Range May
Prevent Triggering of the Monitoring Hardware
False Level One Data Cache Parity Machine-Check Exceptions May
be Signaled
A Memory Access May Get a Wrong Memory Type Following a #GP
due to WRMSR to an MTRR Mask
PMI While LBR Freeze Enabled May Result in Old/Out-of-date LBR
Information
Overlap of an Intel
®
VT APIC Access Page in a Guest with the DS
Save Area May Lead to Unpredictable Behavior
VTPR Write Access During Event Delivery May Cause an APIC-
Access VM Exit
Performance Monitoring Event FP_MMX_TRANS_TO_MMX May Not
Count Some Transitions
Instruction Fetch May Cause a Livelock during Snoops of the L1
Data Cache
Use of Memory Aliasing with Inconsistent Memory Type may Cause
a System Hang or a Machine Check Exception
A WB Store Following a REP STOS/MOVS or FXSAVE May Lead to
Memory-Ordering Violations
VM Exit with Exit Reason “TPR Below Threshold” Can Cause the
Blocking by MOV/POP SS and Blocking by STI Bits to Be Cleared in
the Guest Interruptibility-State Field
Using Memory Type Aliasing with Cacheable and WC Memory
Types May Lead to Memory Ordering Violations
RSM Instruction Execution under Certain Conditions May Cause
Processor Hang or Unexpected Instruction Execution Results
NMIs may not be blocked by a VM-Entry failure.
Benign Exception after a Double Fault May Not Cause a Triple Fault
Shutdown Problem
IA32_MC1_STATUS MSR Bit[60] Does Not Reflect Machine Check
Error Reporting Enable Correctly
Corruption of CS Segment Register During RSM While Transitioning
From Real Mode to Protected Mode
FP Data Operand Pointer May Be Incorrectly Calculated After an FP
Access Which Wraps a 4-Gbyte Boundary in Code That Uses 32-Bit
Address Size in 64-bit Mode
Komentarze do niniejszej Instrukcji