Placement of peripheral devices on PCI bus
Table of Contents
- 1 General Description
- 2 Available PCI slots per each HP Alpha model emulated by CHARON-AXP
- 2.1 AlphaServer 400 (3 PCI slots)
- 2.2 AlphaServer 800 (4 PCI slots)
- 2.3 AlphaServer 1000 (3 PCI slots)
- 2.4 AlphaServer 1000A (7 PCI slots)
- 2.5 AlphaServer 1200 (6 PCI slots)
- 2.6 AlphaServer 2000 (3 PCI slots)
- 2.7 AlphaServer 2100 (3 PCI slots)
- 2.8 AlphaServer 4000 (16 PCI slots)
- 2.9 AlphaServer 4100 (8 PCI slots)
- 2.10 AlphaServer DS10 (4 PCI slots)
- 2.11 AlphaServer DS10L (1 PCI slot)
- 2.12 AlphaServer DS15 (4 PCI slots)
- 2.13 AlphaServer DS20 (6 PCI slots)
- 2.14 AlphaServer DS25 (6 PCI slots)
- 2.15 AlphaServer ES40 (10 PCI slots)
- 2.16 AlphaServer ES45 (10 PCI slots)
- 2.17 AlphaServer GS80 (8 PCI busses)
- 2.18 AlphaServer GS160 (16 PCI busses)
- 2.19 AlphaServer GS320 (32 PCI busses)
General Description
Each peripheral device of CHARON Virtual Machine (VM) connects to CHARON-AXP emulated PCI bus with the following configuration parameters:
bus
Parameter | bus | ||||||||
|---|---|---|---|---|---|---|---|---|---|
Type | Text string | ||||||||
Value | Value formats:
When specified, the bus configuration parameter tells the CHARON-AXP software the virtual PCI bus to which virtual HP Alpha system shall connect a certain virtual PCI adapter. By default the bus configuration parameter is not specified. If the bus configuration parameter is not specified, CHARON VM software connects the virtual PCI adapter to the first available virtual PCI bus. Example (AlphaServer ES40):
Example (AlphaServer GS80):
|
device
Parameter | device | |
|---|---|---|
Type | Numeric | |
Value | When specified, the device configuration parameter specifies position of a virtual PCI adapter on virtual PCI bus. By default the device configuration parameter is not specified. If the device configuration parameter is not specified, the CHARON VM software connects the virtual PCI adapter at the first available position of the virtual PCI bus. Example:
|
function
Parameter | function | |
|---|---|---|
Type | Numeric | |
Value | When specified, the function configuration parameter specifies position of a virtual PCI adapter on virtual PCI bus. By default the function configuration parameter is not specified. If the function configuration parameter is not specified, the CHARON VM software connects the virtual PCI a dapter at the first available position of the virtual PCI bus. Example:
|
irq_bus
Parameter | irq_bus | |
|---|---|---|
Type | Text string | |
Value | When specified, the "irq_bus" configuration parameter specifies virtual bus routing interrupt requests from virtual PCI adapter to CHARON-AXP virtual Alpha CPUs. By default the "irq_bus" configuration parameter is not specified. The "irq_bus" configuration parameter must be set to “isa” for AlphaServer 400. For HP Alpha systems other than AlphaServer 400 the "irq_bus" configuration parameter must be left as is (i.e. not specified). Example:
|
irq
Parameter | irq | |
|---|---|---|
Type | Numeric | |
Value | When specified, the "irq" configuration parameter assigns interrupt request to the virtual PCI adapter in HP Alpha system. By default the irq configuration parameter is not specified. If the irq configuration parameter is not specified, the CHARON VM software uses the correct values depending on the selected PCI position of a virtual PCI adapter. Example:
|
Note that typically all or some of those parameters are specified on loading of some PCI controller in the following way:
|
Available PCI slots per each HP Alpha model emulated by CHARON-AXP
The tables below specifies a map of preloaded devices and available slots for each HP Alpha models emulated by CHARON-AXP.
AlphaServer 400 (3 PCI slots)
In addition to 3 PCI vacant slots there are 2 PCI positions occupied by on-board devices. All 5 PCI positions are listed in the following table in the order in which Alpha SRM console enumerates them.
Slot | pci_<N> | device | function | irq | Description | Preloaded |
|---|---|---|---|---|---|---|
PCI0 (bus=pci_0) | ||||||
- | 0 | 6 | 0 | 11 | NCR 53C810 PCI SCSI Adapter | PKA |
- | 0 | 7 | 0 | - | Intel i82378 PCI ISA Bridge (SATURN) |
|
0 | 0 | 11 | 0 | 10 | <option> |
|
1 | 0 | 12 | 0 | 15 | <option> |
|
2 | 0 | 13 | 0 | 9 | <option> |
|
The IRQ stands for ISA IRQ Number because all interrupts are routed through the Intel i82378 PCI ISA Bridge (SATURN) resident cascade of Intel i8259 interrupt controllers.
So far the CHARON-AXP VMs do not support virtual NCR 53C810 PCI SCSI adapter. Instead, virtual QLOGIC ISP1040B PCI SCSI adapter is used.
No support for Multi-Function PCI devices in AlphaServer 400.
Example: Loading DE435 into slot 0
|
The "irq_bus=isa" setting is specific to AlphaServer 400 only.
AlphaServer 800 (4 PCI slots)
In addition to 4 PCI vacant slots there are 3 PCI positions occupied by on-board devices. All 7 PCI positions are listed in the following table in the order in which Alpha SRM console enumerates them.
Slot | pci_<N> | device | function | irq | Description | Preloaded |
|---|---|---|---|---|---|---|
PCI0 (bus=pci_0) | ||||||
- | 0 | 5 | 0 | 0 | QLOGIC ISP1020 PCI SCSI Adapter | PKA |
- | 0 | 6 | 0 | 0 | S3 Trio32/64 Display Adapter |
|
- | 0 | 7 | 0 | - | Intel i82375 PCI EISA Bridge (MERCURY) |
|
0 | 0 | 11 | 0 | 1 | <option> |
|
| 1 | 2 | <option>, function 1 |
| ||
2 | 17 | <option>, function 2 |
| |||
3 | 18 | <option>, function 3 |
| |||
1 | 0 | 12 | 0 | 3 | <option> |
|
| 1 | 4 | <option>, function 1 |
| ||
2 | 19 | <option>, function 2 |
| |||
3 | 20 | <option>, function 3 |
| |||
2 | 0 | 13 | 0 | 5 | <option> |
|
| 1 | 6 | <option>, function 1 |
| ||
2 | 21 | <option>, function 2 |
| |||
3 | 22 | <option>, function 3 |
| |||
3 | 0 | 14 | 0 | 7 | <option> |
|
| 1 | 8 | <option>, function 1 |
| ||
2 | 23 | <option>, function 2 |
| |||
3 | 24 | <option>, function 3 |
| |||
The IRQ stands for input line of ASIC interrupt controllers. It has nothing to do with "EISA" style interrupts. So far, the CHARON-AXP VMs do not emulate S3 Trio32/64 Display Adapter. So position of the device 6, function 0 on the PCI 0 remains empty.
Example 1: Loading DE500BA into slot 0
|
Example 2: Loading multiple DE500BA’s into slot 3, populating all 4 functions (gives 4 Ethernet ports)
|
Example 3: Loading mixture of KZPBA and DE500BA into slot 1, populating 2 functions out of 4
|
In the above example device name is PKB as there is a built-in PK-like PCI SCSI Adapter located “closer” to CPU and therefore assigned name PKA.
AlphaServer 1000 (3 PCI slots)
In addition to 3 PCI vacant slots there are 2 PCI positions occupied by on-board devices. All 5 PCI positions are listed in the following table in the order in which Alpha SRM console enumerates them.
Slot | pci_<N> | device | function | irq | Description | Preloaded |
|---|---|---|---|---|---|---|
PCI0 (bus=pci_0) | ||||||
- | 0 | 6 | 0 | 12 | NCR 53C810 PCI SCSI Adapter | PKA |
- | 0 | 7 | 0 | - | Intel i82375 PCI EISA Bridge (MERCURY) |
|
0 | 0 | 11 | 0 | 0 | <option> |
|
| 1 | 1 | <option>, function 1 |
| ||
2 | 2 | <option>, function 2 |
| |||
3 | 3 | <option>, function 3 |
| |||
1 | 0 | 12 | 0 | 4 | <option> |
|
| 1 | 5 | <option>, function 1 |
| ||
2 | 6 | <option>, function 2 |
| |||
3 | 7 | <option>, function 3 |
| |||
2 | 0 | |||||
© Stromasys, 1999-2025 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.
Need fast, reliable migration? We have done it countless times. Talk to an expert