![Intel ITANIUM ARCHITECTURE - SOFTWARE DEVELOPERS VOLUME 3 REV 2.3 Manual Download Page 814](http://html.mh-extra.com/html/intel/itanium-architecture-software-developers-volume-3-rev-2-3/itanium-architecture-software-developers-volume-3-rev-2-3_manual_2073404814.webp)
2:566
Volume 2, Part 2: Memory Management
The TCs are treated as a set associative cache and are not addressable by software.
The TC replacement policy is determined by software. All processor models implement
at least 8 instruction and 8 data TRs, and at least 1 instruction and 1 data TC entry.
Software inserts translations into the TLBs via insertion instructions. There are four
variants of insertion instructions.
itr.i
and
itr.d
insert a translation into the
specified instruction or data TR slot, respectively.
itc.i
and
itc.d
insert a translation
into a hardware-selected instruction or data TC entry, respectively.
Software TR purge instructions also distinguish between the instruction and data TRs
(
ptr.i
,
ptr.d
). TC purge instructions do not.
5.2.1
Translation Registers (TRs)
Once a translation is inserted by software into a TR, it remains in that TR until either
the translation is overwritten by software, or the translation is purged. TRs are used by
the OS to pin critical address translations; all memory references made to a TR
translation will always hit the TLB and will never cause the processor's hardware page
walker to walk the VHPT or raise a fault. Examples of memory areas that the OS might
cover with one or more TRs are the Interruption Vector Table, critical interruption
handlers not contained completely in the Interruption Vector Table, the root-level page
table entries, the long format VHPT, and any other non-pageable kernel memory areas.
Two address translations are said to overlap when one or more virtual addresses are
mapped by both translations. Software must ensure that translations in an instruction
TR never overlap other instruction TR or TC translations; likewise, software must
ensure that translations in a data TR never overlap other data TR or TC translations. If
an overlap is created, the processor will raise a Machine Check Abort.
The processor hardware will never overwrite or purge a valid TR. TRs that are currently
unused may be used by the processor hardware as extra TC entries, but if software
subsequently inserts a translation into an unused a TR, the TC translation will be
purged when the insertion is executed.
5.2.1.1
TR Insertion
To insert a translation into a TR, software performs the following steps:
1. If PSR.ic is 1, clear it and execute a
srlz.d
instruction to ensure the new value of
PSR.ic is observed.
2. Place the base virtual address of the translation into the IFA control register.
1
3. Place the page size of the translation into the ps field of the ITIR control register.
If protection key checking is enabled, also place the appropriate translation key
into the key field of the ITIR control register. See below for an explanation of
protection keys.
4. Place the slot number of the instruction or data TR into which the translation is be
inserted into a general register.
5. Place the base physical address of the translation into another general register.
1.
The upper 3 bits (VRN) of this address specify a region register whose contents are inserted along
with the rest of the translation. See
for details.
Summary of Contents for ITANIUM ARCHITECTURE - SOFTWARE DEVELOPERS VOLUME 3 REV 2.3
Page 1: ......
Page 11: ...x Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 13: ...1 2 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 33: ...1 22 Volume 1 Part 1 Introduction to the Intel Itanium Architecture ...
Page 57: ...1 46 Volume 1 Part 1 Execution Environment ...
Page 147: ...1 136 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 149: ...1 138 Volume 1 Part 2 About the Optimization Guide ...
Page 191: ...1 180 Volume 1 Part 2 Predication Control Flow and Instruction Stream ...
Page 230: ......
Page 248: ...236 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 250: ...2 2 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 264: ...2 16 Volume 2 Part 1 Intel Itanium System Environment ...
Page 380: ...2 132 Volume 2 Part 1 Interruptions ...
Page 398: ...2 150 Volume 2 Part 1 Register Stack Engine ...
Page 486: ...2 238 Volume 2 Part 1 IA 32 Interruption Vector Descriptions ...
Page 750: ...2 502 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 754: ...2 506 Volume 2 Part 2 About the System Programmer s Guide ...
Page 796: ...2 548 Volume 2 Part 2 Interruptions and Serialization ...
Page 808: ...2 560 Volume 2 Part 2 Context Management ...
Page 842: ...2 594 Volume 2 Part 2 Floating point System Software ...
Page 850: ...2 602 Volume 2 Part 2 IA 32 Application Support ...
Page 862: ...2 614 Volume 2 Part 2 External Interrupt Architecture ...
Page 870: ...2 622 Volume 2 Part 2 Performance Monitoring Support ...
Page 891: ......
Page 1099: ...3 200 Volume 3 Instruction Reference padd Interruptions Illegal Operation fault ...
Page 1295: ...3 396 Volume 3 Resource and Dependency Semantics ...
Page 1296: ......
Page 1302: ...402 Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 1494: ...4 192 Volume 4 Base IA 32 Instruction Reference FWAIT Wait See entry for WAIT ...
Page 1647: ...Volume 4 Base IA 32 Instruction Reference 4 345 ROL ROR Rotate See entry for RCL RCR ROL ROR ...
Page 1884: ...4 582 Volume 4 IA 32 SSE Instruction Reference ...
Page 1885: ...Index Intel Itanium Architecture Software Developer s Manual Rev 2 3 Index ...
Page 1886: ...Index Intel Itanium Architecture Software Developer s Manual Rev 2 3 ...
Page 1898: ...INDEX Index 12 Index for Volumes 1 2 3 and 4 ...