Skip to main content

1.7.2 Notes on Using the Direct I/O Function


1.7.2 Notes on Using the Direct I/O Function
  1. [SPARC M12-2/M12-2S/M10-4/M10-4S]
    Suppose that one of the following operations with the setpciboxdio command is performed with the condition that the SPARC M12-2/M12-2S is used, XCP 2044 or later is used on the SPARC M10-4, or XCP 2050 or later is used on the SPARC M10-4S. Then, the logical domain configuration of the physical partition will return to the factory-default state the next time the control domain starts. Also, the OpenBoot PROM environment variables of the control domain may be initialized.
    - Changing the enable/disable setting of the direct I/O function for the PCI expansion unit

    - Adding/Removing/Replacing a PCI expansion unit in a PCI slot of a SPARC M12/M10 system chassis where the direct I/O function for the PCI expansion unit is enabled

    You can execute the setpciboxdio command regardless of whether there is a PCI expansion unit. Before doing so, save the logical domain configuration information from Oracle Solaris to an XML file. Also, write down the setting information for the OpenBoot PROM environment variables of the control domain to reconfigure them at any time. 
  1. Table 1-4 indicates what information may need to be saved/restored when changing the enable/disable setting of the direct I/O function for the PCI expansion unit by executing the setpciboxdio command.
Table 1-4  Required Operations for Switching the Enable/Disable Setting of the Direct I/O Function
PCI Expansion Unit Configuration Current Domain Configuration Rebuilding Oracle VM Server for SPARC Configuration Reconfiguring OpenBoot PROM Environment Variables
No factory-default
(Control domain only)
Not required Not required
No With logical domains other than control domain Required (XML file) Required (*1)
Yes factory-default
(Control domain only)
Not required Not required
Yes With logical domains other than control domain Required (XML file) Required (*1)
*1 This is not required in XCP 2230 or later or the SPARC M12-2/M12-2S.
  1. Table 1-5 indicates what information may need to be saved/restored when adding/removing/replacing a PCI expansion unit in a PCI slot in the SPARC M12/M10 system chassis where the direct I/O function for the PCI expansion unit is enabled. Here, the setpciboxdio command has been executed to enable the function.
Note - In PCI expansion unit maintenance using the PCI hot plug (PHP) function, the direct I/O function is disabled, so the above information does not need to be saved/restored.
Table 1-5  Required Operations for the Addition/Removal/Replacement of a PCI Expansion Unit in a PCI Slot in the SPARC M12/M10 System Chassis Where the Direct I/O Function is Enabled
Maintenance Environment Current Domain Configuration Rebuilding Oracle VM Server for SPARC Configuration Reconfiguring OpenBoot PROM Environment Variables
Addition/Removal with PPAR stopped factory-default
(Control domain only)
Not required Not required
With logical domains other than control domain
Required (XML file) Required (*2)
Replacement of faulty PCI expansion unit (*1) with PPAR stopped factory-default
(Control domain only)
Not required Not required
With logical domains other than control domain
Required (XML file) Required (*2)
Replacement of normal PCI expansion unit (*1) with PPAR stopped factory-default
(Control domain only)
Not required Not required
With logical domains other than control domain
Not required Not required
*1 This includes even the replacement of a link card, link cable, management cable, and link board.
*2 This is not required in XCP 2230 or later or the SPARC M12-2/M12-2S.
Note - Execute the ldm list-constraints -x command to save to an XML file, and execute the ldm init-system -i command to restore from an XML file. To display the OpenBoot PROM environment variables, execute the printenv command from the ok prompt. For a detailed procedure, see "1.7.3  How to Save/Restore the Logical Domain Configuration Information and the OpenBoot PROM Environment Variable."