systemsoftware
/
Linux-Architecture-Reference
35
1
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Draft update

Browse Source 
- Complete Platform document cleanup
- Ensure build of all docs in POM
- General cross-doc cleanup

Signed-off-by: Jeff Scheel <scheel@us.ibm.com>
pull/2/head
Jeff Scheel 7 years ago
parent 877f675ef9
commit ea32391eb3
19 changed files with 10646 additions and 2917 deletions
Show Stats Download Patch File Download Diff File

101
DeviceTree/bk_main.xml
Unescape Escape View File

@ -42,7 +42,7 @@
<holder>OpenPOWER Foundation</holder>
</copyright>
<!-- TODO: Set the correct document releaseinfo -->
<releaseinfo>Revision 2.0_pre1</releaseinfo>
<releaseinfo>Revision 2.0_pre2</releaseinfo>
<productname>OpenPOWER</productname>
<pubdate/>

@ -71,6 +71,105 @@

<revhistory>
<!-- TODO: Update as new revisions created -->
<revision>
<date>2017-10-11</date>
<revdescription>
<itemizedlist spacing="compact">
<listitem>
<para>Revision 2.0_pre2 - Updates to include latest PAPR ACRs (2.8) as follows:</para>
<itemizedlist spacing="compact">
<listitem>
<para>ISA 2.07 privileged doorbell extensions (9/16/2012)</para>
</listitem>
<listitem>
<para>POWER ISA Name Change Category Vector.XOR to Vector.CRYPTO (11/4/2012)</para>
</listitem>
<listitem>
<para>Enable Multiple Redirected RDMA mappings per page (3/5/2013)</para>
</listitem>
<listitem>
<para>Add Block Invalidate Option (3/5/2013)</para>
</listitem>
<listitem>
<para>Implementation Dependent Optimizations (3/13/2013)</para>
</listitem>
<listitem>
<para>System Firmware Service Entitlement Date (Warranty Date) Check (4/3/2013)</para>
</listitem>
<listitem>
<para>New Function for ibm,change-msi to specify 32 bit MSI (5/14/2013)</para>
</listitem>
<listitem>
<para>Remove Client-Architecture-Support bit for UUID option (4/16/2013)</para>
</listitem>
<listitem>
<para>AddClient Architecture Support bit for RTAS ibm,change-msi (5/28/2013)</para>
</listitem>
<listitem>
<para>Add VNIC Server (5/24/2014)</para>
</listitem>
<listitem>
<para>VPA changes for P8 (EBB) (5/24/2013)</para>
</listitem>
<listitem>
<para>Add an hcall to clean up the entire MMU hashtable (11/20/2013)</para>
</listitem>
<listitem>
<para>Add LPCR[ILE] support to H_SET_MODE (5/31/2013)</para>
</listitem>
<listitem>
<para>New Root Node Properties (1/12/2016)</para>
</listitem>
<listitem>
<para>Extended Firmware Assisted Dump for P8 Registers (1/24/2014)</para>
</listitem>
<listitem>
<para>Sufficient H_COP_OP output buffer (6/21/2014)</para>
</listitem>
<listitem>
<para>Extend H_SEND_LOGICAL_LAN for large send packets (6/29/2014)</para>
</listitem>
<listitem>
<para>Extend H_GET_MPP_X reporting coalesced pages (8/24/2014)</para>
</listitem>
<listitem>
<para>Update ibm,pcie-link-speed-stats property to support PCIe 3.0 link speeds (6/12/2015)</para>
</listitem>
<listitem>
<para>Extend ibm,get-system-parameters RTAS to report Energy Management Tuning Parameters (3/18/2015)</para>
</listitem>
<listitem>
<para>Additional System Parameters related to mgmt of FW Service Entitlement Warranty period (6/22/2015)</para>
</listitem>
<listitem>
<para>Additional System Parameter to read LPAR Name string (10/7/2015)</para>
</listitem>
<listitem>
<para>Redesign of properties for DRC information and dynamic memory (7/23/2015)</para>
</listitem>
<listitem>
<para>Add additional logical loction code sections (3/4/2016)</para>
</listitem>
<listitem>
<para>Add ibm,vnic-client-mac to support vNIC failover (2/29/2016)</para>
</listitem>
<listitem>
<para>hcall for registering the process table (3/21/2016)</para>
</listitem>
<listitem>
<para>New device tree property for UUID (3/21/2016)</para>
</listitem>
<listitem>
<para>Changes for Hotplug RTAS Events (10/24/2016)</para>
</listitem>
<listitem>
<para>Support 64-bit PE TCEs in ibm,query-pe-dma-window (7/14/2016)</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</revdescription>
</revision>
<revision>
<date>2016-05-04</date>
<revdescription>

33
DeviceTree/ch_devtree_pa.xml
Unescape Escape View File

@ -683,7 +683,7 @@
<listitem>
<para>Standard <emphasis>property name</emphasis>. The value of this
property for CPU nodes shall be
<emphasis role="bold"><literal>&#8220;cpu&#8221;</literal></emphasis>.</para>
<literal>&#8220;cpu&#8221;</literal>.</para>
</listitem>
</varlistentry>
@ -710,23 +710,21 @@
<itemizedlist>
<listitem>
<para><emphasis role="bold"><literal>&#8220;okay&#8221;</literal></emphasis>
for a good processor.</para>
<para><literal>&#8220;okay&#8221;</literal> for a good processor.</para>
</listitem>
<listitem>
<para><emphasis role="bold"><literal>&#8220;fail&#8221;</literal></emphasis>
for a processor that fails during power-on testing.</para>
<para><literal>&#8220;fail&#8221;</literal> for a processor that fails during power-on testing.</para>
</listitem>
<listitem>
<para><emphasis role="bold"><literal>&#8220;fail-offline&#8221;</literal></emphasis>
<para><literal>&#8220;fail-offline&#8221;</literal>
for a processor that has been automatically deconfigured because of previous
failures.</para>
</listitem>
<listitem>
<para><emphasis role="bold"><literal>&#8220;disabled&#8221;</literal></emphasis>
<para><literal>&#8220;disabled&#8221;</literal>
for a processor that has been manually deconfigured.</para>
</listitem>
</itemizedlist>
@ -1189,7 +1187,7 @@
<varlistentry>
<term><emphasis role="bold"><literal>&#8220;ibm,processor-page-sizes&#8221;</literal></emphasis></term>
<listitem>
<para>property name: Relates the number and sizes of the virtual memory
<para><emphasis>property name</emphasis>: Relates the number and sizes of the virtual memory
page sizes supported by the processor describe by this node.</para>
<para><emphasis>prop-encoded-array</emphasis>: One to N cells in ascending
value order, each encoded as with
@ -1201,6 +1199,19 @@
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold"><literal>&#8220;ibm,processor-radix-AP-encodings&#8221;</literal></emphasis></term>
<listitem>
<para><emphasis>property name</emphasis>: Relates the AP (Actual Page size) encodings
for the supported page sizes used by the TLB management instructions when the processor
is in Radix address translation mode.</para>
<para><emphasis>prop-encoded-array</emphasis>: One to N cells in ascending order of
Radix mode supported page size, each encoded as with
<emphasis role="bold"><literal>encode-int</literal></emphasis>. The top 3 bits of the low order byte
contain the tlbie AP field associated with the corresponding Radix mode supported page size.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold"><literal>&#8220;ibm,processor-segment-sizes&#8221;</literal></emphasis></term>
<listitem>
@ -1996,12 +2007,12 @@
<para>0</para>
</entry>
<entry>
<para>2.07 Vector.XOR Support</para>
<para>2.07 Vector.CRYPTO Support</para>
</entry>
<entry>
<para>The value of 1 indicates that the vector.xor category as
<para>The value of 1 indicates that the vector.crypto category as
described by version 2.07 of POWER ISA is supported; else the
2.07 version vector.xor category is not supported.</para>
2.07 version vector.crypto category is not supported.</para>
</entry>
</row>
<row>

864
DeviceTree/ch_devtree_system.xml
View File

File diff suppressed because it is too large Load Diff

101
Error Handling/bk_main.xml
Unescape Escape View File

@ -42,7 +42,7 @@
<holder>OpenPOWER Foundation</holder>
</copyright>
<!-- TODO: Set the correct document releaseinfo -->
<releaseinfo>Revision 2.0_pre1</releaseinfo>
<releaseinfo>Revision 2.0_pre2</releaseinfo>
<productname>OpenPOWER</productname>
<pubdate/>

@ -70,6 +70,105 @@

<revhistory>
<!-- TODO: Update as new revisions created -->
<revision>
<date>2017-10-11</date>
<revdescription>
<itemizedlist spacing="compact">
<listitem>
<para>Revision 2.0_pre2 - Updates to include latest PAPR ACRs (2.8) as follows:</para>
<itemizedlist spacing="compact">
<listitem>
<para>ISA 2.07 privileged doorbell extensions (9/16/2012)</para>
</listitem>
<listitem>
<para>POWER ISA Name Change Category Vector.XOR to Vector.CRYPTO (11/4/2012)</para>
</listitem>
<listitem>
<para>Enable Multiple Redirected RDMA mappings per page (3/5/2013)</para>
</listitem>
<listitem>
<para>Add Block Invalidate Option (3/5/2013)</para>
</listitem>
<listitem>
<para>Implementation Dependent Optimizations (3/13/2013)</para>
</listitem>
<listitem>
<para>System Firmware Service Entitlement Date (Warranty Date) Check (4/3/2013)</para>
</listitem>
<listitem>
<para>New Function for ibm,change-msi to specify 32 bit MSI (5/14/2013)</para>
</listitem>
<listitem>
<para>Remove Client-Architecture-Support bit for UUID option (4/16/2013)</para>
</listitem>
<listitem>
<para>AddClient Architecture Support bit for RTAS ibm,change-msi (5/28/2013)</para>
</listitem>
<listitem>
<para>Add VNIC Server (5/24/2014)</para>
</listitem>
<listitem>
<para>VPA changes for P8 (EBB) (5/24/2013)</para>
</listitem>
<listitem>
<para>Add an hcall to clean up the entire MMU hashtable (11/20/2013)</para>
</listitem>
<listitem>
<para>Add LPCR[ILE] support to H_SET_MODE (5/31/2013)</para>
</listitem>
<listitem>
<para>New Root Node Properties (1/12/2016)</para>
</listitem>
<listitem>
<para>Extended Firmware Assisted Dump for P8 Registers (1/24/2014)</para>
</listitem>
<listitem>
<para>Sufficient H_COP_OP output buffer (6/21/2014)</para>
</listitem>
<listitem>
<para>Extend H_SEND_LOGICAL_LAN for large send packets (6/29/2014)</para>
</listitem>
<listitem>
<para>Extend H_GET_MPP_X reporting coalesced pages (8/24/2014)</para>
</listitem>
<listitem>
<para>Update ibm,pcie-link-speed-stats property to support PCIe 3.0 link speeds (6/12/2015)</para>
</listitem>
<listitem>
<para>Extend ibm,get-system-parameters RTAS to report Energy Management Tuning Parameters (3/18/2015)</para>
</listitem>
<listitem>
<para>Additional System Parameters related to mgmt of FW Service Entitlement Warranty period (6/22/2015)</para>
</listitem>
<listitem>
<para>Additional System Parameter to read LPAR Name string (10/7/2015)</para>
</listitem>
<listitem>
<para>Redesign of properties for DRC information and dynamic memory (7/23/2015)</para>
</listitem>
<listitem>
<para>Add additional logical loction code sections (3/4/2016)</para>
</listitem>
<listitem>
<para>Add ibm,vnic-client-mac to support vNIC failover (2/29/2016)</para>
</listitem>
<listitem>
<para>hcall for registering the process table (3/21/2016)</para>
</listitem>
<listitem>
<para>New device tree property for UUID (3/21/2016)</para>
</listitem>
<listitem>
<para>Changes for Hotplug RTAS Events (10/24/2016)</para>
</listitem>
<listitem>
<para>Support 64-bit PE TCEs in ibm,query-pe-dma-window (7/14/2016)</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</revdescription>
</revision>
<revision>
<date>2016-05-04</date>
<revdescription>

230
Error Handling/sec_rtas_error_reporting_return_format.xml
Unescape Escape View File

