![Intel ITANIUM ARCHITECTURE - SOFTWARE DEVELOPERS VOLUME 3 REV 2.3 Manual Download Page 518](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_2073404518.webp)
2:270
Volume 2, Part 1: Itanium
®
Architecture-based Operating System Interaction Model with IA-32 Applications
Operating System Warning
: Operating system code can not remap a given port to
another port address within the I/O port space, such that
port_physical_address{21:12} != port_physical_address{11:2}. Otherwise, based on
the processor model, I/O port data may be placed on the wrong bytes of the
processor’s bus and the port will not be correctly accessed.
I/O port space breakpoints can be configured by loading the address and mask fields
with the virtual address defined by the operating system to correspond to the I/O port
space.
The processor (as defined in the next section) ensures that load, store references will
not result in references to I/O devices for which permission was not granted.
All memory related faults defined in
can be generated by
IA-32 IN and OUT references to the I/O port space, including IA_32_Exception(Debug)
traps for data address breakpoints and IA_32_Exception(AlignmentCheck) for
unaligned references. (EFLAG.ac enabled unaligned port references are not detected by
the processor). Itanium Data Breakpoint registers (DBRs) can be configured to
generate debug traps for references into the I/O port space by either IA-32 IN/OUT
instructions or by IA-32 or Itanium load/store instructions.
10.7.2
Physical I/O Port Addressing
Some processors implementations will provide an M/IO pin or bus indication by
decoding physical addresses if references are within the 64MB physical I/O block. If so
the 64MB I/O port space is compressed back to 64KB. Subsequent processor
implementations may drop the M/IO pin (or bus indication) and rely on platform or
chip-set decoding of a range of the 64MB physical address space.
Through the PAL firmware interface, the 64MB physical I/O block can be programmed
to any arbitrary physical location. It is suggested that to be compatible with IA-32
based platforms, the platform physical location of the physical I/O block be
programmed above 4G-bytes and above all useful DRAM, ROM and existing memory
mapped I/O areas. See PAL_PLATFORM_ADDR on
for details.
Based on the platform design, some platforms can accept addresses for the expanded
64MB I/O block, while other platforms will require that the I/O port space be
compressed back to 64KB by the processor. If the I/O port space needs to be
compressed either the processor or platform (based on the implementation) will
perform the following operation for all memory references within the physical I/O block.
IO_address{1:0} = PA{1:0}
IO_address{15:2} = PA{25:12}// byte strobes are generated
// from the lower I/O_address bits
The processor ensures that the bus byte strobes and bus port address are derived from
PA{25:12,1:0}. Thus allowing an operating system to control security of each 4 ports
via TLB management of PA{25:12}.
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 ...