Intel ITANIUM ARCHITECTURE - SOFTWARE DEVELOPERS MANUAL VOLUME 1 REV 2.3 Manual page 300

Hide thumbs Also See for ITANIUM ARCHITECTURE - SOFTWARE DEVELOPERS MANUAL VOLUME 1 REV 2.3:
Table of Contents

Advertisement

Note: Please refer to
Table 4-1.
it[cr].[id] overlaps [ID]TC
it[cr].[id] overlaps [DI]TC
it[cr].[id] overlaps [ID]TR
it[cr].[id] overlaps [DI]TR
ptc.l overlaps [ID]TC
ptc.l overlaps [ID]TR
ptc.g (local) overlaps [ID]TC
ptc.g (local) overlaps [ID]TR
ptc.g (remote) overlaps [ID]TC
ptc.g (remote) overlaps [ID]TR
ptc.e overlaps [ID]TC
ptc.e overlaps [ID]TR
ptr.[id] overlaps [ID]TC
ptr.[id] overlaps [DI]TC
ptr.[id] overlaps [ID]TR
ptr.[id] overlaps [DI]TR
a. Bracketed notation is intended to specify TC and TR overlaps in the same stream, e.g. itc.i and
ITC.
b. Must Insert: requires that the translation specified by the operation is inserted into a TC or TR as
appropriate. For itc and VHPT walker inserts, there is no guarantee to software that the entry will
exist in the future, with the exception of the relevant forward-progress requirements specified in
Section 4.1.1.2, "Translation Cache
c. Must Purge: requires that all partially or fully overlapped translations are removed prior to the insert or
purge operation.
d. Must not Machine Check: indicates that a processor does not cause a Machine Check abort as a
result of the operation.
e. Bracketed notation is intended to specify TC and TR overlaps in the opposite stream, e.g. itc.i and
DTC.
f. May Purge: indicates that a processor may remove partially or fully overlapped translations prior to
the insert or purge operation. However, software must not rely on the purge.
g. May Insert: indicates that the translation specified by the operation may be inserted into a TC.
However, software must not rely on the insert.
h. Must Machine Check: indicates that a processor will cause a Machine Check abort if an attempt is
made to insert or purge a partially or fully overlapped translation. The Machine Check abort may not
be delivered synchronously with the TLB insert or purge operation itself, but is guaranteed to be
delivered, at the latest, on a subsequent instruction serialization operation.
i. Must not Purge: the processor does not remove (or check for) partially or fully overlapped translations
prior to the insert or purge operation. Software can rely on this behavior.
j. ptc.g (and ptc.ga): two forms of global TLB purges are distinguished: local and remote. The local
form indicates that the ptc.g or ptc.ga was initiated on the local processor. The remote form
indicates that this is an incoming TLB shoot-down from a remote processor.
2:52
Table 4-1
for footnotes in
Purge Behavior of TLB Inserts and Purges
Case
Insert?
a
Must
e
Must
May
Must
j
N/A
(TC)".
Table
4-2.
Purge?
b
c
Must
f
May
g
May
i
Must not
Must
May
Must
May
Must
Must not
Must
Must not
Must
May
Must
Must not
Volume 2, Part 1: Addressing and Protection
Machine Check?
d
Must not
Must not
h
Must
Must not
Must not
Must
Must not
Must
Must not
Must not
Must not
Must not
Must not
Must not
Must not
Must not

Advertisement

Table of Contents
loading

This manual is also suitable for:

Itanium architecture 2.3

Table of Contents