
Summary Tables of Changes
24 Specification Update
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
Cache Data Access Request from One Core Hitting a
Modified Line in the L1 Data Cache of the Other Core May
Cause Unpredictable System Behavior
PREFETCHh Instruction Execution under Some Conditions
May Lead to Processor Livelock
PREFETCHh Instructions May Not Be Executed when
Alignment Check (AC) Is Enabled
Upper 32 Bits of the FPU Data (Operand) Pointer in the
FXSAVE Memory Image May Be Unexpectedly All 1‟s after
FXSAVE
Concurrent Multi-processor Writes to Non-dirty Page May
Result in Unpredictable Behavior
Performance Monitor IDLE_DURING_DIV (18h) Count May
Not Be Accurate
Values for LBR/BTS/BTM Will Be Incorrect after an Exit
from SMM
Shutdown Condition May Disable Non-Bootstrap Processors
SYSCALL Immediately after Changing EFLAGS.TF May Not
Behave According to the New EFLAGS.TF
Code Segment Limit/Canonical Faults on RSM May be
Serviced before Higher Priority Interrupts/Exceptions and
May Push the Wrong Address Onto the Stack
VM Bit Is Cleared on Second Fault Handled by Task Switch
from Virtual-8086 (VM86)
IA32_FMASK Is Reset during an INIT
An Enabled Debug Breakpoint or Single Step Trap May Be
Taken after MOV SS/POP SS Instruction if it is Followed by
an Instruction That Signals a Floating Point Exception
Last Branch Records (LBR) Updates May Be Incorrect after
a Task Switch
IO_SMI Indication in SMRAM State Save Area May Be Set
Incorrectly
INIT Does Not Clear Global Entries in the TLB
Using Memory Type Aliasing with Memory Types WB/WT
May Lead to Unpredictable Behavior
Update of Read/Write (R/W) or User/Supervisor (U/S) or
Present (P) Bits without TLB Shootdown May Cause
Unexpected Processor Behavior
Komentáře k této Příručce