Lines Matching +full:in +full:- +full:application
1 .. SPDX-License-Identifier: GPL-2.0+
21 https://openpowerfoundation.org/wp-content/uploads/2016/05/LoPAPR_DRAFT_v11_24March2016_cmt1.pdf
27 Console (HMC) - based system management.
31 packaged as an external tower or rack-mounted personal computer. In a
33 processor-based systems.
35 Management Application
36 ----------------------
38 In the management partition, a management application exists which enables
41 State Transfer Application (REST API's).
43 The management application runs on a Linux logical partition on a
44 POWER8 or newer processor-based server that is virtualized by PowerVM.
46 traditionally require an HMC can be implemented in the management
47 application using a combination of HMC to hypervisor interfaces and
51 application component are passed to the hypervisor over a VMC interface,
57 - Logical Partitioning Configuration
58 - Start, and stop actions for individual partitions
59 - Display of partition status
60 - Management of virtual Ethernet
61 - Management of virtual Storage
62 - Basic system management
65 --------------------------------
68 for communicating between the management application and the hypervisor. It
74 Remote Direct Memory Access (RDMA) interfaces. A three-way handshake is
93 -----------
102 from the hypervisor to partition are also reported in this queue.
107 This section provides an example for the management application
114 ----------------------------
119 resources available in both the management partition and the hypervisor.
122 which will be used for management application session initialization.
130 ---------------------------------------->
132 <----------------------------------------
134 ---------------------------------------->
136 <----------------------------------------
138 <---------------------------------------- |
139 ADD BUFFER RESPONSE | - Perform # HMCs Iterations
140 ----------------------------------------> -
143 ------------------
146 connection can be established. The application layer performs an open() to
148 (32 bytes of data) for this session. If the VMC device is in an invalid
164 ---------------------------------------->
166 ---------------------------------------->
168 <---------------------------------------- |
169 Add Buffer Response | - Perform N Iterations
170 ----------------------------------------> -
172 <----------------------------------------
175 ---------------------
177 During normal runtime, the management application and the hypervisor
179 sending data to the hypervisor, the management application performs a
183 are currently available, EBUSY is returned in response to the write(). A
186 put into a VMC buffer and an Signal Message is sent to the VMC driver in
188 and passes the data up to the appropriate management application via a
190 available to read. The management application may use select() to wait for
197 ---------------------------------------->
199 ---------------------------------------->
201 <----------------------------------------
203 <----------------------------------------
206 -------------------
209 the application layer performs a close() against the device. This action
210 results in an Interface Close message flowing to the hypervisor, which
218 ---------------------------------------->
220 <----------------------------------------