@ -466,8 +466,9 @@
later)</para>
<para>Dump notification event (228) (for Version 6 or
later)</para>
<para>Hot-plug-events (229) (for Version 6 or later)</para>
<para>&#160;</para>
<para>Vendor-specific events(229-255): Non-architected</para>
<para>Vendor-specific events(230-255): Non-architected</para>
<para>&#160;</para>
<para>Other (0): none of the above</para>
</entry>
@ -634,6 +635,9 @@
<para>For the EPOW Type, the EPOW section must be provided.</para>
</listitem>

<listitem>
<para>For the HOTPLUG Type, the Hotplug section must be provided.</para>
</listitem>
</orderedlist>
</listitem>
@ -1034,6 +1038,19 @@
<xref linkend="dbdoclet.50569337_54366"/>.</para>
</entry>
</row>
<row>
<entry>
<para>&#160;</para>
</entry>
<entry>
<para>???</para>
</entry>
<entry>
<para>Hotplug Section (ID = “HP”). Optional, present only for
Hotplug event notification. If present, this section follows
Main-B section. See <xref linkend="error.hotplug"/>.</para>
</entry>
</row>
<row>
<entry>
<para>...- 2047</para>
@ -4050,6 +4067,217 @@
</section>

<section xml:id="error.hotplug">
<title>Platform Event Log Format, Hotplug Section</title>
<table frame="all" pgwide="1" xml:id="table.error.hotplug">
<title>Platform Error Event Log Format, Version 6, Hotplug Section</title>
<tgroup cols="4">
<colspec colname="c1" colwidth="10*" align="center" />
<colspec colname="c2" colwidth="10*" align="center" />
<colspec colname="c3" colwidth="5*" />
<colspec colname="c4" colwidth="75*" />
<thead valign="top">
<row>
<entry>
<para><emphasis role="bold">Offset</emphasis></para>
</entry>
<entry>
<para><emphasis role="bold">Length in Bytes</emphasis></para>
</entry>
<entry namest='c3' nameend='c4' align="center">
<para><emphasis role="bold">Description</emphasis></para>
</entry>
</row>
</thead>
<tbody valign="top">
<row>
<entry>
<para>0x00</para>
</entry>
<entry>
<para>2</para>
</entry>
<entry namest='c3' nameend='c4'>
<para>Section ID: A two-ASCII character field which uniquely
identifies the type of section. Value = “HP”.</para>
</entry>
</row>
<row>
<entry>
<para>0x02</para>
</entry>
<entry>
<para>2</para>
</entry>
<entry namest='c3' nameend='c4' >
<para>Section length: Length in bytes of the section, including
the section ID.</para>
</entry>
</row>
<row>
<entry>
<para>0x04</para>
</entry>
<entry>
<para>1</para>
</entry>
<entry namest='c3' nameend='c4'>
<para>Section Version</para>
</entry>
</row>
<row>
<entry>
<para>0x05</para>
</entry>
<entry>
<para>1</para>
</entry>
<entry namest='c3' nameend='c4'>
<para>Section subType</para>
</entry>
</row>
<row>
<entry>
<para>0x06</para>
</entry>
<entry>
<para>2</para>
</entry>
<entry namest='c3' nameend='c4'>
<para>Creator Component ID</para>
</entry>
</row>
<row>
<entry>
<para>0x08</para>
</entry>
<entry>
<para>1</para>
</entry>
<entry namest='c3' nameend='c4'>
<para>Hotplug Resource Type.<?linebreak?>
0x01 = CPU<?linebreak?>
0x02 = Memory<?linebreak?>
0x03 = SLOT<?linebreak?>
0x04 = PHB<?linebreak?>
0x05 = PCI</para>
</entry>
</row>
<row>
<entry>
<para>0x09</para>
</entry>
<entry>
<para>1</para>
</entry>
<entry namest='c3' nameend='c4'>
<para>Hotplug Action<?linebreak?>
0x01 = Add<?linebreak?>
0x02 = Remove</para>
</entry>
</row>
<row>
<entry>
<para>0x0A</para>
</entry>
<entry>
<para>1</para>
</entry>
<entry namest='c3' nameend='c4'>
<para>Hotplug Identifier Type<?linebreak?>
0x01 = drc name, resource is identified by drc name<?linebreak?>
0x02 = drc index, resource is identified by drc index<?linebreak?>
0x03 = drc count, number of resources to act upon<?linebreak?>
0x04 = drc count indexed, number of resources to act upon beginning at the specified drc index</para>
</entry>
</row>

<row>
<entry morerows='3'>
<para>0x0B</para>
</entry>
<entry morerows='3'>
<para>1</para>
</entry>
<entry align="center">
<para><emphasis role="bold">Bit</emphasis></para>
</entry>
<entry align="center">
<para><emphasis role="bold">Hotplug Event Capability Description</emphasis></para>
</entry>
</row>
<row>
<entry align="center">
<para>0</para>
</entry>
<entry>
<para>1 = Hotplug Token Present</para>
</entry>
</row>
<row>
<entry align="center">
<para>1</para>
</entry>
<entry>
<para>0 = Transactional Request: When using “drc count”or “drc count indexed”as the Hotplug
Identifier, the OS should take steps to verify the entirety of the request can be satisfied
before proceeding with the hotplug / unplug operations. If only a partial count can be
satisfied, the OS should ignore the entirety of the request. If the OS cannot determine
this beforehand, it should satisfy the hotplug / unplug request for as many of the
requested resources as possible, and attempt to revert to the original OS / DRC state.</para>
<para>1 = Non-transactional Request: When using “drc count”or “drc count indexed”as the
Hotplug Identifier, the OS should attempt to satisfy as much of the request as possible,
even if it cannot be satisfied for all the DRCs specified.</para>
</entry>
</row>
<row>
<entry align="center">
<para>2:7</para>
</entry>
<entry>
<para>Reserved</para>
</entry>
</row>
<row>
<entry>
<para>0x0C</para>
</entry>
<entry>
<para>Variable</para>
</entry>
<entry namest='c3' nameend='c4' >
<para>Hotplug Identifier<?linebreak?>
Variable length field depending on the Hotplug Identifier Type specified.
For drc name, this field is a null-terminated ASCII character field containing
the drc name of the resource to hotplug.</para>
<para>For drc index, this is 4 byte field with the drc index of the resource to hotplug.</para>
<para>For drc count, this is a 4 byte field with the number of resources to hotplug.</para>
<para>For drc count indexed, this is two 4 byte fields the first being the number of resources
to hotplug and the second being the drc index at which to start.</para>
</entry>
</row>
<row>
<entry>
<para>(Section Length - 4)</para>
</entry>
<entry>
<para>4</para>
</entry>
<entry namest='c3' nameend='c4' >
<para>Hotplug Token<?linebreak?>
Present only if corresponding Hotplug Event Capability bit is set.</para>
<para>Integer value that can be used in conjunction with other fields of the hotplug
event structure (Hotplug Indentifier, Hotplug Type, etc.) to allow OS to associate
hotplug event with the request which generated it for the purposes of providing
feedback to the requestor, such as debugging or error information.</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
</section>
</section>

18
Error Handling/sec_rtas_hot_plug.xml
Unescape Escape View File

@ -23,11 +23,19 @@
<title>Hot Plug Events</title>
<para>Hot Plug Events, when implemented, are reported through the
event-scan RTAS call. These events are surfaced through the fixed
portions of the RTAS return value. (see
<xref linkend="dbdoclet.50569337_21249"/>) Some parts of the system may
be modified without direct support from the OS.</para>
<para>Hot Plug Events, when implemented, are reported through
either the event-scan RTAS call or a hotplug interrupt.</para>

<para>An OS that wants to be notified of hotplug events will need to
set the appropriate arch-vector bit. Look for the hot-plug-events
node in the /event-sources node of the OF device tree (see
<xref linkend="LoPAR.DeviceTree" />), enable the interrupts listed
in its “interrupts” property and provide an interrupt handler to call
check-exception when one of those interrupts are received.</para>

<para>When a hotplug event occurs, whether reported by check-exception
or event-scan, RTAS will directly pass back the Hotplug Event Log as
described in <xref linkend="table.error.hotplug" />.</para>
<variablelist>

101
Platform/bk_main.xml
Unescape Escape View File

@ -42,7 +42,7 @@
<holder>OpenPOWER Foundation</holder>
</copyright>
<!-- TODO: Set the correct document releaseinfo -->
<releaseinfo>Revision 2.0_pre1</releaseinfo>
<releaseinfo>Revision 2.0_pre2</releaseinfo>
<productname>OpenPOWER</productname>
<pubdate/>

@ -71,6 +71,105 @@

<revhistory>
<!-- TODO: Update as new revisions created -->
<revision>
<date>2017-10-11</date>
<revdescription>
<itemizedlist spacing="compact">
<listitem>
<para>Revision 2.0_pre2 - Updates to include latest PAPR ACRs (2.8) as follows:</para>
<itemizedlist spacing="compact">
<listitem>
<para>ISA 2.07 privileged doorbell extensions (9/16/2012)</para>
</listitem>
<listitem>
<para>POWER ISA Name Change Category Vector.XOR to Vector.CRYPTO (11/4/2012)</para>
</listitem>
<listitem>
<para>Enable Multiple Redirected RDMA mappings per page (3/5/2013)</para>
</listitem>
<listitem>
<para>Add Block Invalidate Option (3/5/2013)</para>
</listitem>
<listitem>
<para>Implementation Dependent Optimizations (3/13/2013)</para>
</listitem>
<listitem>
<para>System Firmware Service Entitlement Date (Warranty Date) Check (4/3/2013)</para>
</listitem>
<listitem>
<para>New Function for ibm,change-msi to specify 32 bit MSI (5/14/2013)</para>
</listitem>
<listitem>
<para>Remove Client-Architecture-Support bit for UUID option (4/16/2013)</para>
</listitem>
<listitem>
<para>AddClient Architecture Support bit for RTAS ibm,change-msi (5/28/2013)</para>
</listitem>
<listitem>
<para>Add VNIC Server (5/24/2014)</para>
</listitem>
<listitem>
<para>VPA changes for P8 (EBB) (5/24/2013)</para>
</listitem>
<listitem>
<para>Add an hcall to clean up the entire MMU hashtable (11/20/2013)</para>
</listitem>
<listitem>
<para>Add LPCR[ILE] support to H_SET_MODE (5/31/2013)</para>
</listitem>
<listitem>
<para>New Root Node Properties (1/12/2016)</para>
</listitem>
<listitem>
<para>Extended Firmware Assisted Dump for P8 Registers (1/24/2014)</para>
</listitem>
<listitem>
<para>Sufficient H_COP_OP output buffer (6/21/2014)</para>
</listitem>
<listitem>
<para>Extend H_SEND_LOGICAL_LAN for large send packets (6/29/2014)</para>
</listitem>
<listitem>
<para>Extend H_GET_MPP_X reporting coalesced pages (8/24/2014)</para>
</listitem>
<listitem>
<para>Update ibm,pcie-link-speed-stats property to support PCIe 3.0 link speeds (6/12/2015)</para>
</listitem>
<listitem>
<para>Extend ibm,get-system-parameters RTAS to report Energy Management Tuning Parameters (3/18/2015)</para>
</listitem>
<listitem>
<para>Additional System Parameters related to mgmt of FW Service Entitlement Warranty period (6/22/2015)</para>
</listitem>
<listitem>
<para>Additional System Parameter to read LPAR Name string (10/7/2015)</para>
</listitem>
<listitem>
<para>Redesign of properties for DRC information and dynamic memory (7/23/2015)</para>
</listitem>
<listitem>
<para>Add additional logical loction code sections (3/4/2016)</para>
</listitem>
<listitem>
<para>Add ibm,vnic-client-mac to support vNIC failover (2/29/2016)</para>
</listitem>
<listitem>
<para>hcall for registering the process table (3/21/2016)</para>
</listitem>
<listitem>
<para>New device tree property for UUID (3/21/2016)</para>
</listitem>
<listitem>
<para>Changes for Hotplug RTAS Events (10/24/2016)</para>
</listitem>
<listitem>
<para>Support 64-bit PE TCEs in ibm,query-pe-dma-window (7/14/2016)</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</revdescription>
</revision>
<revision>
<date>2016-05-04</date>
<revdescription>

273
Platform/ch_product_topology.xml
Unescape Escape View File

