ALXD800EEXJ2VD AMD (ADVANCED MICRO DEVICES), ALXD800EEXJ2VD Datasheet - Page 639

• Manufacturer Part Number: ALXD800EEXJ2VD
• Manufacturer: AMD (ADVANCED MICRO DEVICES)

Specifications of ALXD800EEXJ2VD

• Operating Temperature (min): 0C
• Operating Temperature (max): 85C
• Operating Temperature Classification: Commercial
• Mounting: Surface Mount
• Lead Free Status / RoHS Status: Compliant

Instruction Set
Instruction Notes for Instruction Set Summary
Notes a through c apply to real address mode only:
a.
b.
c.
Notes e through g apply to real address mode and protected virtual address mode:
e.
f.
g.
Notes h through r apply to protected virtual address mode only:
h.
i.
j.
k.
l.
m. An exception 13 fault occurs if CPL is greater than IOPL.
n.
o.
p.
q.
r.
Issue s applies to AMD-specific SMM and DMM instructions:
s.
Issue t applies to the cache invalidation instruction with the cache operating in writeback mode:
t.
u.
AMD Geode™ LX Processors Data Book
This is a protected mode instruction. Attempted execution in real mode results in exception 6 (invalid opcode).
Exception 13 fault (general protection) occurs in real mode if an operand reference is made that partially or fully
extends beyond the maximum CS, DS, ES, FS, or GS segment limit. Exception 12 fault (stack segment limit violation or
not present) occurs in real mode if an operand reference is made that partially or fully extends beyond the maximum SS
limit.
This instruction may be executed in real mode. In real mode, its purpose is primarily to initialize the CPU for protected
mode.
An exception may occur, depending on the value of the operand.
LOCK# is automatically asserted, regardless of the presence or absence of the LOCK prefix.
LOCK# is asserted during descriptor table accesses.
Exception 13 fault occurs if the memory operand in CS, DS, ES, FS, or GS cannot be used due to either a segment
limit violation or an access rights violation. If a stack limit is violated, an exception 12 occurs.
For segment load operations, the CPL, RPL, and DPL must agree with the privilege rules to avoid an exception 13
fault. The segment’s descriptor must indicate “present” or exception 11 (CS, DS, ES, FS, or GS not present). If the SS
register is loaded, and a stack segment not present is detected, an exception 12 occurs.
All segment descriptor accesses in the GDT or LDT made by this instruction automatically assert LOCK# to maintain
descriptor integrity in multiprocessor systems.
JMP, CALL, INT, RET, and IRET instructions referring to another code segment cause an exception 13, if an applicable
privilege rule is violated.
An exception 13 fault occurs if CPL is greater than 0 (0 is the most privileged level).
The IF bit of the Flags register is not updated if CPL is greater than IOPL. The IOPL and VM fields of the Flags register
are updated only if CPL = 0.
The PE bit of the MSW (CR0) cannot be reset by this instruction. Use MOV into CR0 if you need to reset the PE bit.
Any violation of privilege rules as they apply to the selector operand do not cause a Protection exception; rather, the
zero flag is cleared.
If the processor’s memory operand violates a segment limit or segment access rights, an exception 13 fault occurs
before the ESC instruction is executed. An exception 12 fault occurs if the stack limit is violated by the operand’s
starting address.
The destination of a JMP, CALL, INT, RET, or IRET must be in the defined limit of a code segment or an exception 13
fault occurs.
An invalid opcode exception 6 occurs unless the current privilege level is zero (most privileged) and either the instruc-
tion is enabled in SMM_CTL, the instruction is enabled in DMM_CTL, the processor is in system management mode,
or the processor is in debug management mode.
The total clock count is the clock count shown plus the number of clocks required to write all “modified” cache lines to
external memory.
Non-standard processor core instructions. See Section 8.3.4 "Non-Standard Processor Core Instructions" on page 640
for details.
33234C
639