
Summary Tables of Changes
30 Specification Update
Code Segment Limit Violation May Occur On 4 Gigabyte Limit
Check
FP Inexact-Result Exception Flag May Not Be Set
Global Pages in the Data Translation Look-Aside Buffer (DTLB) May
Not Be Flushed by RSM instruction before Restoring the
Architectural State from SMRAM
Sequential Code Fetch to Non-canonical Address May have
Nondeterministic Results
VMCALL to Activate Dual-monitor Treatment of SMIs and SMM
Ignores Reserved Bit settings in VM-exit Control Field
REP MOVS/STOS Executing with Fast Strings Enabled and Crossing
Page Boundaries with Inconsistent Memory Types May Use an
Incorrect Data Size or Lead to Memory-Ordering Violations.
Some Bus Performance Monitoring Events May Not Count Local
Events under Certain Conditions
Premature Execution of a Load Operation Prior to Exception
Handler Invocation
General Protection (#GP) Fault May Not Be Signaled on Data
Segment Limit Violation above 4-G Limit
EIP May Be Incorrect after Shutdown in IA-32e Mode
#GP Fault is Not Generated on Writing IA32_MISC_ENABLE [34]
When Execute Disable is Not supported
Performance Monitoring Events for Retired Loads (CBH) and
Instructions Retired (C0H) May Not Be Accurate
Upper 32 bits of „From‟ Address Reported through BTMs or BTSs
May Be Incorrect
Unsynchronized Cross-Modifying Code Operations Can Cause
unexpected Instruction Execution Results
MSRs Actual Frequency Clock Count (IA32_APERF) or Maximum
Frequency Clock Count (IA32_MPERF) May Contain Incorrect Data
after a Machine Check Exception (MCE)
Incorrect Address Computed for Last Byte of FXSAVE/FXRSTOR
Image Leads to Partial Memory Update
Split Locked Stores May Not Trigger the Monitoring Hardware
REP CMPS/SCAS Operations May Terminate Early in 64-bit Mode
When RCX >= 0X100000000
FXSAVE/FXRSTOR Instructions which Store to the End of the
Segment and Cause a Wrap to a Misaligned Base Address
(Alignment <= 0x10h) May Cause FPU Instruction or Operand
Pointer Corruption
Komentarze do niniejszej Instrukcji