@ -771,7 +771,7 @@ xml:lang="en">
<para>A logical path location label consists of the prefix
&#x201C;L&#x201D; followed by a decimal or hexadecimal number with no leading
zeros. Refer to <xref linkend="dbdoclet.50569341_26909"/> through
<xref linkend="dbdoclet.50569341_35517"/> to determine when decimal and hexadecimal
<xref linkend="sec_nvme_device_logical_path_location_codes"/> to determine when decimal and hexadecimal
values are allowed. A location code may have zero or more logical path location
labels. When present, the logical path location label follows the location
label of the resource that interfaces with the resource being located, usually
@ -1124,20 +1124,30 @@ xml:lang="en">

<section xml:id="dbdoclet.50569341_32742">
<title>Virtual Card Connector Location Codes</title>
<para>Virtual card connector location codes are formed as though there
were a virtual planar with card slots. For example, a virtual IOA would have a
location code of form: </para>
<para>Virtual card connector location codes are formed as
though there were a virtual planar with card slots.
For example, the location code for a virtual IOA in partition
5 and in virtual slot 3 would be of the form:</para>
<itemizedlist mark="none">
<listitem>
<para>U9117.150.1054321-V5-C2</para>
<para>U9117.001.1076DEF-V5-C4</para>
</listitem>
</itemizedlist>
<para>The partition number 5 is specified in the V label
and the virtual slot number 3 is specified in the C
label. Also note that the U label specifies the system
type, model, and serial (the system location code),
not the enclosure type, model, and serial.</para>
<para>Some operating systems may append a T label
to the virtual IOA location code. For example:</para>
<itemizedlist mark="none">
<listitem>
<para>U9117.001.1076DEF-V5-C4-T1</para>
</listitem>
</itemizedlist>
<para>In the virtual card connector location code, the unit location
label specifies the system location code, not the CEC enclosure location
code.</para>
<para>It is recommended that the card connector location label have a
non-zero numeric part, for human factors reasons.</para>
</section>
<section xml:id="dbdoclet.50569341_26909">
<title>Port Location Codes</title>
<para>Port location codes are formed by appending the port location
@ -1241,8 +1251,7 @@ xml:lang="en">
</section>

<section>
<title>SCSI Device Logical Path Location Codes -- Real and
Virtual</title>
<title>SCSI Device Logical Path Location Codes -- Real</title>
<para>SCSI (Small Computer System Interface) devices whose parent does
not support location label VPD will have location codes that are composed of
the location code of the controlling SCSI port followed by the SCSI Target
@ -1255,24 +1264,6 @@ xml:lang="en">
(Decimal L values)</para>
</listitem>
</itemizedlist>

<para>For virtual SCSI, a 48-bit ID is currently used (but is not limited
from moving to 64-bit) to identify the attached virtualized SCSI device. This
48/64 bit ID is represented with a -L# in hexadecimal. There is no separate
LUN#. Examples are:</para>
<itemizedlist mark="none">
<listitem>
<para>U7043.150.1076543-P4-T1-L830000000000<?linebreak?>
(Hexadecimal L value)</para>
</listitem>
<listitem>
<para>or</para>
</listitem>
<listitem>
<para>U7043.150.1076543-P4-T3-W830000000000-L0 <?linebreak?>
(Hexadecimal W and L values)</para>
</listitem>
</itemizedlist>
</section>

<section>
@ -1319,7 +1310,7 @@ xml:lang="en">

<section>
<title>Fibre Channel Device Logical Path Location Codes --
Real and Virtual</title>
Real</title>
<para>Fibre channel devices that are not mounted/docked on a backplane
that supports location code VPD will have location codes composed of the
location of the port on the controlling IOA followed by the worldwide unique
@ -1332,15 +1323,6 @@ xml:lang="en">
<para>U787A.001.1012345-P1-C5-T2-W123456789ABCDEF0-L1A05000000000000</para>
</listitem>
</itemizedlist>

<para>The same disk being accessed through virtual fibre channel would
appear like:</para>
<itemizedlist mark="none">
<listitem>
<para>U9111.520.1012345-V2-C4-T1-W123456789ABCDEF0-L1A05000000000000</para>
</listitem>
</itemizedlist>
</section>

<section xml:id="dbdoclet.50569341_30561">
@ -1582,6 +1564,177 @@ xml:lang="en">
</itemizedlist>
</section>
</section>
<section xml:id="sec_resource_location_codes">
<title>Resource Location Codes</title>
<para>The resource location label consists of the
prefix 'R' followed by a non-zero decimal number. A
resource location code identifies a chip or function
embedded on a FRU. There may be multiple
resources associated with a FRU. The numbering of the
resources on a particular FRU should match
the left to right, top to bottom positioning of the
resources on the FRU when the FRU is in a typical
service position.</para>
<para>It should be noted that embedded adapters with
internal ports existed prior to introduction of the
resource label. Use of the resource label for unique
partitionable endpoint identification may or may
not be retrofitted to those adapters as they are
carried forward to new platforms.</para>
</section>
<section xml:id="sec_multiple_frus_same_physical_space">
<title>Multiple FRUs In The Same Physical Space</title>
<para>A physical location code is tied to the connector
that a FRU plugs into. If two different parts with
different part numbers can plug into the same connector,
both parts will have the same location code.
However, if two different parts can plug into two
different connectors but share the same physical
space when either is installed, those parts should
each have a different location code. For example, if
two different GX adapters (such as the Bjorn IB adapter
and Newcombe PCI slot riser on Jupiter-IOC)
connect to the same planar using the same connector,
they should both be assigned the same location
code. But if a GX adapter or a PCI adapter can be
installed on a planar, but not both at the same time
as they both can't fit at the same time given the
placement of the connectors on the planar, both slots
should be assigned unique location codes.</para>
</section>
<section xml:id="sec_pcie_attached_io_drawers">
<title>PCI-E Attached I/O Drawers</title>
<para>A PCI-E attached I/O drawer is an I/O drawer that
attaches to a GX adapter in the CEC via PCI-E
cables (as opposed to RIO or IB cables). There are two
different types of PCI-E attached I/O drawers:
ones where PHB(s) on the GX adapter connect directly
to I/O devices in the drawer and ones where the
PHB(s) on the GX adapter connect to switches (or other
fan-out logic) in the I/O drawer. In the former
case, the partitionable endpoint (PE) is the logical
PHB connection to the device. In the latter case, the
PEs are the slots wired to the downstream switch ports.</para>

<para>For GX cards whose PHBs connect directly to
devices in the I/O drawer (such as Bluehawk), the
location code and DRC name of the I/O slot partitionable
endpoint will be of the form Ucec-Pw-Cx-
Ty-Lz. Here, Ucec is the type/model/serial of the CEC
that contains the GX adapter, Pw is the planar
that contains the GX adapter, Cx is the GX adapter,
Ty is one of the ports on the adapter, and Lz is a
logical label representing a logical PCI-e connection
to an I/O device at the other end of the PCI-e
cable plugged into that port (note that there may be
multiple Cx labels if the GX adapter doesn't plug
directly into the planar in the system in question).
This location code and DRC name will be generated
by system firmware for each PE on each GX adapter that
is installed in the system and that supports
direct-connect drawers (i.e. drawers without a PCI-E
switch in them). The location code and DRC
name will be generated regardless of whether or not a
PCI-E cable is attached to the GX adapter.
It is permissible to append additional labels beyond
the L label to create different location codes for
FRUs/devices downstream from the I/O device in the
drawer that is attached to the PCI-e cable. It is
not required that all subsequent labels be logical labels.</para>

<para>For GX cards whose ports connect to a PCI-E switch
in an I/O drawer via PCI-E cables, the location
code format has not yet been defined.</para>
</section>
<section xml:id="sec_virtual_scsi_device_location_codes">
<title>Virtual SCSI (vSCSI) Device Location Codes</title>
<para>The location code for a virtual SCSI (vSCSI)
device is formed by appending an L label to the location
code of the parent virtual IOA. The L label contains a
48 or 64 bit hexadecimal value that uniquely
identifies the virtualized SCSI device. A virtual
SCSI device attached to a virtual IOA at
U9119.MME.1085B17-V4-C5-T1 would have a location code of the form:
U9119.MME.1085B17-V4-C5-T1-L8100000000000000
Note that some old pSeries firmware may represent
the virtualized device identifier as
W8100000000000000-L0 rather than simply L8100000000000000. This approach was abandoned in
late 2008.</para>
<para>See <xref linkend="dbdoclet.50569341_32742" /> for a description of the
virtual IOA location code.</para>
</section>
<section xml:id="sec_virtual_fibre_channel_device_location_codes">
<title>Virtual Fibre Channel Device Location Codes</title>
<para>The location code for a virtual fibre channel device
is formed by appending the worldwide unique port
identifier (W label) and LUN (L label) to the location
code of the parent virtual IOA. The values of
the L and W labels are both in hexadecimal. A fibre
channel disk attached to a virtual IOA at
U9119.MME.1085B17-V4-C5-T1 would have a location
code of the form:</para>
<itemizedlist mark="none">
<listitem>
<para>U9119.MME.1085B17-V2-C4-T1-W123456789ABCDEF0-L1A05000000000000</para>
</listitem>
</itemizedlist>
<para>See <xref linkend="dbdoclet.50569341_32742" /> for a description of the
virtual IOA location code.</para>
</section>
<section xml:id="sec_nvme_device_logical_path_location_codes">
<title>NVMe Device Logical Path Location Codes</title>
<para>Non-volatile memory (NVM) devices that are
not mounted/docked on a backplane that supports
location code VPD will have location codes composed
of the location code of the controlling IOA
followed by a L label. The number value of L label
is a decimal value, and it is the unique NVMe
namespace identifier. An NVMe device controlled by
an IOA at U787A.001.1012345-P1-C5 would
have a location code of the form:</para>
<itemizedlist mark="none">
<listitem>
<para>U787A.001.1012345-P1-C5-L3</para>
</listitem>
</itemizedlist>
</section>
<section xml:id="sec_virtual_capi_function_location_codes">
<title>Virtual Coherent Accelerator (CAPI) Function Location Codes</title>
<para>The location code for a virtual coherent accelerator
(CA) function is formed by appending two S labels,
the first specifying the identifier of the physical
function and the second specifying the identifier of the
logical function, both in decimal, to the location code of
the physical CAPI adapter. A virtual CA
function associated with physical function 1 and logical
function 2 on the CAPI adapter at location
U78CA.001.1234567-P1-C4-C1 would have location code:</para>
<itemizedlist mark="none">
<listitem>
<para>U78CA.001.1234567-P1-C4-C1-S1-S2</para>
</listitem>
</itemizedlist>
</section>
</section>

<section xml:id="dbdoclet.50569341_29745">
@ -2954,6 +3107,27 @@ xml:lang="en">
<para> Model Number: 3 characters with a leading blank.</para>
</entry>
</row>
<row>
<entry>
<para> ME </para>
</entry>
<entry>
<para> ASCII</para>
</entry>
<entry>
<para> 8</para>
</entry>
<entry>
<para> --</para>
</entry>
<entry>
<para>Microcode Service Entitlement Expiration Date</para>
<para>This is the date a customer's system firmware service warranty period
expires. System firmware images with MG dates that are later than a system's
ME date are not entitled to be flashed on that system.</para>
<para>Format:<?linebreak?>yyyymmdd</para>
</entry>
</row>
<row>
<entry>
<para> MF </para>
@ -2973,6 +3147,25 @@ xml:lang="en">
keyword.</para>
</entry>
</row>
<row>
<entry>
<para> MG </para>
</entry>
<entry>
<para> ASCII</para>
</entry>
<entry>
<para> 8</para>
</entry>
<entry>
<para> --</para>
</entry>
<entry>
<para>Microcode General Availability/Release Date</para>
<para>This is the date the system firmware image was released and published for customer use.</para>
<para>Format:<?linebreak?>yyyymmdd</para>
</entry>
</row>
<row>
<entry>
<para> MI </para>

60
Platform/ch_system_reqs.xml
Unescape Escape View File

