|
EFI_STATUS | RedfishCheckHttpReceiveStatus (IN RESTEX_INSTANCE *Instance, IN EFI_STATUS HttpIoReceiveStatus) |
|
EFI_STATUS | ResetHttpTslSession (IN RESTEX_INSTANCE *Instance) |
|
EFI_STATUS | RedfishHttpAddExpectation (IN EFI_REST_EX_PROTOCOL *This, IN EFI_HTTP_MESSAGE *RequestMessage, IN EFI_HTTP_HEADER **PreservedRequestHeaders, IN BOOLEAN *ItsWrite) |
|
EFI_STATUS EFIAPI | RedfishRestExSendReceive (IN EFI_REST_EX_PROTOCOL *This, IN EFI_HTTP_MESSAGE *RequestMessage, OUT EFI_HTTP_MESSAGE *ResponseMessage) |
|
EFI_STATUS EFIAPI | RedfishRestExGetServiceTime (IN EFI_REST_EX_PROTOCOL *This, OUT EFI_TIME *Time) |
|
EFI_STATUS EFIAPI | RedfishRestExGetService (IN EFI_REST_EX_PROTOCOL *This, OUT EFI_REST_EX_SERVICE_INFO **RestExServiceInfo) |
|
EFI_STATUS EFIAPI | RedfishRestExGetModeData (IN EFI_REST_EX_PROTOCOL *This, OUT EFI_REST_EX_CONFIG_DATA *RestExConfigData) |
|
EFI_STATUS EFIAPI | RedfishRestExConfigure (IN EFI_REST_EX_PROTOCOL *This, IN EFI_REST_EX_CONFIG_DATA RestExConfigData) |
|
EFI_STATUS EFIAPI | RedfishRestExAyncSendReceive (IN EFI_REST_EX_PROTOCOL *This, IN EFI_HTTP_MESSAGE *RequestMessage OPTIONAL, IN EFI_REST_EX_TOKEN *RestExToken, IN UINTN *TimeOutInMilliSeconds OPTIONAL) |
|
EFI_STATUS EFIAPI | RedfishRestExEventService (IN EFI_REST_EX_PROTOCOL *This, IN EFI_HTTP_MESSAGE *RequestMessage OPTIONAL, IN EFI_REST_EX_TOKEN *RestExToken) |
|
EFI_STATUS EFIAPI | RestExDestroyChildEntryInHandleBuffer (IN LIST_ENTRY *Entry, IN VOID *Context) |
|
VOID | RestExDestroyInstance (IN RESTEX_INSTANCE *Instance) |
|
EFI_STATUS | RestExCreateInstance (IN RESTEX_SERVICE *Service, OUT RESTEX_INSTANCE **Instance) |
|
VOID | RestExDestroyService (IN RESTEX_SERVICE *RestExSb) |
|
EFI_STATUS | RestExCreateService (IN EFI_HANDLE Controller, IN EFI_HANDLE Image, OUT RESTEX_SERVICE **Service) |
|
EFI_STATUS EFIAPI | RedfishRestExDriverEntryPoint (IN EFI_HANDLE ImageHandle, IN EFI_SYSTEM_TABLE *SystemTable) |
|
EFI_STATUS EFIAPI | RedfishRestExDriverBindingSupported (IN EFI_DRIVER_BINDING_PROTOCOL *This, IN EFI_HANDLE ControllerHandle, IN EFI_DEVICE_PATH_PROTOCOL *RemainingDevicePath OPTIONAL) |
|
EFI_STATUS EFIAPI | RedfishRestExDriverBindingStart (IN EFI_DRIVER_BINDING_PROTOCOL *This, IN EFI_HANDLE ControllerHandle, IN EFI_DEVICE_PATH_PROTOCOL *RemainingDevicePath OPTIONAL) |
|
EFI_STATUS EFIAPI | RedfishRestExDriverBindingStop (IN EFI_DRIVER_BINDING_PROTOCOL *This, IN EFI_HANDLE ControllerHandle, IN UINTN NumberOfChildren, IN EFI_HANDLE *ChildHandleBuffer OPTIONAL) |
|
EFI_STATUS EFIAPI | RedfishRestExServiceBindingCreateChild (IN EFI_SERVICE_BINDING_PROTOCOL *This, IN EFI_HANDLE *ChildHandle) |
|
EFI_STATUS EFIAPI | RedfishRestExServiceBindingDestroyChild (IN EFI_SERVICE_BINDING_PROTOCOL *This, IN EFI_HANDLE ChildHandle) |
|
RedfishRestExDxe support functions definitions.
Copyright (c) 2019, Intel Corporation. All rights reserved.
(C) Copyright 2019-2020 Hewlett Packard Enterprise Development LP
Copyright (c) 2023, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
SPDX-License-Identifier: BSD-2-Clause-Patent
Definition in file RedfishRestExInternal.h.
This function send the HTTP request without body to see if the write to URL is permitted by Redfish service. This function checks if the HTTP request has Content-length in HTTP header. If yes, set HTTP body to NULL and then send to service. Check the HTTP status for the firther actions.
- Parameters
-
[in] | This | Pointer to EFI_REST_EX_PROTOCOL instance for a particular REST service. |
[in] | RequestMessage | Pointer to the HTTP request data for this resource |
[in] | PreservedRequestHeaders | The pointer to save the request headers |
[in] | ItsWrite | This is write method to URL. |
- Return values
-
EFI_INVALID_PARAMETER | Improper given parameters. |
EFI_SUCCESS | This HTTP request is free to send to Redfish service. |
EFI_OUT_OF_RESOURCES | NOt enough memory to process. |
EFI_ACCESS_DENIED | Not allowed to write to this URL. |
Others | Other errors as indicated. |
This function send the HTTP request without body to see if the write to URL is permitted by Redfish service. This function checks if the HTTP request has Content-length in HTTP header. If yes, set HTTP body to NULL and then send to service. Check the HTTP status for the further actions.
- Parameters
-
[in] | This | Pointer to EFI_REST_EX_PROTOCOL instance for a particular REST service. |
[in] | RequestMessage | Pointer to the HTTP request data for this resource |
[in] | PreservedRequestHeaders | The pointer to save the request headers |
[in] | ItsWrite | This is write method to URL. |
- Return values
-
EFI_INVALID_PARAMETER | Improper given parameters. |
EFI_SUCCESS | This HTTP request is free to send to Redfish service. |
EFI_OUT_OF_RESOURCES | NOt enough memory to process. |
EFI_ACCESS_DENIED | Not allowed to write to this URL. |
Others | Other errors as indicated. |
Definition at line 130 of file RedfishRestExImpl.c.
This function is used to configure EFI REST EX child instance.
This function is used to configure the setting of underlying protocol of REST EX child instance. The type of configuration is according to the implementation of EFI REST EX driver instance. For example, HTTP-aware EFI REST EX driver instance uses EFI HTTP protocol as the undying protocol to communicate with REST service. The type of configuration is EFI_REST_EX_CONFIG_TYPE_HTTP and RestExConfigData is the same format with EFI_HTTP_CONFIG_DATA. Akin to HTTP configuration, REST EX child instance can be configure to use different HTTP local access point for the data transmission. Multiple REST clients may use different configuration of HTTP to distinguish themselves, such as to use the different TCP port. For those non HTTP-aware REST EX driver instance, the type of configuration is EFI_REST_EX_CONFIG_TYPE_UNSPECIFIC. RestExConfigData refers to the non industrial standard. Instead, the format of configuration data is system/platform specific definition such as BMC. In this case, EFI REST client and EFI REST EX driver instance have to refer to the specific system/platform spec which is out of the UEFI scope. Besides GetService()function, no other EFI REST EX functions can be executed by this instance until Configure()is executed and returns successfully. All other functions must returns EFI_NOT_READY if this instance is not configured yet. Set RestExConfigData to NULL means to put EFI REST EX child instance into the unconfigured state.
- Parameters
-
[in] | This | This is the EFI_REST_EX_PROTOCOL instance. |
[in] | RestExConfigData | Pointer to EFI_REST_EX_CONFIG_DATA. See Related Definitions in GetModeData() protocol interface. |
- Return values
-
EFI_SUCCESS | EFI_REST_EX_CONFIG_DATA is set in successfully. |
EFI_DEVICE_ERROR | Configuration for this REST EX child instance is failed with the given EFI_REST_EX_CONFIG_DATA. |
EFI_UNSUPPORTED | This function is not supported in this REST EX Protocol driver instance. |
Definition at line 629 of file RedfishRestExProtocol.c.
Starts a device controller or a bus controller.
The Start() function is designed to be invoked from the EFI boot service ConnectController(). As a result, much of the error checking on the parameters to Start() has been moved into this common boot service. It is legal to call Start() from other locations, but the following calling restrictions must be followed, or the system behavior will not be deterministic.
- ControllerHandle must be a valid EFI_HANDLE.
- If RemainingDevicePath is not NULL, then it must be a pointer to a naturally aligned EFI_DEVICE_PATH_PROTOCOL.
- Prior to calling Start(), the Supported() function for the driver specified by This must have been called with the same calling parameters, and Supported() must have returned EFI_SUCCESS.
- Parameters
-
[in] | This | A pointer to the EFI_DRIVER_BINDING_PROTOCOL instance. |
[in] | ControllerHandle | The handle of the controller to start. This handle must support a protocol interface that supplies an I/O abstraction to the driver. |
[in] | RemainingDevicePath | A pointer to the remaining portion of a device path. This parameter is ignored by device drivers, and is optional for bus drivers. For a bus driver, if this parameter is NULL, then handles for all the children of Controller are created by this driver. If this parameter is not NULL and the first Device Path Node is not the End of Device Path Node, then only the handle for the child device specified by the first Device Path Node of RemainingDevicePath is created by this driver. If the first Device Path Node of RemainingDevicePath is the End of Device Path Node, no child handle is created by this driver. |
- Return values
-
EFI_SUCCESS | The device was started. |
EFI_DEVICE_ERROR | The device could not be started due to a device error.Currently not implemented. |
EFI_OUT_OF_RESOURCES | The request could not be completed due to a lack of resources. |
Others | The driver failded to start the device. |
Definition at line 425 of file RedfishRestExDriver.c.
Stops a device controller or a bus controller.
The Stop() function is designed to be invoked from the EFI boot service DisconnectController(). As a result, much of the error checking on the parameters to Stop() has been moved into this common boot service. It is legal to call Stop() from other locations, but the following calling restrictions must be followed, or the system behavior will not be deterministic.
- ControllerHandle must be a valid EFI_HANDLE that was used on a previous call to this same driver's Start() function.
- The first NumberOfChildren handles of ChildHandleBuffer must all be a valid EFI_HANDLE. In addition, all of these handles must have been created in this driver's Start() function, and the Start() function must have called OpenProtocol() on ControllerHandle with an Attribute of EFI_OPEN_PROTOCOL_BY_CHILD_CONTROLLER.
- Parameters
-
[in] | This | A pointer to the EFI_DRIVER_BINDING_PROTOCOL instance. |
[in] | ControllerHandle | A handle to the device being stopped. The handle must support a bus specific I/O protocol for the driver to use to stop the device. |
[in] | NumberOfChildren | The number of child device handles in ChildHandleBuffer. |
[in] | ChildHandleBuffer | An array of child handles to be freed. May be NULL if NumberOfChildren is 0. |
- Return values
-
EFI_SUCCESS | The device was stopped. |
EFI_DEVICE_ERROR | The device could not be stopped due to a device error. |
Definition at line 530 of file RedfishRestExDriver.c.
Tests to see if this driver supports a given controller. If a child device is provided, it further tests to see if this driver supports creating a handle for the specified child device.
This function checks to see if the driver specified by This supports the device specified by ControllerHandle. Drivers will typically use the device path attached to ControllerHandle and/or the services from the bus I/O abstraction attached to ControllerHandle to determine if the driver supports ControllerHandle. This function may be called many times during platform initialization. In order to reduce boot times, the tests performed by this function must be very small, and take as little time as possible to execute. This function must not change the state of any hardware devices, and this function must be aware that the device specified by ControllerHandle may already be managed by the same driver or a different driver. This function must match its calls to AllocatePages() with FreePages(), AllocatePool() with FreePool(), and OpenProtocol() with CloseProtocol(). Because ControllerHandle may have been previously started by the same driver, if a protocol is already in the opened state, then it must not be closed with CloseProtocol(). This is required to guarantee the state of ControllerHandle is not modified by this function.
- Parameters
-
[in] | This | A pointer to the EFI_DRIVER_BINDING_PROTOCOL instance. |
[in] | ControllerHandle | The handle of the controller to test. This handle must support a protocol interface that supplies an I/O abstraction to the driver. |
[in] | RemainingDevicePath | A pointer to the remaining portion of a device path. This parameter is ignored by device drivers, and is optional for bus drivers. For bus drivers, if this parameter is not NULL, then the bus driver must determine if the bus controller specified by ControllerHandle and the child controller specified by RemainingDevicePath are both supported by this bus driver. |
- Return values
-
EFI_SUCCESS | The device specified by ControllerHandle and RemainingDevicePath is supported by the driver specified by This. |
EFI_ALREADY_STARTED | The device specified by ControllerHandle and RemainingDevicePath is already being managed by the driver specified by This. |
EFI_ACCESS_DENIED | The device specified by ControllerHandle and RemainingDevicePath is already being managed by a different driver or an application that requires exclusive access. Currently not implemented. |
EFI_UNSUPPORTED | The device specified by ControllerHandle and RemainingDevicePath is not supported by the driver specified by This. |
Definition at line 354 of file RedfishRestExDriver.c.
This function returns operational configuration of current EFI REST EX child instance.
This function returns the current configuration of EFI REST EX child instance. The format of operational configuration depends on the implementation of EFI REST EX driver instance. For example, HTTP-aware EFI REST EX driver instance uses EFI HTTP protocol as the undying protocol to communicate with REST service. In this case, the type of configuration is EFI_REST_EX_CONFIG_TYPE_HTTP returned from GetService(). EFI_HTTP_CONFIG_DATA is used as EFI REST EX configuration format and returned to EFI REST client. User has to type cast RestExConfigData to EFI_HTTP_CONFIG_DATA. For those non HTTP-aware REST EX driver instances, the type of configuration is EFI_REST_EX_CONFIG_TYPE_UNSPECIFIC returned from GetService(). In this case, the format of returning data could be non industrial. Instead, the format of configuration data is system/platform specific definition such as BMC mechanism used in EFI REST EX driver instance. EFI REST client and EFI REST EX driver instance have to refer to the specific system /platform spec which is out of UEFI scope.
- Parameters
-
[in] | This | This is the EFI_REST_EX_PROTOCOL instance. |
[out] | RestExConfigData | Pointer to receive a pointer to EFI_REST_EX_CONFIG_DATA. The memory allocated for configuration data should be freed by caller. See Related Definitions for the details. |
- Return values
-
EFI_SUCCESS | EFI_REST_EX_CONFIG_DATA is returned in successfully. |
EFI_UNSUPPORTED | This function is not supported in this REST EX Protocol driver instance. |
EFI_NOT_READY | The configuration of this instance is not set yet. Configure() must be executed and returns successfully prior to invoke this function. |
Definition at line 588 of file RedfishRestExProtocol.c.
Provides a simple HTTP-like interface to send and receive resources from a REST service.
The SendReceive() function sends an HTTP request to this REST service, and returns a response when the data is retrieved from the service. RequestMessage contains the HTTP request to the REST resource identified by RequestMessage.Request.Url. The ResponseMessage is the returned HTTP response for that request, including any HTTP status.
- Parameters
-
[in] | This | Pointer to EFI_REST_EX_PROTOCOL instance for a particular REST service. |
[in] | RequestMessage | Pointer to the HTTP request data for this resource |
[out] | ResponseMessage | Pointer to the HTTP response data obtained for this requested. |
- Return values
-
EFI_SUCCESS | operation succeeded. |
EFI_INVALID_PARAMETER | This, RequestMessage, or ResponseMessage are NULL. |
EFI_DEVICE_ERROR | An unexpected system or network error occurred. |
Provides a simple HTTP-like interface to send and receive resources from a REST service.
The SendReceive() function sends an HTTP request to this REST service, and returns a response when the data is retrieved from the service. RequestMessage contains the HTTP request to the REST resource identified by RequestMessage.Request.Url. The ResponseMessage is the returned HTTP response for that request, including any HTTP status. It's caller's responsibility to free this ResponseMessage using FreePool(). RestConfigFreeHttpMessage() in RedfishLib is an example to release ResponseMessage structure.
- Parameters
-
[in] | This | Pointer to EFI_REST_EX_PROTOCOL instance for a particular REST service. |
[in] | RequestMessage | Pointer to the HTTP request data for this resource |
[out] | ResponseMessage | Pointer to the HTTP response data obtained for this requested. |
- Return values
-
EFI_SUCCESS | operation succeeded. |
EFI_INVALID_PARAMETER | This, RequestMessage, or ResponseMessage are NULL. |
EFI_DEVICE_ERROR | An unexpected system or network error occurred. |
EFI_ACCESS_DENIED | HTTP method is not allowed on this URL. |
EFI_BAD_BUFFER_SIZE | The payload is to large to be handled on server side. |
EFI_UNSUPPORTED | Unsupported HTTP response. |
Definition at line 50 of file RedfishRestExProtocol.c.
Creates a child handle and installs a protocol.
The CreateChild() function installs a protocol on ChildHandle. If ChildHandle is a pointer to NULL, then a new handle is created and returned in ChildHandle. If ChildHandle is not a pointer to NULL, then the protocol installs on the existing ChildHandle.
- Parameters
-
[in] | This | Pointer to the EFI_SERVICE_BINDING_PROTOCOL instance. |
[in] | ChildHandle | Pointer to the handle of the child to create. If it is NULL, then a new handle is created. If it is a pointer to an existing UEFI handle, then the protocol is added to the existing UEFI handle. |
- Return values
-
EFI_SUCCES | The protocol was added to ChildHandle. |
EFI_INVALID_PARAMETER | ChildHandle is NULL. |
EFI_OUT_OF_RESOURCES | There are not enough resources available to create the child |
other | The child handle was not created |
Creates a child handle and installs a protocol.
The CreateChild() function installs a protocol on ChildHandle. If ChildHandle is a pointer to NULL, then a new handle is created and returned in ChildHandle. If ChildHandle is not a pointer to NULL, then the protocol installs on the existing ChildHandle.
- Parameters
-
[in] | This | Pointer to the EFI_SERVICE_BINDING_PROTOCOL instance. |
[in] | ChildHandle | Pointer to the handle of the child to create. If it is NULL, then a new handle is created. If it is a pointer to an existing UEFI handle, then the protocol is added to the existing UEFI handle. |
- Return values
-
EFI_SUCCESS | The protocol was added to ChildHandle. |
EFI_INVALID_PARAMETER | ChildHandle is NULL. |
EFI_OUT_OF_RESOURCES | There are not enough resources available to create the child |
other | The child handle was not created |
Definition at line 672 of file RedfishRestExDriver.c.
Destroys a child handle with a protocol installed on it.
The DestroyChild() function does the opposite of CreateChild(). It removes a protocol that was installed by CreateChild() from ChildHandle. If the removed protocol is the last protocol on ChildHandle, then ChildHandle is destroyed.
- Parameters
-
[in] | This | Pointer to the EFI_SERVICE_BINDING_PROTOCOL instance. |
[in] | ChildHandle | Handle of the child to destroy |
- Return values
-
EFI_SUCCES | The protocol was removed from ChildHandle. |
EFI_UNSUPPORTED | ChildHandle does not support the protocol that is being removed. |
EFI_INVALID_PARAMETER | Child handle is NULL. |
EFI_ACCESS_DENIED | The protocol could not be removed from the ChildHandle because its services are being used. |
other | The child handle was not destroyed |
Destroys a child handle with a protocol installed on it.
The DestroyChild() function does the opposite of CreateChild(). It removes a protocol that was installed by CreateChild() from ChildHandle. If the removed protocol is the last protocol on ChildHandle, then ChildHandle is destroyed.
- Parameters
-
[in] | This | Pointer to the EFI_SERVICE_BINDING_PROTOCOL instance. |
[in] | ChildHandle | Handle of the child to destroy |
- Return values
-
EFI_SUCCESS | The protocol was removed from ChildHandle. |
EFI_UNSUPPORTED | ChildHandle does not support the protocol that is being removed. |
EFI_INVALID_PARAMETER | Child handle is NULL. |
EFI_ACCESS_DENIED | The protocol could not be removed from the ChildHandle because its services are being used. |
other | The child handle was not destroyed |
Definition at line 816 of file RedfishRestExDriver.c.