GXM Datasheet, PDF (223/244 Pages) National Semiconductor (TI) – Geode™ GXm Processor Integrated x86 Solution with MMX Support

Instruction Set (Continued)
Instruction Notes for Instruction Set Summary
Notes a through c apply to Real Address Mode only:
a. This is a Protected Mode instruction. Attempted execution in
Real Mode will result in exception 6 (invalid opcode).
b. Exception 13 fault (general protection) will occur in Real
Mode if an operand reference is made that partially or fully
extends beyond the maximum CS, DS, ES, FS, or GS seg-
ment limit (FFFFH). Exception 12 fault (stack segment limit vio-
lation or not present) will occur in Real Mode if an operand
reference is made that partially or fully extends beyond the
maximum SS limit.
c. This instruction may be executed in Real Mode. In Real
Mode, its purpose is primarily to initialize the CPU for Pro-
tected Mode.
d. -
Notes e through g apply to Real Address Mode and Protected
Virtual Address Mode:
e. An exception may occur, depending on the value of the oper-
and.
f. LOCK# is automatically asserted, regardless of the presence
or absence of the LOCK prefix.
g. LOCK# is asserted during descriptor table accesses.
Notes h through r apply to Protected Virtual Address Mode
only:
h. Exception 13 fault will occur 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.
i. 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, GS not present). If the SS register is
loaded and a stack segment not present is detected, an
exception 12 occurs.
j. All segment descriptor accesses in the GDT or LDT made by
this instruction will automatically assert LOCK# to maintain
descriptor integrity in multiprocessor systems.
k. JMP, CALL, INT, RET, and IRET instructions referring to
another code segment will cause an exception 13, if an appli-
cable privilege rule is violated.
l. An exception 13 fault occurs if CPL is greater than 0 (0 is the
most privileged level).
m. An exception 13 fault occurs if CPL is greater than IOPL.
n. The IF bit of the flag register is not updated if CPL is greater
than IOPL. The IOPL and VM fields of the flag register are
updated only if CPL = 0.
o. The PE bit of the MSW (CR0) cannot be reset by this instruc-
tion. Use MOV into CRO if desiring to reset the PE bit.
p. Any violation of privilege rules as apply to the selector oper-
and does not cause a Protection exception, rather, the zero
flag is cleared.
q. If the coprocessor’s memory operand violates a segment limit
or segment access rights, an exception 13 fault will occur
before the ESC instruction is executed. An exception 12 fault
will occur if the stack limit is violated by the operand’s starting
address.
r. 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
will occur.
Note s applies to National Semiconductor-specific SMM in-
structions:
s. All memory accesses to SMM space are non-cacheable. An
invalid opcode exception 6 occurs unless SMI is enabled and
SMAR size > 0, and CPL = 0 and [SMAC is set or if in an SMI
handler].
Note t applies to cache invalidation instruction with the
cache operating in write-back mode:
t. The total clock count is the clock count shown plus the num-
ber of clocks required to write all “modified” cache lines to
external memory.
Revision 3.1
223
www.national.com