@ -2460,7 +2460,7 @@ ELSE
</entry>
<entry>
<para>
<xref linkend="LoPAR.Virtualization"/>
<xref linkend="LoPAR.DeviceTree"/> for information on ibm,partition-uuid.
</para>
</entry>
</row>
@ -2493,6 +2493,64 @@ ELSE
functions see <xref linkend="LoPAR.Virtualization"/></para>
</entry>
</row>
<row>
<entry>
<para> Memory Usage Instrumentation Option (MUI)</para>
</entry>
<entry>
<para> O</para>
</entry>
<entry>
<para> O</para>
</entry>
<entry>
<para> See <xref linkend="LoPAR.Virtualization"/>.</para>
</entry>
</row>
<row>
<entry>
<para>Block Invalidate Option</para>
</entry>
<entry>
<para> O</para>
</entry>
<entry>
<para> O</para>
</entry>
<entry>
<para>Allows improved performance for removing page table entries representing a naturally aligned
block of virtual addresses.</para>
</entry>
</row>
<row>
<entry>
<para>Energy Management Tuning Parameters (EMTP)</para>
</entry>
<entry>
<para> O</para>
</entry>
<entry>
<para> O</para>
</entry>
<entry>
<para>Reports the system Energy Management tuning values.</para>
</entry>
</row>
<row>
<entry>
<para>In-Memory Table Translation Option</para>
</entry>
<entry>
<para> O</para>
</entry>
<entry>
<para> O</para>
</entry>
<entry>
<para>Provides support for the system wide Memory Management Unit
architecture introduced in POWER ISA 3.0</para>
</entry>
</row>
</tbody>
</tgroup>
</table>

2
README.md
Unescape Escape View File

@ -1,5 +1,5 @@
# Linux Architecture Reference Specification for OpenPOWER
This repository hold the source for the source for the
This repository holds the source for the
Linux on Power Architecture Reference documents. There are
multiple component documents as follows:


101
RTAS/bk_main.xml
Unescape Escape View File

@ -42,7 +42,7 @@
<holder>OpenPOWER Foundation</holder>
</copyright>
<!-- TODO: Set the correct document releaseinfo -->
<releaseinfo>Revision 2.0_pre1</releaseinfo>
<releaseinfo>Revision 2.0_pre2</releaseinfo>
<productname>OpenPOWER</productname>
<pubdate/>

@ -72,6 +72,105 @@
<revhistory>
<!-- TODO: Update as new revisions created -->
<revision>
<date>2017-10-11</date>
<revdescription>
<itemizedlist spacing="compact">
<listitem>
<para>Revision 2.0_pre2 - Updates to include latest PAPR ACRs (2.8) as follows:</para>
<itemizedlist spacing="compact">
<listitem>
<para>ISA 2.07 privileged doorbell extensions (9/16/2012)</para>
</listitem>
<listitem>
<para>POWER ISA Name Change Category Vector.XOR to Vector.CRYPTO (11/4/2012)</para>
</listitem>
<listitem>
<para>Enable Multiple Redirected RDMA mappings per page (3/5/2013)</para>
</listitem>
<listitem>
<para>Add Block Invalidate Option (3/5/2013)</para>
</listitem>
<listitem>
<para>Implementation Dependent Optimizations (3/13/2013)</para>
</listitem>
<listitem>
<para>System Firmware Service Entitlement Date (Warranty Date) Check (4/3/2013)</para>
</listitem>
<listitem>
<para>New Function for ibm,change-msi to specify 32 bit MSI (5/14/2013)</para>
</listitem>
<listitem>
<para>Remove Client-Architecture-Support bit for UUID option (4/16/2013)</para>
</listitem>
<listitem>
<para>AddClient Architecture Support bit for RTAS ibm,change-msi (5/28/2013)</para>
</listitem>
<listitem>
<para>Add VNIC Server (5/24/2014)</para>
</listitem>
<listitem>
<para>VPA changes for P8 (EBB) (5/24/2013)</para>
</listitem>
<listitem>
<para>Add an hcall to clean up the entire MMU hashtable (11/20/2013)</para>
</listitem>
<listitem>
<para>Add LPCR[ILE] support to H_SET_MODE (5/31/2013)</para>
</listitem>
<listitem>
<para>New Root Node Properties (1/12/2016)</para>
</listitem>
<listitem>
<para>Extended Firmware Assisted Dump for P8 Registers (1/24/2014)</para>
</listitem>
<listitem>
<para>Sufficient H_COP_OP output buffer (6/21/2014)</para>
</listitem>
<listitem>
<para>Extend H_SEND_LOGICAL_LAN for large send packets (6/29/2014)</para>
</listitem>
<listitem>
<para>Extend H_GET_MPP_X reporting coalesced pages (8/24/2014)</para>
</listitem>
<listitem>
<para>Update ibm,pcie-link-speed-stats property to support PCIe 3.0 link speeds (6/12/2015)</para>
</listitem>
<listitem>
<para>Extend ibm,get-system-parameters RTAS to report Energy Management Tuning Parameters (3/18/2015)</para>
</listitem>
<listitem>
<para>Additional System Parameters related to mgmt of FW Service Entitlement Warranty period (6/22/2015)</para>
</listitem>
<listitem>
<para>Additional System Parameter to read LPAR Name string (10/7/2015)</para>
</listitem>
<listitem>
<para>Redesign of properties for DRC information and dynamic memory (7/23/2015)</para>
</listitem>
<listitem>
<para>Add additional logical loction code sections (3/4/2016)</para>
</listitem>
<listitem>
<para>Add ibm,vnic-client-mac to support vNIC failover (2/29/2016)</para>
</listitem>
<listitem>
<para>hcall for registering the process table (3/21/2016)</para>
</listitem>
<listitem>
<para>New device tree property for UUID (3/21/2016)</para>
</listitem>
<listitem>
<para>Changes for Hotplug RTAS Events (10/24/2016)</para>
</listitem>
<listitem>
<para>Support 64-bit PE TCEs in ibm,query-pe-dma-window (7/14/2016)</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</revdescription>
</revision>
R <revision>
<date>2016-05-04</date>
<revdescription>
<itemizedlist spacing="compact">

2187
RTAS/ch_firmware_dump.xml
View File

File diff suppressed because it is too large Load Diff

562
RTAS/ch_rtas_call_defn.xml
Unescape Escape View File

@ -8811,6 +8811,22 @@
<para>&#8220;ML&#8221;&lt;sp&gt; new-T-image &lt;sp&gt;
new-P-image &lt;0x00&gt;</para>
</listitem>

<listitem>
<para>&#8220;MG&#8221;&lt;sp&gt;current-T-img-ga-date&lt;sp&gt;current-P-img-ga-date&lt;0x0A&gt;</para>
</listitem>
<listitem>
<para>&#8220;MG&#8221;&lt;sp&gt;new-T-img-ga-date&lt;sp&gt;new-P-img-ga-date&lt;0x0A&gt;</para>
</listitem>
<listitem>
<para>&#8220;MG&#8221;&lt;sp&gt;input-image-ga-date&lt;0x0A&gt;</para>
</listitem>

