VirtualBox

source: vbox/trunk/src/VBox/Devices/EFI/Firmware/MdePkg/Include/Protocol/RestEx.h@ 105681

最後變更 在這個檔案從105681是 105670,由 vboxsync 提交於 7 月 前

Devices/EFI/FirmwareNew: Merge edk2-stable-202405 and make it build on aarch64, bugref:4643

  • 屬性 svn:eol-style 設為 native
檔案大小: 19.3 KB
 
1/** @file
2 This file defines the EFI REST EX Protocol interface. It is
3 split into the following two main sections.
4
5 - REST EX Service Binding Protocol
6 - REST EX Protocol
7
8 Copyright (c) 2019, Intel Corporation. All rights reserved.<BR>
9 (C) Copyright 2020 Hewlett Packard Enterprise Development LP<BR>
10
11 SPDX-License-Identifier: BSD-2-Clause-Patent
12
13 @par Revision Reference:
14 This Protocol is introduced in UEFI Specification 2.8
15
16**/
17
18#ifndef EFI_REST_EX_PROTOCOL_H_
19#define EFI_REST_EX_PROTOCOL_H_
20
21#include <Protocol/Http.h>
22
23//
24// GUID definitions
25//
26#define EFI_REST_EX_SERVICE_BINDING_PROTOCOL_GUID \
27 { \
28 0x456bbe01, 0x99d0, 0x45ea, {0xbb, 0x5f, 0x16, 0xd8, 0x4b, 0xed, 0xc5, 0x59 } \
29 }
30
31#define EFI_REST_EX_PROTOCOL_GUID \
32 { \
33 0x55648b91, 0xe7d, 0x40a3, {0xa9, 0xb3, 0xa8, 0x15, 0xd7, 0xea, 0xdf, 0x97 } \
34 }
35
36typedef struct _EFI_REST_EX_PROTOCOL EFI_REST_EX_PROTOCOL;
37
38// *******************************************************
39// EFI_REST_EX_SERVICE_INFO_VER
40// *******************************************************
41typedef struct {
42 UINT8 Major;
43 UINT8 Minor;
44} EFI_REST_EX_SERVICE_INFO_VER;
45
46// *******************************************************
47// EFI_REST_EX_SERVICE_INFO_HEADER
48// *******************************************************
49typedef struct {
50 UINT32 Length;
51 EFI_REST_EX_SERVICE_INFO_VER RestServiceInfoVer;
52} EFI_REST_EX_SERVICE_INFO_HEADER;
53
54// *******************************************************
55// EFI_REST_EX_SERVICE_TYPE
56// *******************************************************
57typedef enum {
58 EfiRestExServiceUnspecific = 1,
59 EfiRestExServiceRedfish,
60 EfiRestExServiceOdata,
61 EfiRestExServiceVendorSpecific = 0xff,
62 EfiRestExServiceTypeMax
63} EFI_REST_EX_SERVICE_TYPE;
64
65// *******************************************************
66// EFI_REST_EX_SERVICE_ACCESS_MODE
67// *******************************************************
68typedef enum {
69 EfiRestExServiceInBandAccess = 1,
70 EfiRestExServiceOutOfBandAccess = 2,
71 EfiRestExServiceModeMax
72} EFI_REST_EX_SERVICE_ACCESS_MODE;
73
74// *******************************************************
75// EFI_REST_EX_CONFIG_TYPE
76// *******************************************************
77typedef enum {
78 EfiRestExConfigHttp,
79 EfiRestExConfigUnspecific,
80 EfiRestExConfigTypeMax
81} EFI_REST_EX_CONFIG_TYPE;
82
83// *******************************************************
84// EFI_REST_EX_SERVICE_INFO v1.0
85// *******************************************************
86typedef struct {
87 EFI_REST_EX_SERVICE_INFO_HEADER EfiRestExServiceInfoHeader;
88 EFI_REST_EX_SERVICE_TYPE RestServiceType;
89 EFI_REST_EX_SERVICE_ACCESS_MODE RestServiceAccessMode;
90 EFI_GUID VendorRestServiceName;
91 UINT32 VendorSpecificDataLength;
92 UINT8 *VendorSpecifcData;
93 EFI_REST_EX_CONFIG_TYPE RestExConfigType;
94 UINT8 RestExConfigDataLength;
95} EFI_REST_EX_SERVICE_INFO_V_1_0;
96
97// *******************************************************
98// EFI_REST_EX_SERVICE_INFO
99// *******************************************************
100typedef union {
101 EFI_REST_EX_SERVICE_INFO_HEADER EfiRestExServiceInfoHeader;
102 EFI_REST_EX_SERVICE_INFO_V_1_0 EfiRestExServiceInfoV10;
103} EFI_REST_EX_SERVICE_INFO;
104
105// *******************************************************
106// EFI_REST_EX_HTTP_CONFIG_DATA
107// *******************************************************
108typedef struct {
109 EFI_HTTP_CONFIG_DATA HttpConfigData;
110 UINT32 SendReceiveTimeout;
111} EFI_REST_EX_HTTP_CONFIG_DATA;
112
113// *******************************************************
114// EFI_REST_EX_CONFIG_DATA
115// *******************************************************
116typedef UINT8 *EFI_REST_EX_CONFIG_DATA;
117
118// *******************************************************
119// EFI_REST_EX_TOKEN
120// *******************************************************
121typedef struct {
122 EFI_EVENT Event;
123 EFI_STATUS Status;
124 EFI_HTTP_MESSAGE *ResponseMessage;
125} EFI_REST_EX_TOKEN;
126
127/**
128 Provides a simple HTTP-like interface to send and receive resources from a REST service.
129
130 The SendReceive() function sends an HTTP request to this REST service, and returns a
131 response when the data is retrieved from the service. RequestMessage contains the HTTP
132 request to the REST resource identified by RequestMessage.Request.Url. The
133 ResponseMessage is the returned HTTP response for that request, including any HTTP
134 status. It's caller's responsibility to free this ResponseMessage using FreePool().
135 RestConfigFreeHttpMessage() in RedfishLib is an example to release ResponseMessage structure.
136
137 @param[in] This Pointer to EFI_REST_EX_PROTOCOL instance for a particular
138 REST service.
139 @param[in] RequestMessage Pointer to the HTTP request data for this resource
140 @param[out] ResponseMessage Pointer to the HTTP response data obtained for this requested.
141
142 @retval EFI_SUCCESS operation succeeded.
143 @retval EFI_INVALID_PARAMETER This, RequestMessage, or ResponseMessage are NULL.
144 @retval EFI_DEVICE_ERROR An unexpected system or network error occurred.
145
146**/
147typedef
148EFI_STATUS
149(EFIAPI *EFI_REST_SEND_RECEIVE)(
150 IN EFI_REST_EX_PROTOCOL *This,
151 IN EFI_HTTP_MESSAGE *RequestMessage,
152 OUT EFI_HTTP_MESSAGE *ResponseMessage
153 );
154
155/**
156 Obtain the current time from this REST service instance.
157
158 The GetServiceTime() function is an optional interface to obtain the current time from
159 this REST service instance. If this REST service does not support to retrieve the time,
160 this function returns EFI_UNSUPPORTED. This function must returns EFI_UNSUPPORTED if
161 EFI_REST_EX_SERVICE_TYPE returned in EFI_REST_EX_SERVICE_INFO from GetService() is
162 EFI_REST_EX_SERVICE_UNSPECIFIC.
163
164 @param[in] This Pointer to EFI_REST_EX_PROTOCOL instance for a particular
165 REST service.
166 @param[out] Time A pointer to storage to receive a snapshot of the current time of
167 the REST service.
168
169 @retval EFI_SUCCESS operation succeeded.
170 @retval EFI_INVALID_PARAMETER This or Time are NULL.
171 @retval EFI_UNSUPPORTED The RESTful service does not support returning the time.
172 @retval EFI_DEVICE_ERROR An unexpected system or network error occurred.
173 @retval EFI_NOT_READY The configuration of this instance is not set yet. Configure() must
174 be executed and returns successfully prior to invoke this function.
175
176**/
177typedef
178EFI_STATUS
179(EFIAPI *EFI_REST_GET_TIME)(
180 IN EFI_REST_EX_PROTOCOL *This,
181 OUT EFI_TIME *Time
182 );
183
184/**
185 This function returns the information of REST service provided by this EFI REST EX driver instance.
186
187 The information such as the type of REST service and the access mode of REST EX driver instance
188 (In-band or Out-of-band) are described in EFI_REST_EX_SERVICE_INFO structure. For the vendor-specific
189 REST service, vendor-specific REST service information is returned in VendorSpecifcData.
190 REST EX driver designer is well know what REST service this REST EX driver instance intends to
191 communicate with. The designer also well know this driver instance is used to talk to BMC through
192 specific platform mechanism or talk to REST server through UEFI HTTP protocol. REST EX driver is
193 responsible to fill up the correct information in EFI_REST_EX_SERVICE_INFO. EFI_REST_EX_SERVICE_INFO
194 is referred by EFI REST clients to pickup the proper EFI REST EX driver instance to get and set resource.
195 GetService() is a basic and mandatory function which must be able to use even Configure() is not invoked
196 in previously.
197
198 @param[in] This Pointer to EFI_REST_EX_PROTOCOL instance for a particular
199 REST service.
200 @param[out] RestExServiceInfo Pointer to receive a pointer to EFI_REST_EX_SERVICE_INFO structure. The
201 format of EFI_REST_EX_SERVICE_INFO is version controlled for the future
202 extension. The version of EFI_REST_EX_SERVICE_INFO structure is returned
203 in the header within this structure. EFI REST client refers to the correct
204 format of structure according to the version number. The pointer to
205 EFI_REST_EX_SERVICE_INFO is a memory block allocated by EFI REST EX driver
206 instance. That is caller's responsibility to free this memory when this
207 structure is no longer needed. Refer to Related Definitions below for the
208 definitions of EFI_REST_EX_SERVICE_INFO structure.
209
210 @retval EFI_SUCCESS EFI_REST_EX_SERVICE_INFO is returned in RestExServiceInfo. This function
211 is not supported in this REST EX Protocol driver instance.
212 @retval EFI_UNSUPPORTED This function is not supported in this REST EX Protocol driver instance.
213
214**/
215typedef
216EFI_STATUS
217(EFIAPI *EFI_REST_EX_GET_SERVICE)(
218 IN EFI_REST_EX_PROTOCOL *This,
219 OUT EFI_REST_EX_SERVICE_INFO **RestExServiceInfo
220 );
221
222/**
223 This function returns operational configuration of current EFI REST EX child instance.
224
225 This function returns the current configuration of EFI REST EX child instance. The format of
226 operational configuration depends on the implementation of EFI REST EX driver instance. For
227 example, HTTP-aware EFI REST EX driver instance uses EFI HTTP protocol as the undying protocol
228 to communicate with REST service. In this case, the type of configuration is
229 EFI_REST_EX_CONFIG_TYPE_HTTP returned from GetService(). EFI_HTTP_CONFIG_DATA is used as EFI REST
230 EX configuration format and returned to EFI REST client. User has to type cast RestExConfigData
231 to EFI_HTTP_CONFIG_DATA. For those non HTTP-aware REST EX driver instances, the type of configuration
232 is EFI_REST_EX_CONFIG_TYPE_UNSPECIFIC returned from GetService(). In this case, the format of
233 returning data could be non industrial. Instead, the format of configuration data is system/platform
234 specific definition such as BMC mechanism used in EFI REST EX driver instance. EFI REST client and
235 EFI REST EX driver instance have to refer to the specific system /platform spec which is out of UEFI scope.
236
237 @param[in] This This is the EFI_REST_EX_PROTOCOL instance.
238 @param[out] RestExConfigData Pointer to receive a pointer to EFI_REST_EX_CONFIG_DATA.
239 The memory allocated for configuration data should be freed
240 by caller. See Related Definitions for the details.
241
242 @retval EFI_SUCCESS EFI_REST_EX_CONFIG_DATA is returned in successfully.
243 @retval EFI_UNSUPPORTED This function is not supported in this REST EX Protocol driver instance.
244 @retval EFI_NOT_READY The configuration of this instance is not set yet. Configure() must be
245 executed and returns successfully prior to invoke this function.
246
247**/
248typedef
249EFI_STATUS
250(EFIAPI *EFI_REST_EX_GET_MODE_DATA)(
251 IN EFI_REST_EX_PROTOCOL *This,
252 OUT EFI_REST_EX_CONFIG_DATA *RestExConfigData
253 );
254
255/**
256 This function is used to configure EFI REST EX child instance.
257
258 This function is used to configure the setting of underlying protocol of REST EX child
259 instance. The type of configuration is according to the implementation of EFI REST EX
260 driver instance. For example, HTTP-aware EFI REST EX driver instance uses EFI HTTP protocol
261 as the undying protocol to communicate with REST service. The type of configuration is
262 EFI_REST_EX_CONFIG_TYPE_HTTP and RestExConfigData is the same format with EFI_HTTP_CONFIG_DATA.
263 Akin to HTTP configuration, REST EX child instance can be configure to use different HTTP
264 local access point for the data transmission. Multiple REST clients may use different
265 configuration of HTTP to distinguish themselves, such as to use the different TCP port.
266 For those non HTTP-aware REST EX driver instance, the type of configuration is
267 EFI_REST_EX_CONFIG_TYPE_UNSPECIFIC. RestExConfigData refers to the non industrial standard.
268 Instead, the format of configuration data is system/platform specific definition such as BMC.
269 In this case, EFI REST client and EFI REST EX driver instance have to refer to the specific
270 system/platform spec which is out of the UEFI scope. Besides GetService()function, no other
271 EFI REST EX functions can be executed by this instance until Configure()is executed and returns
272 successfully. All other functions must returns EFI_NOT_READY if this instance is not configured
273 yet. Set RestExConfigData to NULL means to put EFI REST EX child instance into the unconfigured
274 state.
275
276 @param[in] This This is the EFI_REST_EX_PROTOCOL instance.
277 @param[in] RestExConfigData Pointer to EFI_REST_EX_CONFIG_DATA. See Related Definitions in
278 GetModeData() protocol interface.
279
280 @retval EFI_SUCCESS EFI_REST_EX_CONFIG_DATA is set in successfully.
281 @retval EFI_DEVICE_ERROR Configuration for this REST EX child instance is failed with the given
282 EFI_REST_EX_CONFIG_DATA.
283 @retval EFI_UNSUPPORTED This function is not supported in this REST EX Protocol driver instance.
284
285**/
286typedef
287EFI_STATUS
288(EFIAPI *EFI_REST_EX_CONFIGURE)(
289 IN EFI_REST_EX_PROTOCOL *This,
290 IN EFI_REST_EX_CONFIG_DATA RestExConfigData
291 );
292
293/**
294 This function sends REST request to REST service and signal caller's event asynchronously when
295 the final response is received by REST EX Protocol driver instance.
296
297 The essential design of this function is to handle asynchronous send/receive implicitly according
298 to REST service asynchronous request mechanism. Caller will get the notification once the response
299 is returned from REST service.
300
301 @param[in] This This is the EFI_REST_EX_PROTOCOL instance.
302 @param[in] RequestMessage This is the HTTP request message sent to REST service. Set RequestMessage
303 to NULL to cancel the previous asynchronous request associated with the
304 corresponding RestExToken. See descriptions for the details.
305 @param[in] RestExToken REST EX token which REST EX Protocol instance uses to notify REST client
306 the status of response of asynchronous REST request. See related definition
307 of EFI_REST_EX_TOKEN.
308 @param[in] TimeOutInMilliSeconds The pointer to the timeout in milliseconds which REST EX Protocol driver
309 instance refers as the duration to drop asynchronous REST request. NULL
310 pointer means no timeout for this REST request. REST EX Protocol driver
311 signals caller's event with EFI_STATUS set to EFI_TIMEOUT in RestExToken
312 if REST EX Protocol can't get the response from REST service within
313 TimeOutInMilliSeconds.
314
315 @retval EFI_SUCCESS Asynchronous REST request is established.
316 @retval EFI_UNSUPPORTED This REST EX Protocol driver instance doesn't support asynchronous request.
317 @retval EFI_TIMEOUT Asynchronous REST request is not established and timeout is expired.
318 @retval EFI_ABORT Previous asynchronous REST request has been canceled.
319 @retval EFI_DEVICE_ERROR Otherwise, returns EFI_DEVICE_ERROR for other errors according to HTTP Status Code.
320 @retval EFI_NOT_READY The configuration of this instance is not set yet. Configure() must be executed
321 and returns successfully prior to invoke this function.
322
323**/
324typedef
325EFI_STATUS
326(EFIAPI *EFI_REST_EX_ASYNC_SEND_RECEIVE)(
327 IN EFI_REST_EX_PROTOCOL *This,
328 IN EFI_HTTP_MESSAGE *RequestMessage OPTIONAL,
329 IN EFI_REST_EX_TOKEN *RestExToken,
330 IN UINTN *TimeOutInMilliSeconds OPTIONAL
331 );
332
333/**
334 This function sends REST request to a REST Event service and signals caller's event
335 token asynchronously when the URI resource change event is received by REST EX
336 Protocol driver instance.
337
338 The essential design of this function is to monitor event implicitly according to
339 REST service event service mechanism. Caller will get the notification if certain
340 resource is changed.
341
342 @param[in] This This is the EFI_REST_EX_PROTOCOL instance.
343 @param[in] RequestMessage This is the HTTP request message sent to REST service. Set RequestMessage
344 to NULL to cancel the previous event service associated with the corresponding
345 RestExToken. See descriptions for the details.
346 @param[in] RestExToken REST EX token which REST EX Protocol driver instance uses to notify REST client
347 the URI resource which monitored by REST client has been changed. See the related
348 definition of EFI_REST_EX_TOKEN in EFI_REST_EX_PROTOCOL.AsyncSendReceive().
349
350 @retval EFI_SUCCESS Asynchronous REST request is established.
351 @retval EFI_UNSUPPORTED This REST EX Protocol driver instance doesn't support asynchronous request.
352 @retval EFI_ABORT Previous asynchronous REST request has been canceled or event subscription has been
353 delete from service.
354 @retval EFI_DEVICE_ERROR Otherwise, returns EFI_DEVICE_ERROR for other errors according to HTTP Status Code.
355 @retval EFI_NOT_READY The configuration of this instance is not set yet. Configure() must be executed
356 and returns successfully prior to invoke this function.
357
358**/
359typedef
360EFI_STATUS
361(EFIAPI *EFI_REST_EX_EVENT_SERVICE)(
362 IN EFI_REST_EX_PROTOCOL *This,
363 IN EFI_HTTP_MESSAGE *RequestMessage OPTIONAL,
364 IN EFI_REST_EX_TOKEN *RestExToken
365 );
366
367///
368/// EFI REST(EX) protocols are designed to support REST communication between EFI REST client
369/// applications/drivers and REST services. EFI REST client tool uses EFI REST(EX) protocols
370/// to send/receive resources to/from REST service to manage systems, configure systems or
371/// manipulate resources on REST service. Due to HTTP protocol is commonly used to communicate
372/// with REST service in practice, EFI REST(EX) protocols adopt HTTP as the message format to
373/// send and receive REST service resource. EFI REST(EX) driver instance abstracts EFI REST
374/// client functionality and provides underlying interface to communicate with REST service.
375/// EFI REST(EX) driver instance knows how to communicate with REST service through certain
376/// interface after the corresponding configuration is initialized.
377///
378struct _EFI_REST_EX_PROTOCOL {
379 EFI_REST_SEND_RECEIVE SendReceive;
380 EFI_REST_GET_TIME GetServiceTime;
381 EFI_REST_EX_GET_SERVICE GetService;
382 EFI_REST_EX_GET_MODE_DATA GetModeData;
383 EFI_REST_EX_CONFIGURE Configure;
384 EFI_REST_EX_ASYNC_SEND_RECEIVE AyncSendReceive;
385 EFI_REST_EX_EVENT_SERVICE EventService;
386};
387
388extern EFI_GUID gEfiRestExServiceBindingProtocolGuid;
389extern EFI_GUID gEfiRestExProtocolGuid;
390
391#endif
注意: 瀏覽 TracBrowser 來幫助您使用儲存庫瀏覽器

© 2025 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette