| United States-English |
|
|
|
![]() |
HP 9000 V-Class Server: Architecture > Chapter 2 Physical address spaceCSR access |
|
There are three packet routing methods used for accessing CSRs:
The 40-bit physical address determines which access method will be used. Processor-local accesses reference CSRs that reside in the processor issuing the request. These accesses are sent out and brought back into the requesting processor on its Runway bus. The EPAC, which is also connected to the Runway bus, ignores the request. The processor online bits of the processor agent are not checked for processor-local accesses. EPAC-local accesses are accesses to CSRs that reside in the EPAC physically connected to the processor that is issuing the request. These accesses are identified as EPAC-local and are not sent to the Hyperplane crossbar. Table 2-7 “Field specifications for system access” shows which fields must be specified for EPAC-local addressing. This method accesses processor-specific CSRs that reside in an EPAC. All processor-specific EPAC CSRs are identified as having bit 2 of the Chip field set. When the EPAC detects a processor-specific page, it forces bit three of the page field according to the processor issuing the request.
System accesses are used to access CSRs throughout the system. If the access is to an EMAC, the DXbr field routes the request to the proper EMAC. The EMAC Online field of the source EPAC System Configuration register is checked to ensure the destination EMAC is online. A high-priority machine check trap will result if the destination EMAC is not online. If the access is to an EPAC, EPIC, or processor, the request is first routed to the EMAC specified by the Intermediate EMAC field of the EPAC Configuration CSR. The EPAC Online field of the source EPAC System Configuration CSR is checked to ensure the destination EPAC is online. If the destination EMAC is not online, an HPMC results. Table 2-7 Field specifications for system access
It is possible to send a request to a CSR in a controller that is not online. Online bits are implemented for processors, EPACs, EMACs, and EPICs. Memory uses existence bits. Accesses to nonexistent CSRs terminate in one of the following ways:
The System Configuration register specifies system configuration parameters. The register is replicated on the EPAC and EMAC, but only fields used by each controller type are implemented for a particular controller. Therefore, not all fields exist on an EPAC or EMAC. Figure 2-12 “System Configuration register definition” shows the generic format of the register. All fields are written to by a write access and read from by a read access. All fields are unaffected by reset unless specified. The bits and fields of the System Configuration register are defined as follows:
Each EPAC has one Processor Agent Configuration register which specifies information about the EPAC. Each EPAC can be configured differently. Figure 2-13 “EPAC Configuration register definition” shows the format of the EPAC Configuration register. All fields of the register are read by a read access. The bits and fields in the EPAC Configuration register are defined as follows:
Each EPAC has a Processor Configuration register that contains specific information about the EPAC processor. Each processor attached to the EPAC can be configured differently. Figure 2-14 “EPAC Processor Configuration register definition” shows the format of the EPAC Processor Configuration register. All fields of the register are read by a read access. The bits and fields in the EPAC Processor Configuration register are defined as follows:
Each EPAC has a Memory Board Configuration register that specifies the memory block to memory board mapping. Figure 2-15 “EPAC Memory Board Configuration register definition” shows the format of the register. All fields are written by a write access and read by a read access. Reset has no effect. Writes to reserved bits are ignored and reads to reserved bits return the value zero. The three-bit memory block generated by the memory block interleave generation logic indexes into one of the eight memory board fields of the Memory Board Configuration register. The memory board fields specify the most significant two bits of the physical memory board. The least significant bit of the memory block index is the least significant bit of the physical memory board. This forces even memory blocks to be mapped to even memory boards and odd memory blocks to odd memory boards. Each EMAC has a Configuration register that contains specific information. Each EMAC can be configured differently. Figure 2-16 “EMAC Configuration register definition” shows the format of the register. All fields of the register are read by a read access. The bits and fields in the EMAC Configuration register are defined as follows:
Associated with each EMAC are four banks of memory, each bank having up to eight rows of SDRAMs. A table maps the row specified in the physical address to a physically installed row of SDRAMs. The four banks of memory controlled by an EMAC have the same memory row mapping. Each EMAC has a register that specifies the memory row mapping. The format of the register is shown in Figure 2-17 “Memory Row Configuration register definition”. All fields are written by a write access and read by a read access. Reset has no effect. Writes to reserved bits are ignored and reads to reserved bits return the value zero. The 3-bit row field of a physical address indexes one of the eight sets of row fields of a Memory Row configuration register. The bits and fields in the EMAC Memory Row Configuration Register are defined as follows:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||