<listitem>
<para>&#8220;ME&#8221;&lt;sp&gt;fw-service-entitlement-expiration-date&lt;0x00&gt;</para>
</listitem>
</itemizedlist>
<para>In Requirement
@ -8915,6 +8931,16 @@
<para>T side will be updated with a downlevel image</para>
</entry>
</row>
<row>
<entry>
<para>7</para>
</entry>
<entry>
<para>No update done, the candidate image's release date is later
than the system's firmware service entitlement date - service
warranty period has expired</para>
</entry>
</row>
<row>
<entry>
<para>0</para>
@ -11442,7 +11468,7 @@
specifies that the platform implements the version of this RTAS call that
allows
<emphasis>Number Outputs</emphasis> equal to 4 and
<emphasis>Functions</emphasis> 3 and 4.</para>
<emphasis>Functions</emphasis> 3, 4 and 5.</para>
<para>If the
<emphasis>ibm,change-msi</emphasis> RTAS call is made with
<emphasis>Number Outputs</emphasis> equal to 4 or with
@ -11475,8 +11501,7 @@
<xref linkend="dbdoclet.50569332_69854" />.</para>
<table frame="all" pgwide="1" xml:id="dbdoclet.50569332_69854">
<title>Argument Call Buffer
<emphasis>ibm,change-msi</emphasis></title>
<title><emphasis>ibm,change-msi</emphasis> Argument Call Buffer</title>
<tgroup cols="3">
<colspec colname="c1" colwidth="33*" />
<colspec colname="c2" colwidth="33*" />
@ -11607,6 +11632,11 @@
&#8220;ibm,change-msix-capable&#8221;</literal></emphasis> exists):
Request to set to a new number of MSI-X interrupts (including
set to 0)</para>
<para>5: (Only valid if
<emphasis role="bold"><literal>
&#8220;ibm,change-msix-capable&#8221;</literal></emphasis> exists):
Request to set to a new number of 32 bit MSI (including set to 0)
disregarding the adapter capability to support 64 bit MSI.</para>
</entry>
</row>
<row>
@ -11620,8 +11650,7 @@
configuration address. A value of 0 is specified in order to
remove all MSIs for the PCI configuration address. This input
parameter is ignored by RTAS for
<emphasis>Function</emphasis> values other than 1, 3, or
4.</para>
<emphasis>Function</emphasis> values other than 1, 3, 4 or 5.</para>
</entry>
</row>
<row>
@ -11943,6 +11972,13 @@
<emphasis>ibm,change-msi</emphasis> to increase the number of interrupts
may produce a greater number of interrupts.</para>
</listitem>
<listitem>
<para>The platform will return a status -2 or 990x only when the OS
indicates support. The OS indicates support via ibm,client-architecture-support,
vector 4. See <xref linkend="LoPAR.DeviceTree" /> section on "Root Node Methods"
for more information.</para>
</listitem>
</orderedlist>
</section>
@ -18905,15 +18941,13 @@
<para>48</para>
</entry>
<entry>
<para>UUID</para>
<para>Reserved</para>
</entry>
<entry>
<para>16 Byte String</para>
<para>&#160;</para>
</entry>
<entry>
<para>
<xref linkend="dbdoclet.50569332_97508" />
</para>
<para>&#160;</para>
</entry>
<entry>
<para>&#160;</para>
@ -18921,7 +18955,130 @@
</row>
<row>
<entry>
<para>&gt;48</para>
<para>49</para>
</entry>
<entry>
<para>Reserved</para>
</entry>
<entry>
<para>&#160;</para>
</entry>
<entry>
<para>&#160;</para>
</entry>
<entry>
<para>&#160;</para>
</entry>
</row>
<row>
<entry>
<para>50</para>
</entry>
<entry>
<para>TLB Block Invalidate Characteristics</para>
</entry>
<entry>
<para>Variable Length Series of Bytes</para>
</entry>
<entry>
<para>See <xref linkend="sec_tlb_block_invalidate" /></para>
</entry>
<entry>
<para>&#160;</para>
</entry>
</row>
<row>
<entry>
<para>51</para>
</entry>
<entry>
<para>Reserved</para>
</entry>
<entry>
<para>&#160;</para>
</entry>
<entry>
<para>&#160;</para>
</entry>
<entry>
<para>&#160;</para>
</entry>
</row>
<row>
<entry>
<para>52</para>
</entry>
<entry>
<para>Energy Management Tuning Parameters</para>
</entry>
<entry>
<para>Series of 8 byte entries of bytes encoding the tuning parameters supported by the system</para>
</entry>
<entry>
<para>See <xref linkend="sec_energy_management_tuning_parameters" /></para>
</entry>
<entry>
<para>Used by <emphasis>ibm,get-system-parameter</emphasis>; not supported for
<emphasis>ibm,set-system-parameter</emphasis>.</para>
</entry>
</row>
<row>
<entry>
<para>53</para>
</entry>
<entry>
<para>Firmware Service Expiration Date</para>
</entry>
<entry>
<para>This is the date a system's system firmware service warranty
period expires. </para>
</entry>
<entry>
<para>8-character null-terminated ASCII string in YYYYMMDD format</para>
</entry>
<entry>
<para>Used by <emphasis>ibm,get-system-parameter</emphasis>; not supported for
<emphasis>ibm,set-system-parameter</emphasis>.</para>
</entry>
</row>
<row>
<entry>
<para>54</para>
</entry>
<entry>
<para>Firmware Service Entitlement Activation Key</para>
</entry>
<entry>
<para>This is the activation key used to set or extend a system's firmware service
warranty period.</para>
</entry>
<entry>
<para>34-character null-terminated ASCII string key value</para>
</entry>
<entry>
<para>Used by ibm,set-system-parameter; not supported for ibm,get-system-parameter</para>
</entry>
</row>
<row>
<entry>
<para>55</para>
</entry>
<entry>
<para>LPAR Name</para>
</entry>
<entry>
<para>Logical Partition name</para>
</entry>
<entry>
<para>Null-terminated ASCII string</para>
</entry>
<entry>
<para>Used by ibm,set-system-parameter; not supported for ibm,get-system-parameter</para>
</entry>
</row>
<row>
<entry>
<para>&gt;55</para>
</entry>
<entry>
<para>Reserved</para>
@ -24521,136 +24678,326 @@
</section>
<section xml:id="dbdoclet.50569332_97508">
<title>Universally Unique IDentifier</title>
<para>The Universally Unique IDentifier (UUID) option provides each
partition with a Universally Unique Identifier that is persisted by the
platform across partition reboots, reconfigurations, OS reinstalls,
partition migration, hibernation etc. The UUID is a 16 byte string of
format fields and random bits as defined in
<xref linkend="dbdoclet.50569332_20419" />. The random bits are generated
in an implementation dependent manner to achieve a projected probability
of collision of not greater than one in 2**60.</para>
<section xml:id="sec_tlb_block_invalidate">
<title>TLB Block Invalidate Characteristics</title>
<para>The Block Invalidate option allows for the removal of multiple page table entries with a single platform wide TLB invalidate
sequence, providing significantly improved performance when removing a virtual memory object. The size of
the block (the number of consecutive virtual memory pages) that is processed by a single TLB invalidate sequence is
implementation dependent. This block size might also be dependent upon the page sizes of the TLB entries. This block
size represents the upper bound of the number of pages that may be processed in a single operation as for example a
single call to H_BLOCK_REMOVE. This system parameter provides the client code the characteristics of the implementation’s
TLB invalidate operations. The TLB Invalidate Characteristics return string is a variable length series of
bytes which contains one or more TLB Block Invalidate Specifiers as defined in Table 108‚ “TLB Block Invalidate
Characteristics Specifier Format‚” on page 253. If the implementation invalidates different sized blocks for different
page size encodings, there will be multiple “TLB Block Invalidate Characteristics Specifiers” within the returned
string.</para>
<table frame="all" pgwide="1" xml:id="dbdoclet.50569332_20419">
<title>UUID Format</title>
<tgroup cols="4">
<colspec colname="c1" colwidth="25*" />
<colspec colname="c2" colwidth="25*" />
<colspec colname="c3" colwidth="25*" />
<colspec colname="c4" colwidth="25*" />
<thead>
<table xml:id="table_tlb_block_invalidate_format">
<title>TLB Block Invalidate Characteristics Specifier Format</title>
<tgroup cols="3">
<colspec colname="c1" colwidth="10*" align="center" />
<colspec colname="c2" colwidth="15*" align="center" />
<colspec colname="c3" colwidth="75*" />
<thead valign="middle">
<row>
<entry>
<para>
<emphasis role="bold">Field</emphasis>
</para>
</entry>
<entry>
<para>
<emphasis role="bold">Byte:Bit</emphasis>
</para>
<para>Byte Offset</para>
</entry>
<entry>
<para>
<emphasis role="bold">Size (Bits)</emphasis>
</para>
<para>Bit Number in Byte</para>
</entry>
<entry>
<para>
<emphasis role="bold">Values</emphasis>
</para>
<entry align="center">
<para>Description</para>
</entry>
</row>
</thead>
<tbody>
<tbody valign="middle">
<row>
<entry>
<para>Version</para>
<para>0</para>
</entry>
<entry>
<para>0:0</para>
<para>0 - 7</para>
</entry>
<entry>
<para>1</para>
</entry>
<entry>
<para>0: Initial Version</para>
<para>1: Reserved</para>
<para>LOG base 2 of the TLB invalidate block size being specified</para>
</entry>
</row>
<row>
<entry>
<para>Random Bits</para>
</entry>
<entry>
<para>0:1 thru 5:7</para>
<para>1</para>
</entry>
<entry>
<para>47</para>
<para>0 - 7</para>
</entry>
<entry>
<para>Random Bits</para>
<para>Number of page sizes (N) that are supported for the specified TLB invalidate block size</para>
</entry>
</row>
<row>
<entry>
<para>Generation Method</para>
</entry>
<entry>
<para>6:0-3</para>
<entry morerows="2">
<para>2 - (N+1)</para>
</entry>
<entry>
<para>4</para>
<para>0</para>
</entry>
<entry>
<para>0b0000 Never Used</para>
<para>0b0100 Random Generated</para>
<para>All other values are reserved</para>
<para>PTE “L” bit:<?linebreak?>
0 = 4K page in a segment who’s base page size is 4K<?linebreak?>
1 = page size and segment base size per bits 2 - 7</para>
</entry>
</row>
<row>
<entry>
<para>Random Bits</para>
<para>1</para>
</entry>
<entry>
<para>6:4 - 7:7</para>
<para>Reserved</para>
</entry>
</row>
<row>
<entry>
<para>12</para>
<para>2 - 7</para>
</entry>
<entry>
<para>Random Bits</para>
<para>Encoded segment base page size and actual page size per
<xref linkend="dbdoclet.50569387_99718" /> Book IVa</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
<variablelist>
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="sec_tlb_block_invalidate"
xrefstyle="select: labelnumber nopage"/>-1.</emphasis></term>
<listitem>
<para><emphasis role="bold">For the Block Invalidate option with the
System Parameters option:</emphasis> For the Block Invalidate system
parameter, the <emphasis>ibm,get-system-parameter</emphasis> RTAS call must
never return a Status of -9002 (Not Authorized).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="sec_tlb_block_invalidate"
xrefstyle="select: labelnumber nopage"/>-2.</emphasis></term>
<listitem>
<para><emphasis role="bold">For the Block Invalidate option with the
System Parameters option:</emphasis> If the Block Invalidate option
is enabled for the partition, the platform must provide in response
to the <emphasis>ibm,get-system-parameter</emphasis> for
parameter token 50 the one or more TLB Block Invalidate
Specifiers for the calling partition as described in
<xref linkend="table_tlb_block_invalidate_format" />.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="sec_tlb_block_invalidate"
xrefstyle="select: labelnumber nopage"/>-3.</emphasis></term>
<listitem>
<para><emphasis role="bold">For the Block Invalidate option with the
System Parameters option:</emphasis> If the Block Invalidate
option is disabled for the system/partition, the platform must
provide in response to the <emphasis>ibm,get-system-parameter</emphasis>
for parameter token 50 the two byte value 0x0000.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="sec_tlb_block_invalidate"
xrefstyle="select: labelnumber nopage"/>-4.</emphasis></term>
<listitem>
<para><emphasis role="bold">For the Block Invalidate option with the
System Parameters option:</emphasis> For the Block Invalidate
system parameter, the <emphasis>ibm,get-system-parameter</emphasis>RTAS call must
always return a Status of -9002 (Setting not allowed/authorized).</para>
</listitem>
</varlistentry>
</variablelist>

</section>
<section xml:id="sec_energy_management_tuning_parameters">
<title>Energy Management Tuning Parameters (EMTP)</title>
<para>The energy management tuning parameters are reported. Each parameter occupies
its own 8 byte self-defining entry. As many energy management tuning parameter entries
as are supported by the system are reported, subject to the limitation of the buffer
length. Each reported parameter entry is formatted per
<xref linkend="table_format_emtp_entry" />.</para>
<table xml:id="table_format_emtp_entry">
<title>Format of the Energy Management Tuning Parameter Entry</title>
<tgroup cols="8">
<colspec colname="c1" colwidth="12*" align="center" />
<colspec colname="c2" colwidth="12*" align="center" />
<colspec colname="c3" colwidth="12*" align="center" />
<colspec colname="c4" colwidth="12*" align="center" />
<colspec colname="c5" colwidth="12*" align="center" />
<colspec colname="c6" colwidth="12*" align="center" />
<colspec colname="c7" colwidth="12*" align="center" />
<colspec colname="c8" colwidth="12*" align="center" />
<thead valign="middle">
<row>
<entry><para>Byte 0</para></entry>
<entry><para>Byte 1</para></entry>
<entry><para>Byte 2</para></entry>
<entry><para>Byte 3</para></entry>
<entry><para>Byte 4</para></entry>
<entry><para>Byte 5</para></entry>
<entry><para>Byte 6</para></entry>
<entry><para>Byte 7</para></entry>
</row>
</thead>
<tbody valign="middle">
<row>
<entry>
<para>Variant</para>
<para>Parameter Identifier<?linebreak?>See <xref linkend="table_definition_emtp_parms" />
for definition values.</para>
</entry>
<entry>
<para>8:0-1</para>
<para>Parameter Units<?linebreak?>See <xref linkend="table_definition_emtp_parm_unit_vals" />
for definition values.</para>
</entry>
<entry>
<para>2</para>
<entry namest="c3" nameend="c4">
<para>Current<?linebreak?>Parameter Value</para>
</entry>
<entry>
<para>0b10 DCE Variant UUID</para>
<para>All other values are reserved</para>
<entry namest="c5" nameend="c6">
<para>Minimum<?linebreak?>Parameter Value</para>
</entry>
<entry namest="c7" nameend="c8">
<para>Maximum<?linebreak?>Parameter Value</para>
</entry>
</row>
</tbody>
</tgroup>
</table>

<table xml:id="table_definition_emtp_parms">
<title>Definition of the Energy Management Tuning Parameters</title>
<tgroup cols="2">
<colspec colname="c1" colwidth="20*" align="center" />
<colspec colname="c2" colwidth="80*" />
<thead valign="middle">
<row>
<entry><para>Parameter ID</para></entry>
<entry align="center"><para>Definition</para></entry>
</row>
</thead>
<tbody valign="middle">
<row>
<entry><para>0x01</para></entry>
<entry><para>Utilization threshold for increasing frequency</para></entry>
</row>
<row>
<entry><para>0x02</para></entry>
<entry><para>Utilization threshold for decreasing frequency</para></entry>
</row>
<row>
<entry><para>0x03</para></entry>
<entry><para>Number of samples for computing utilization statistics</para></entry>
</row>
<row>
<entry><para>0x04</para></entry>
<entry><para>Step size for going up in frequency</para></entry>
</row>
<row>
<entry><para>0x05</para></entry>
<entry><para>Step size for going down in frequency</para></entry>
</row>
<row>
<entry><para>0x06</para></entry>
<entry><para>Delta percentage for determining active cores</para></entry>
</row>
<row>
<entry><para>0x07</para></entry>
<entry><para>Utilization threshold to determine active cores with slack</para></entry>
</row>
<row>
<entry><para>0x08</para></entry>
<entry><para>Enable/Disable frequency delta between cores</para></entry>
</row>
<row>
<entry><para>0x09</para></entry>
<entry><para>Maximum frequency delta between cores</para></entry>
</row>
<row>
<entry namest="c1" nameend="c2"><para>&#160;</para></entry>
</row>
<row>
<entry><para>0x50</para></entry>
<entry><para>Idle Power Saver enabled/disabled</para></entry>
</row>
<row>
<entry><para>0x51</para></entry>
<entry><para>Delay time to enter Idle Power Saver</para></entry>
</row>
<row>
<entry><para>0x52</para></entry>
<entry><para>Utilization threshold to enter Idle Power Saver</para></entry>
</row>
<row>
<entry><para>0x53</para></entry>
<entry><para>Delay time to exit Idle Power Saver</para></entry>
</row>
<row>
<entry><para>0x54</para></entry>
<entry><para>Utilization threshold to exit Idle Power Saver</para></entry>
</row>
<row>
<entry><para>&#160;</para></entry>
<entry>
<para>Random Bits</para>
</entry>
<entry>
<para>8:2 - 15:7</para>
</entry>
<entry>
<para>62</para>
<para>All other Parameter ID Values are reserved, should calling software
encounter a parameter id value which was reserved at the time it was
written, it shall ignore the specific entry, and only that entry.</para>
</entry>
</row>
</tbody>
</tgroup>
</table>

<table xml:id="table_definition_emtp_parm_unit_vals">
<title>Definition of the Energy Management Parameter Unit Values</title>
<tgroup cols="2">
<colspec colname="c1" colwidth="20*" align="center" />
<colspec colname="c2" colwidth="80*" />
<thead valign="middle">
<row>
<entry><para>Parameter Units</para></entry>
<entry align="center"><para>Definition</para></entry>
</row>
</thead>
<tbody valign="middle">
<row>
<entry><para>0x00</para></entry>
<entry><para>Parameter can only be either 1 (enabled) or 0 (disabled)</para></entry>
</row>
<row>
<entry><para>0x01</para></entry>
<entry><para>Parameter is time in seconds i.e. 10 = 10 seconds</para></entry>
</row>
<row>
<entry><para>0x02</para></entry>
<entry><para>Parameter is a percentage i.e. 10 = 10%</para></entry>
</row>
<row>
<entry><para>0x03</para></entry>
<entry><para>Parameter is in 10ths of a percent i.e. 15 = 1.5%</para></entry>
</row>
<row>
<entry><para>0x04</para></entry>
<entry><para>Parameter is an integer</para></entry>
</row>
<row>
<entry><para>&#160;</para></entry>
<entry>
<para>Random Bits</para>
<para>All other Parameter Unit Values are reserved, should calling software
encounter a parameter unit value which was reserved at the time it was
written, it shall ignore the specific entry, and only that entry.</para>
</entry>
</row>
</tbody>
@ -24659,49 +25006,44 @@

<variablelist>
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="dbdoclet.50569332_97508"
<term><emphasis role="bold">R1-<xref linkend="sec_energy_management_tuning_parameters"
xrefstyle="select: labelnumber nopage"/>-1.</emphasis></term>
<listitem>
<para><emphasis role="bold">For the UUID option with the System Parameters
option:</emphasis> For the UUID system parameter, the
<emphasis>ibm,get-system-parameter</emphasis> RTAS call must never return
a Status of -9002 (Not Authorized).</para>
<para><emphasis role="bold">For the EMTP option with the System Parameters option:</emphasis>
For the EMTP system parameter, the <emphasis>ibm,get-system-parameter</emphasis> RTAS call
must never return a Status of -9002 (Not Authorized).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="dbdoclet.50569332_97508"
<term><emphasis role="bold">R1-<xref linkend="sec_energy_management_tuning_parameters"
xrefstyle="select: labelnumber nopage"/>-2.</emphasis></term>
<listitem>
<para><emphasis role="bold">For the UUID option with the System Parameters
option:</emphasis> If the UUID option is enabled for the partition, the
platform must provide in response to the
<emphasis>ibm,getsystem-parameter</emphasis> for parameter token 48 the
calling partition unique 16 byte sting as described in
<xref linkend="dbdoclet.50569332_20419" />.</para>
<para><emphasis role="bold">For the EMTP option with the System Parameters option:</emphasis>
If the EMTP option is enabled for the partition, the platform must provide in response to the
<emphasis>ibm,get-system-parameter</emphasis> for parameter token 52 the Energy Management
Tuning Parameters for the calling system as described in this section.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="dbdoclet.50569332_97508"
<term><emphasis role="bold">R1-<xref linkend="sec_energy_management_tuning_parameters"
xrefstyle="select: labelnumber nopage"/>-3.</emphasis></term>
<listitem>
<para><emphasis role="bold">For the UUID option with the System Parameters
option:</emphasis> If the UUID option is disabled for the
system/partition, the platform must provide in response to the
<emphasis>ibm,get-system-parameter</emphasis> for parameter token 48 the
<para><emphasis role="bold">For the EMTP option with the System Parameters option:</emphasis>
If the EMTP option is disabled for the system/partition, the platform must provide in
response to the <emphasis>ibm,get-system-parameter</emphasis> for parameter token 52 the
two byte value 0x0000.</para>
</listitem>
</varlistentry>
<varlistentry xml:id="dbdoclet.50569332_64091">
<term><emphasis role="bold">R1-<xref linkend="dbdoclet.50569332_97508"
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="sec_energy_management_tuning_parameters"
xrefstyle="select: labelnumber nopage"/>-4.</emphasis></term>
<listitem>
<para><emphasis role="bold">For the UUID option with the System Parameters
option:</emphasis> For the UUID system parameter, the
<emphasis>ibm,set-system-parameter</emphasis> RTAS call must always return
a Status of -9002 (Setting not allowed/authorized).</para>
<para><emphasis role="bold">For the EMTP option with the System Parameters option:</emphasis>
For the EMTP system parameter, the <emphasis>ibm,set-system-parameter</emphasis> RTAS call
must always return a Status of -9002 (Setting not allowed/authorized).</para>
</listitem>
</varlistentry>
</variablelist>

4
RTAS/ch_rtas_environment.xml
Unescape Escape View File

@ -1541,7 +1541,7 @@
<emphasis role="bold"><literal>&#8220;ibm,get-indices&#8221;</literal></emphasis>
</para>
<para>
<xref linkend="dbdoclet.50569332_64091" />
<xref linkend="sec_get_indices_rtas_call" />
</para>
</entry>
<entry>
@ -1934,7 +1934,7 @@
time and do not change. Information about non-DR dynamic indicators and
sensors, needs to be gathered via the
<emphasis>ibm,get-indices</emphasis> RTAS call (see
<xref linkend="dbdoclet.50569332_64091" />), and sensors, instead of
<xref linkend="sec_get_indices_rtas_call" />), and sensors, instead of
being represented in the device tree.</para>
<para>Indicators and sensors within a platform generally have location
codes associated with them. Location code information for static

205
RTAS/sec_rtas_get_indices.xml
Unescape Escape View File

@ -454,7 +454,7 @@
</variablelist>

<section xml:id="dbdoclet.50569332_30542">
<title>RTAS Call <emphasis>ibm,set-dynamic-indicator</emphasis></title>
<title><emphasis>ibm,set-dynamic-indicator</emphasis> RTAS Call</title>
<para>This RTAS call behaves as the RTAS
<emphasis>set-indicator</emphasis> call, except that the instance of the
@ -711,7 +711,7 @@
</section>
<section xml:id="dbdoclet.50569332_61055">
<title>RTAS Call <emphasis>ibm,get-dynamic-sensor-state</emphasis></title>
<title><emphasis>ibm,get-dynamic-sensor-state</emphasis> RTAS Call</title>
<para>This RTAS call behaves as the RTAS
<emphasis>get-sensor-state</emphasis> call, except that the instance of
the sensor is identified by a location code instead of a index.</para>
@ -978,7 +978,7 @@
</section>
<section xml:id="dbdoclet.50569332_72964">
<title>RTAS Call <emphasis>ibm,get-vpd</emphasis></title>
<title><emphasis>ibm,get-vpd</emphasis> RTAS Call</title>
<para>This RTAS call allows for collection of VPD that changes after OS
boot time (after the initial reporting in the OF device tree). When this
call is implemented, there is no overlap between what is reported in the
@ -1853,7 +1853,7 @@
</section>
<section xml:id="dbdoclet.50569332_45918">
<title>RTAS Call <emphasis>ibm,suspend-me</emphasis></title>
<title><emphasis>ibm,suspend-me</emphasis> RTAS Call</title>
<para>The
<emphasis>ibm,suspend-me</emphasis> RTAS call provides the calling OS the
ability to suspend processing. Suspension of processing is required as
@ -2504,7 +2504,7 @@
</section>
<section xml:id="dbdoclet.50569332_84414">
<title>RTAS Call <emphasis>ibm,update-nodes</emphasis></title>
<title><emphasis>ibm,update-nodes</emphasis> RTAS Call</title>
<para>This RTAS call is used to determine which device tree nodes have
changed due to a massive platform reconfiguration such as when the
@ -2537,13 +2537,13 @@
<listitem>
<para>The opcode of 0x01 is used for deleted nodes -- the operands are
the
<emphasis>phandle</emphasis> values for the deleted nodes.</para>
<emphasis role="bold">phandle</emphasis> values for the deleted nodes.</para>
</listitem>
<listitem>
<para>The opcode of 0x02 is used for updated nodes -- the operands are
the
<emphasis>phandle</emphasis> values for the updated nodes. The updated
<emphasis role="bold">phandle</emphasis> values for the updated nodes. The updated
properties are obtained using the
<emphasis>ibm,update-properties</emphasis> RTAS call.</para>
</listitem>
@ -2551,11 +2551,11 @@
<listitem>
<para>The opcode of 0x03 is used for adding nodes -- the operands are
pairs of
<emphasis>phandle</emphasis> and
<emphasis>ibm,drc-index</emphasis> values; the
<emphasis>phandle</emphasis> value denotes the parent node of the node to
<emphasis role="bold">phandle</emphasis> and
<emphasis role="bold">drc-index</emphasis> values; the
<emphasis role="bold">phandle</emphasis> value denotes the parent node of the node to
be added and the
<emphasis>ibm,drc-index</emphasis> value is passed with the
<emphasis role="bold">ibm,drc-index</emphasis> value is passed with the
<emphasis>ibm,configure-connector</emphasis> RTAS call to obtain the
contents of the added node.</para>
</listitem>
@ -2565,8 +2565,8 @@
(delete) operations (if any) are presented prior to all opcode 0x02
(update) operations (if any), and finally any 0x03 (addition) operations
are presented. The
<emphasis>phandle</emphasis> operand values are the same
<emphasis>phandle</emphasis> values as reported by the
<emphasis role="bold">phandle</emphasis> operand values are the same
<emphasis role="bold">phandle</emphasis> values as reported by the
<emphasis role="bold"><literal>&#8220;ibm,phandle&#8221;</literal></emphasis> property.</para>

<variablelist>
@ -2847,7 +2847,7 @@
<para>The operands for opcode 0x01 in an
<emphasis>ibm,update-nodes</emphasis> RTAS call operation list must be the
<emphasis>phandle</emphasis> values for the deleted nodes.</para>
<emphasis role="bold">phandle</emphasis> values for the deleted nodes.</para>
</listitem>
</varlistentry>
@ -2867,7 +2867,7 @@
<listitem>
<para>The operands for opcode 0x02 in an
<emphasis>ibm,update-nodes</emphasis> RTAS call operation list must be the
<emphasis>phandle</emphasis> values for the updated nodes that may be used
<emphasis role="bold">phandle</emphasis> values for the updated nodes that may be used
as the
<emphasis>ibm,update-properties</emphasis> RTAS call argument to obtain
the changed properties of the updated node.</para>
@ -2890,8 +2890,8 @@
<listitem>
<para>The operands for opcode of 0x03 in an
<emphasis>ibm,update-nodes</emphasis> RTAS call operation list must be
<emphasis>phandle</emphasis> and
<emphasis>ibm,drc-index</emphasis> value pairs (each value being 4 bytes
<emphasis role="bold">phandle</emphasis> and
<emphasis role="bold">drc-index</emphasis> value pairs (each value being 4 bytes
on a natural boundary totalling 8 bytes for the pair) denoting the parent
node of the added node and the
<emphasis>ibm,configure-connector</emphasis> RTAS call argument to obtain
@ -3005,7 +3005,7 @@
</thead>
<tbody>
<row>
<entry morerows="6">
<entry morerows="7">
<para>Negative values: Platform Resource Reassignment events as
from
<emphasis>event-scan</emphasis> RTAS</para>
@ -3074,7 +3074,17 @@
</entry>
</row>
<row>
<entry morerows="12">
<entry>
<para>
<emphasis>ibm,memory-utilization_instrumentation-v#</emphasis>
</para>
</entry>
<entry>
<para>0x01-0x03</para>
</entry>
</row>
<row>
<entry morerows="13">
<para>1 Partition Migration / Hibernation</para>
</entry>
<entry>
@ -3202,6 +3212,16 @@
<para>0x01-0x03</para>
</entry>
</row>
<row>
<entry>
<para>
<emphasis>ibm,memory-utilization_instrumentation-v#</emphasis>
</para>
</entry>
<entry>
<para>0x01-0x03</para>
</entry>
</row>
<row>
<entry>
<para>2 Activate Firmware</para>
@ -3225,7 +3245,7 @@
</section>
<section xml:id="dbdoclet.50569332_40069">
<title>TAS Call <emphasis>ibm,update-properties</emphasis></title>
<title><emphasis>ibm,update-properties</emphasis> RTAS Call</title>
<para>This RTAS call is used to report updates to the properties changed
due to a massive platform reconfiguration such as when the partition is
@ -3252,7 +3272,6 @@
<para>A single updated property value string may exceed the capacity of a
single 4 K work area. In that case, the updated property value descriptor
for the property appears in the work area of multiple sequential calls to
<emphasis>ibm,update-properties</emphasis> RTAS. When the updated property
value descriptor contains the final data for the property value, the
property string length field of the updated property value descriptor is
@ -3414,7 +3433,7 @@
<row>
<entry>
<para>
<emphasis>phandle</emphasis> of updated node containing updated
<emphasis role="bold">phandle</emphasis> of updated node containing updated
properties to be reported (4 bytes)</para>
</entry>
</row>
@ -3423,7 +3442,7 @@
<row>
<entry>
<para>0x00000000 (Indicates Initial call for specified
<emphasis>phandle</emphasis>)</para>
<emphasis role="bold">phandle</emphasis>)</para>
</entry>
</row>
<row>
@ -3474,7 +3493,7 @@
<row>
<entry>
<para>
<emphasis>phandle</emphasis> of updated node containing updated
<emphasis role="bold">phandle</emphasis> of updated node containing updated
properties to be reported.</para>
</entry>
<entry>
@ -3600,7 +3619,7 @@
<row>
<entry>
<para>
<emphasis>phandle</emphasis> of updated node containing updated
<emphasis role="bold">phandle</emphasis> of updated node containing updated
properties to be reported (4 Bytes)</para>
</entry>
</row>
@ -3670,7 +3689,7 @@
</thead>
<tbody>
<row>
<entry morerows="5">
<entry morerows="6">
<para>All negative values: Resource Reassignment events as from
event-scan RTAS</para>
</entry>
@ -3678,7 +3697,7 @@
<para>/memory</para>
</entry>
<entry>
<para>&#8220;ibm,associativity&#8221;</para>
<para><emphasis role="bold"><literal>&#8220;ibm,associativity&#8221;</literal></emphasis></para>
</entry>
</row>
<row>
@ -3686,7 +3705,8 @@
<para>ibm,dynamic-reconfiguration-memory</para>
</entry>
<entry>
<para>&#8220;ibm,dynamic-memory&#8221;</para>
<para><emphasis role="bold"><literal>&#8220;ibm,dynamic-memory&#8221;</literal></emphasis></para>
<para><emphasis role="bold"><literal>&#8220;ibm,dynamic-memory-v2&#8221;</literal></emphasis></para>
</entry>
</row>
<row>
@ -3700,7 +3720,7 @@
<row>
<entry>
<para>
<emphasis>ibm,random-v#</emphasis>
<emphasis role="bold"><literal>ibm,random-v#</literal></emphasis>
</para>
</entry>
<entry>
@ -3710,7 +3730,7 @@
<row>
<entry>
<para>
<emphasis>ibm,compression-v#</emphasis>
<emphasis role="bold"><literal>ibm,compression-v#</literal></emphasis>
</para>
</entry>
<entry>
@ -3720,7 +3740,17 @@
<row>
<entry>
<para>
<emphasis>ibm,encryption-v#</emphasis>
<emphasis role="bold"><literal>ibm,encryption-v#</literal></emphasis>
</para>
</entry>
<entry>
<para>&lt;all&gt;</para>
</entry>
</row>
<row>
<entry>
<para>
<emphasis role="bold"><literal>ibm,memory-utilization_instrumentation-v#</literal></emphasis>
</para>
</entry>
<entry>
@ -3728,12 +3758,12 @@
</entry>
</row>
<row>
<entry morerows="29">
<entry morerows="31">
<para>1 Partition Migration / Hibernation</para>
</entry>
<entry morerows="17">
<entry morerows="18">
<para>
<emphasis>root</emphasis>
<emphasis role="bold"><literal>root</literal></emphasis>
</para>
</entry>
<entry>
@ -3792,6 +3822,13 @@
</para>
</entry>
</row>
<row>
<entry>
<para>
<emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis>
</para>
</entry>
</row>
<row>
<entry>
<para>
@ -3867,7 +3904,7 @@
<row>
<entry>
<para>
<emphasis>openprom</emphasis>
<emphasis role="bold"><literal>openprom</literal></emphasis>
</para>
</entry>
<entry>
@ -3879,7 +3916,7 @@
<row>
<entry morerows="8">
<para>
<emphasis>rtas</emphasis>
<emphasis role="bold"><literal>rtas</literal></emphasis>
</para>
</entry>
<entry>
@ -3950,9 +3987,9 @@
</entry>
</row>
<row>
<entry>
<entry morerows="1">
<para>
<emphasis>vdevice</emphasis>
<emphasis role="bold"><literal>vdevice</literal></emphasis>
</para>
</entry>
<entry>
@ -3961,10 +3998,17 @@
</para>
</entry>
</row>
<row>
<entry>
<para>
<emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis>
</para>
</entry>
</row>
<row>
<entry>
<para>children of the
<emphasis>vdevice</emphasis> node</para>
<emphasis role="bold"><literal>vdevice</literal></emphasis> node</para>
</entry>
<entry>
<para>
@ -3979,7 +4023,7 @@
</entry>
<entry morerows="20">
<para>
<emphasis>cpu</emphasis>
<emphasis role="bold"><literal>cpu</literal></emphasis>
</para>
</entry>
<entry>
@ -4124,14 +4168,14 @@
<row>
<entry>
<para>
<emphasis>"ibm,sub-processors"</emphasis>
<emphasis role="bold"><literal>&#8220;ibm,sub-processors&#8221;</literal></emphasis>
</para>
</entry>
</row>
<row>
<entry morerows="4">
<para>
<emphasis>cache</emphasis>
<emphasis role="bold"><literal>cache</literal></emphasis>
</para>
</entry>
<entry>
@ -4164,14 +4208,14 @@
<row>
<entry>
<para>
<emphasis>l2-cache</emphasis>
<emphasis role="bold"><literal>l2-cache</literal></emphasis>
</para>
</entry>
</row>
<row>
<entry>
<para>
<emphasis>options</emphasis>
<emphasis role="bold"><literal>options</literal></emphasis>
</para>
</entry>
<entry>
@ -4183,7 +4227,7 @@
<row>
<entry>
<para>
<emphasis>memory</emphasis>
<emphasis role="bold"><literal>memory</literal></emphasis>
</para>
</entry>
<entry>
@ -4195,28 +4239,29 @@
<row>
<entry morerows="2">
<para>
<emphasis>ibm,dynamic-reconfiguration-memory</emphasis>
<emphasis role="bold"><literal>ibm,dynamic-reconfiguration-memory</literal></emphasis>
</para>
</entry>
<entry>
<para>&#8220;ibm,associativity-lookup-arrays&#8221;</para>
<para><emphasis role="bold"><literal>&#8220;ibm,associativity-lookup-arrays&#8221;</literal></emphasis></para>
</entry>
</row>
<row>
<entry>
<para>&#8220;ibm,dynamic-memory&#8221;</para>
<para><emphasis role="bold"><literal>&#8220;ibm,dynamic-memory&#8221;</literal></emphasis></para>
<para><emphasis role="bold"><literal>&#8220;ibm,dynamic-memory-v2&#8221;</literal></emphasis></para>
<para>only the associativity list index fields</para>
</entry>
</row>
<row>
<entry>
<para>&#8220;ibm,memory-preservation-time&#8221;</para>
<para><emphasis role="bold"><literal>&#8220;ibm,memory-preservation-time&#8221;</literal></emphasis></para>
</entry>
</row>
<row>
<entry>
<para>
<emphasis>/chosen</emphasis>
<emphasis role="bold"><literal>/chosen</literal></emphasis>
</para>
</entry>
<entry>
@ -4227,13 +4272,13 @@
</entry>
</row>
<row>
<entry morerows="2">
<entry morerows="3">
<para>1 Partition Migration / Hibernation</para>
<para>&#160;</para>
</entry>
<entry>
<para>
<emphasis>ibm,random-v#</emphasis>
<emphasis role="bold"><literal>ibm,random-v#</literal></emphasis>
</para>
</entry>
<entry>
@ -4243,7 +4288,7 @@
<row>
<entry>
<para>
<emphasis>ibm,compression-v#</emphasis>
<emphasis role="bold"><literal>ibm,compression-v#</literal></emphasis>
</para>
</entry>
<entry>
@ -4253,7 +4298,17 @@
<row>
<entry>
<para>
<emphasis>ibm,encryption-v#</emphasis>
<emphasis role="bold"><literal>ibm,encryption-v#</literal></emphasis>
</para>
</entry>
<entry>
<para>&lt;all&gt;</para>
</entry>
</row>
<row>
<entry>
<para>
<emphasis role="bold"><literal>ibm,memory-utilization_instrumentation-v#</literal></emphasis>
</para>
</entry>
<entry>
@ -4266,7 +4321,7 @@
</entry>
<entry>
<para>
<emphasis>rtas</emphasis>
<emphasis role="bold"><literal>rtas</literal></emphasis>
</para>
</entry>
<entry>
@ -4306,7 +4361,7 @@
</section>
<section xml:id="dbdoclet.50569332_67111">
<title>RTAS call <emphasis>ibm,configure-kernel-dump</emphasis></title>
<title><emphasis>ibm,configure-kernel-dump</emphasis> RTAS Call</title>
<para>This RTAS call is used to register and unregister with the platform
a data structure describing kernel dump information. This dump
@ -5088,6 +5143,11 @@
to make a successful subsequent call to
<emphasis>ibm,create-dma-window</emphasis>.</para>
<para>If the <emphasis>ibm,query-pe-dma-window</emphasis> RTAS call is made with Number Outputs
equal to 6, and the <emphasis role="bold"><literal>&#8220;ibm,ddw-extensions&#8221;</literal></emphasis>
property does not include list index of 3,
then the call will return a Status of -3 (Invalid Parameter).</para>
<variablelist>
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="dbdoclet.50569332_99826"
@ -5156,7 +5216,9 @@
</para>
</entry>
<entry>
<para>5</para>
<para>5 or 6. The value 6 may be used when the ibm,ddw-extensions property
in the PHB node specified by this call indicates support for a 64-bit value of
PE TCEs. See <xref linkend="dbdoclet.50569332_25585" />.</para>
</entry>
</row>
<row>
@ -5195,7 +5257,7 @@
</entry>
</row>
<row>
<entry morerows="4">
<entry morerows="5">
<para>Out</para>
</entry>
<entry>
@ -5227,11 +5289,20 @@
</row>
<row>
<entry>
<para>PE TCEs</para>
<para>PE TCEs hi</para>
</entry>
<entry>
<para>Represents the most-significant 32-bits of the largest contiguous
block of TCEs allocated specifically for (that is, are reserved for) this PE.</para>
</entry>
</row>
<row>
<entry>
<para>Largest contiguous block of TCEs allocated specifically
for (that is, are reserved for) this PE. See also Requirement
<para>PE TCEs lo</para>
</entry>
<entry>
<para>Represents the least-significant 32-bits of the largest contiguous block
of TCEs allocated specifically for (that is, are reserved for) this PE. See also Requirement
<xref linkend="dbdoclet.50569332_91197" />.</para>
</entry>
</row>
@ -5751,6 +5822,18 @@
<emphasis>bm,reset-pe-dma-windows</emphasis> RTAS Call</para>
</entry>
</row>
<row>
<entry>
<para>2.7</para>
</entry>
<entry>
<para>3</para>
</entry>
<entry>
<para>Value of 1 indicates the OS may invoke RTAS <emphasis>ibm,query-pe-dma-window</emphasis>
with Number Outputs equal to 6. Other values are reserved.</para>
</entry>
</row>
</tbody>
</tgroup>
</table>

101
Virtualization/bk_main.xml
Unescape Escape View File

@ -42,7 +42,7 @@
<holder>OpenPOWER Foundation</holder>
</copyright>
<!-- TODO: Set the correct document releaseinfo -->
<releaseinfo>Revision 2.0_pre1</releaseinfo>
<releaseinfo>Revision 2.0_pre2</releaseinfo>
<productname>OpenPOWER</productname>
<pubdate/>

@ -71,6 +71,105 @@

<revhistory>
<!-- TODO: Update as new revisions created -->
<revision>
<date>2017-10-11</date>
<revdescription>
<itemizedlist spacing="compact">
<listitem>
<para>Revision 2.0_pre2 - Updates to include latest PAPR ACRs (2.8) as follows:</para>
<itemizedlist spacing="compact">
<listitem>
<para>ISA 2.07 privileged doorbell extensions (9/16/2012)</para>
</listitem>
<listitem>
<para>POWER ISA Name Change Category Vector.XOR to Vector.CRYPTO (11/4/2012)</para>
</listitem>
<listitem>
<para>Enable Multiple Redirected RDMA mappings per page (3/5/2013)</para>
</listitem>
<listitem>
<para>Add Block Invalidate Option (3/5/2013)</para>
</listitem>
<listitem>
<para>Implementation Dependent Optimizations (3/13/2013)</para>
</listitem>
<listitem>
<para>System Firmware Service Entitlement Date (Warranty Date) Check (4/3/2013)</para>
</listitem>
<listitem>
<para>New Function for ibm,change-msi to specify 32 bit MSI (5/14/2013)</para>
</listitem>
<listitem>
<para>Remove Client-Architecture-Support bit for UUID option (4/16/2013)</para>
</listitem>
<listitem>
<para>AddClient Architecture Support bit for RTAS ibm,change-msi (5/28/2013)</para>
</listitem>
<listitem>
<para>Add VNIC Server (5/24/2014)</para>
</listitem>
<listitem>
<para>VPA changes for P8 (EBB) (5/24/2013)</para>
</listitem>
<listitem>
<para>Add an hcall to clean up the entire MMU hashtable (11/20/2013)</para>
</listitem>
<listitem>
<para>Add LPCR[ILE] support to H_SET_MODE (5/31/2013)</para>
</listitem>
<listitem>
<para>New Root Node Properties (1/12/2016)</para>
</listitem>
<listitem>
<para>Extended Firmware Assisted Dump for P8 Registers (1/24/2014)</para>
</listitem>
<listitem>
<para>Sufficient H_COP_OP output buffer (6/21/2014)</para>
</listitem>
<listitem>
<para>Extend H_SEND_LOGICAL_LAN for large send packets (6/29/2014)</para>
</listitem>
<listitem>
<para>Extend H_GET_MPP_X reporting coalesced pages (8/24/2014)</para>
</listitem>
<listitem>
<para>Update ibm,pcie-link-speed-stats property to support PCIe 3.0 link speeds (6/12/2015)</para>
</listitem>
<listitem>
<para>Extend ibm,get-system-parameters RTAS to report Energy Management Tuning Parameters (3/18/2015)</para>
</listitem>
<listitem>
<para>Additional System Parameters related to mgmt of FW Service Entitlement Warranty period (6/22/2015)</para>
</listitem>
<listitem>
<para>Additional System Parameter to read LPAR Name string (10/7/2015)</para>
</listitem>
<listitem>
<para>Redesign of properties for DRC information and dynamic memory (7/23/2015)</para>
</listitem>
<listitem>
<para>Add additional logical loction code sections (3/4/2016)</para>
</listitem>
<listitem>
<para>Add ibm,vnic-client-mac to support vNIC failover (2/29/2016)</para>
</listitem>
<listitem>
<para>hcall for registering the process table (3/21/2016)</para>
</listitem>
<listitem>
<para>New device tree property for UUID (3/21/2016)</para>
</listitem>
<listitem>
<para>Changes for Hotplug RTAS Events (10/24/2016)</para>
</listitem>
<listitem>
<para>Support 64-bit PE TCEs in ibm,query-pe-dma-window (7/14/2016)</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</revdescription>
</revision>
<revision>
<date>2017-05-18</date>
<revdescription>

169
Virtualization/ch_dynamic_reconfig.xml
Unescape Escape View File

@ -1122,14 +1122,13 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
</section>
<section xml:id="dbdoclet.50569342_17435">
<title>Property
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis></title>
<title><emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> Property</title>
<para>This property is added for the DR option to specify for each DR
connector an index to be passed between the OS and RTAS to identify the
DR connector to be operated upon. This property is in the parent node of
the DR connector to which the property applies. See
<xref linkend="LoPAR.DeviceTree" /> for the definition of this
property.</para>
property. See <xref linkend="sec_ibmdrcinfo_property" /> for additional information.</para>

<variablelist>
<varlistentry>
@ -1146,8 +1145,7 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
</section>
<section xml:id="dbdoclet.50569342_31379">
<title>Property
<emphasis role="bold"><literal>&#8220;ibm,my-drc-index&#8221;</literal></emphasis></title>
<title><emphasis role="bold"><literal>&#8220;ibm,my-drc-index&#8221;</literal></emphasis> Property</title>
<para>This property is added for the DR option to specify for each node
which has a DR connector between it and its parent, the value of the
entry in the
@ -1171,12 +1169,11 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
</section>
<section xml:id="dbdoclet.50569342_22748">
<title>Property
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis></title>
<title><emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis> Property</title>
<para>This property is added for the DR option to specify for each DR
connector a user-readable location code for the connector. See
<xref linkend="LoPAR.DeviceTree" /> for the definition of this
property.</para>
property. See <xref linkend="sec_ibmdrcinfo_property" /> for additional information.</para>

<variablelist>
<varlistentry>
@ -1287,7 +1284,7 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<para>This property is added for the DR option to specify for each DR
connector the power domain in which the connector resides. See
<xref linkend="LoPAR.DeviceTree" /> for the definition of this
property.</para>
property. See <xref linkend="sec_ibmdrcinfo_property" /> for additional information.</para>

<variablelist>
<varlistentry xml:id="dbdoclet.50569342_45966">
@ -1323,12 +1320,11 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
</section>
<section xml:id="dbdoclet.50569342_27002">
<title>Property
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis></title>
<title><emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis> Property</title>
<para>This property is added for the DR option to specify for each DR
connector a user-readable connector type for the connector. See
<xref linkend="LoPAR.DeviceTree" /> for the definition of this
property.</para>
property. See <xref linkend="sec_ibmdrcinfo_property" /> for additional information.</para>
<para>
<emphasis role="bold">Architecture Note:</emphasis> The logical connectors (CPU, MEM
etc.) represent DR boundaries that may not have physical DR connectors
@ -1354,8 +1350,7 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
</section>
<section xml:id="dbdoclet.50569342_79298">
<title>Property
<emphasis role="bold"><literal>&#8220;ibm,phandle&#8221;</literal></emphasis></title>
<title><emphasis role="bold"><literal>&#8220;ibm,phandle&#8221;</literal></emphasis> Property</title>
<para>This property is added for the DR option to specify the phandle for
each OF device tree node returned by ibm,configure-connector. See
<xref linkend="LoPAR.DeviceTree" /> for the definition of this
@ -1377,6 +1372,57 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
</varlistentry>
</variablelist>
</section>
<section xml:id="sec_ibmdrcinfo_property">
<title><emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis> Property</title>
<para>This property is added to consolidate the information provided by the
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis> and
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis> properties.
When present, it replaces those properties.</para>
<variablelist>
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="sec_ibmdrcinfo_property"
xrefstyle="select: labelnumber nopage"/>-1.</emphasis></term>
<listitem>
<para>For each OF device tree node which supports DR operations on its children, OF must
provide an <emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis>
property for that node.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="sec_ibmdrcinfo_property"
xrefstyle="select: labelnumber nopage"/>-2.</emphasis></term>
<listitem>
<para>The <emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis> property shall only
be present if the Operating System indicates support for this new property definition,
otherwise, the <emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis> and
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis> will be present.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><emphasis role="bold">R1-<xref linkend="sec_ibmdrcinfo_property"
xrefstyle="select: labelnumber nopage"/>-3.</emphasis></term>
<listitem>
<para>Following live partition migration the Operating System must be prepared to support
either the <emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis> property or the
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis> and
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis>
set of properties. The property or properties presented will based on the capability of the target partition.</para>
</listitem>
</varlistentry>
</variablelist>
</section>
</section>

<section xml:id="dbdoclet.50569342_40601">
@ -1416,7 +1462,8 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<para>This RTAS call is used in DR to power up or power down a DR
connector, if necessary (that is, if there is a non-zero power domain
listed for the DR connector in the
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis> property). The
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> or
<emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis> property). The
input is the power domain and the output is the power level that is
actually to be set for that domain; for purposes of DR, only two of the
current power levels are of interest: &#8220;full on&#8221; and
@ -1769,7 +1816,8 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<emphasis>get-sensor-state</emphasis> RTAS call for the sensors in
<xref linkend="dbdoclet.50569342_92542" /> must be the index for the
connector, as passed in the
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> property.</para>
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> or
<emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis> property.</para>
<para>
<emphasis role="bold">Hardware and Software Implementation Note:</emphasis> The status
introduced in Requirement
@ -1997,7 +2045,8 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<emphasis>set-indicator</emphasis> RTAS call for the indicators in
<xref linkend="dbdoclet.50569342_34333" /> must be the index for the
connector, as passed in the
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> property.</para>
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> or
<emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis> property.</para>
</listitem>
</varlistentry>
@ -2269,7 +2318,8 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
</entry>
<entry>
<para>entry from the
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> property for
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> or
<emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis> property for
the connector to configure</para>
</entry>
</row>
@ -2325,10 +2375,12 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
which returns &#8220;configuration complete&#8221; status. A subsequent
sequence of calls to
<emphasis>ibm,configure-connector</emphasis> with the same entry from the
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> property will restart
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> or
<emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis> property will restart
the configuration of devices which were not completely configured.</para>
<para>If the index from
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> refers to a connector
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> or
<emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis> refers to a connector
that would return an &#8220;DR entity unusable&#8221; status (2) to the
<emphasis>get-sensor</emphasis> RTAS call with dr-entity-sense token, the
<emphasis>ibm,configure-connector</emphasis> RTAS call for that index
@ -3670,6 +3722,17 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<xref linkend="LoPAR.DeviceTree" />.</para>
</entry>
</row>
<row>
<entry>
<para>
<emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis>
</para>
</entry>
<entry>
<para>As defined in
<xref linkend="sec_ibmdrcinfo_property" />.</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
@ -3691,13 +3754,14 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<listitem>
<para><emphasis role="bold">For the LRDR option:</emphasis> The
<emphasis role="bold"><literal>/cpus</literal></emphasis> OF device tree node must include
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis> (of type CPU),
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis>
(of value -1),
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis>, and
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis>
properties with entries for each potentially
supported dynamically reconfigurable processor.</para>
either the <emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis>
property or the following four properties:
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis> and
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis>.
The drc-type must be type CPU, and the drc-power-domain must have the value -1. The
property or properties must contain entries for each potentially supported dynamically reconfigurable processor.</para>
</listitem>
</varlistentry>
@ -3707,14 +3771,15 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<listitem>
<para><emphasis role="bold">For the LRDR option:</emphasis> The root node of the OF device
tree must include
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis>
(of type MEM),
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis>
(of value -1),
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis>, and
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis>
properties with entries for each potentially
supported dynamically reconfigurable memory region.</para>
ither the <emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis>
property or the following four properties:
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis> and
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis>.
The drc-type must be type MEM and the drc-power-domain must have the value -1.
The property or properties must contain entries for each potentially supported dynamically
reconfigurable memory region.</para>
</listitem>
</varlistentry>
@ -3735,14 +3800,15 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<listitem>
<para><emphasis role="bold">For the LRDR option:</emphasis> The root node of the OF device
tree must include
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis>
(of type PHB),
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis>
(of value -1),
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis>, and
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis>
properties with entries for each potentially
supported dynamically reconfigurable PHB.</para>
either the <emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis>
property or the following four properties:
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis> and
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis>.
The drc-type must be type PHB, and the drc-power-domain must have the value -1.
The property or properties must contain entries for each potentially supported dynamically
reconfigurable PHB.</para>
</listitem>
</varlistentry>
@ -3753,14 +3819,15 @@ xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<para><emphasis role="bold">For the LRDR option:</emphasis> The
<emphasis role="bold"><literal>/pci</literal></emphasis> OF device tree node representing a PHB must
include
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis>
(of type SLOT),
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis>
(of value -1),
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis>, and
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis>
properties with entries for each potentially
supported dynamically reconfigurable PCI SLOT.</para>
either the <emphasis role="bold"><literal>&#8220;ibm,drc-info&#8221;</literal></emphasis>
property or the following four properties:
<emphasis role="bold"><literal>&#8220;ibm,drc-indexes&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-names&#8221;</literal></emphasis>,
<emphasis role="bold"><literal>&#8220;ibm,drc-types&#8221;</literal></emphasis> and
<emphasis role="bold"><literal>&#8220;ibm,drc-power-domains&#8221;</literal></emphasis>.
The drc-type must be type SLOT, and the drc-power-domain must have the value -1.
The property or properties must contain entries for each potentially supported dynamically
reconfigurable PCI SLOT.</para>
</listitem>
</varlistentry>

15405
Virtualization/ch_lpar_option.xml
View File

File diff suppressed because it is too large Load Diff

630
Virtualization/ch_virtual_io.xml
View File

File diff suppressed because it is too large Load Diff
Write Preview
Loading…
Cancel
Save