edk2/OvmfPkg/Include/Library/SerializeVariablesLib.h
Michael Kubacki a536e5d699 OvmfPkg: Replace include guards with #pragma once
Replace traditional `#ifndef`/`#define`/`#endif` include guards with
`#pragma` once.

`#pragma once` is a widely supported preprocessor directive that
prevents header files from being included multiple times. It is
supported by all toolchains used to build edk2: GCC, Clang/LLVM, and
MSVC.

Note: Headers taken directly from external projects, such as those
in OvmfPkg/Include/IndustryStandard/Xen/ were not modified since they
may be periodically re-synced and do not follow other edk2 coding
stadards.

Compared to macro-based include guards, `#pragma once`:

- Eliminates the risk of macro name collisions or copy/paste errors
  where two headers inadvertently use the same guard macro.
- Eliminate inconsistency in the way include guard macros are named
  (e.g., some files use `__FILE_H__`, others use `FILE_H_`, etc.).
- Reduces boilerplate (three lines replaced by one).
- Avoids polluting the macro namespace with guard symbols.
- Can improve build times as the preprocessor can skip re-opening the
  file entirely, rather than re-reading it to find the matching
  `#endif` ("multiple-include optimization").
  - Note that some compilers may already optimize traditional include
    guards, by recognzining the idiomatic pattern.

This change is made acknowledging that overall portability of the
code will technically be reduced, as `#pragma once` is not part of the
C/C++ standards.

However, this is considered acceptable given:

1. edk2 already defines a subset of supported compilers in
   BaseTools/Conf/tools_def.template, all of which have supported
   `#pragma once` for over two decades.
2. There have been concerns raised to the project about inconsistent
   include guard naming and potential macro collisions.

Approximate compiler support dates:

- MSVC: Supported since Visual C++ 4.2 (1996)
- GCC: Supported since 3.4 (2004)
  (http://gnu.ist.utl.pt/software/gcc/gcc-3.4/changes.html)
- Clang (LLVM based): Since initial release in 2007

Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
2026-02-23 21:01:28 +00:00

209 lines
7.1 KiB
C

/** @file
Serialize & Deserialize UEFI Variables
Copyright (c) 2011, Intel Corporation. All rights reserved.<BR>
SPDX-License-Identifier: BSD-2-Clause-Patent
**/
#pragma once
/**
Callback function for each variable
@param[in] Context - Context as sent to the iteration function
@param[in] VariableName - Refer to RuntimeServices GetNextVariableName
@param[in] VendorGuid - Refer to RuntimeServices GetNextVariableName
@param[in] Attributes - Refer to RuntimeServices GetVariable
@param[in] DataSize - Refer to RuntimeServices GetVariable
@param[in] Data - Refer to RuntimeServices GetVariable
@retval RETURN_SUCCESS Continue iterating through the variables
@return Any RETURN_ERROR Stop iterating through the variables
**/
typedef
RETURN_STATUS
(EFIAPI *VARIABLE_SERIALIZATION_ITERATION_CALLBACK)(
IN VOID *Context,
IN CHAR16 *VariableName,
IN EFI_GUID *VendorGuid,
IN UINT32 Attributes,
IN UINTN DataSize,
IN VOID *Data
);
/**
Creates a new variable serialization instance
@param[out] Handle - Handle for a variable serialization instance
@retval RETURN_SUCCESS - The variable serialization instance was
successfully created.
@retval RETURN_OUT_OF_RESOURCES - There we not enough resources to
create the variable serialization instance.
**/
RETURN_STATUS
EFIAPI
SerializeVariablesNewInstance (
OUT EFI_HANDLE *Handle
);
/**
Free memory associated with a variable serialization instance
@param[in] Handle - Handle for a variable serialization instance
@retval RETURN_SUCCESS - The variable serialization instance was
successfully freed.
@retval RETURN_INVALID_PARAMETER - Handle was not a valid
variable serialization instance.
**/
RETURN_STATUS
EFIAPI
SerializeVariablesFreeInstance (
IN EFI_HANDLE Handle
);
/**
Creates a new variable serialization instance using the given
binary representation of the variables to fill the new instance
@param[out] Handle - Handle for a variable serialization instance
@param[in] Buffer - A buffer with the serialized representation
of the variables. Must be the same format as produced
by SerializeVariablesToBuffer.
@param[in] Size - This is the size of the binary representation
of the variables.
@retval RETURN_SUCCESS - The binary representation was successfully
imported into a new variable serialization instance
@retval RETURN_OUT_OF_RESOURCES - There we not enough resources to
create the new variable serialization instance
**/
RETURN_STATUS
EFIAPI
SerializeVariablesNewInstanceFromBuffer (
OUT EFI_HANDLE *Handle,
IN VOID *Buffer,
IN UINTN Size
);
/**
Iterates all variables found with RuntimeServices GetNextVariableName
@param[in] CallbackFunction - Function called for each variable instance
@param[in] Context - Passed to each call of CallbackFunction
@retval RETURN_SUCCESS - All variables were iterated without the
CallbackFunction returning an error
@retval RETURN_OUT_OF_RESOURCES - There we not enough resources to
iterate through the variables
@return Any of RETURN_ERROR indicates an error reading the variable
or an error was returned from CallbackFunction
**/
RETURN_STATUS
EFIAPI
SerializeVariablesIterateSystemVariables (
IN VARIABLE_SERIALIZATION_ITERATION_CALLBACK CallbackFunction,
IN VOID *Context
);
/**
Iterates all variables found in the variable serialization instance
@param[in] Handle - Handle for a variable serialization instance
@param[in] CallbackFunction - Function called for each variable instance
@param[in] Context - Passed to each call of CallbackFunction
@retval RETURN_SUCCESS - All variables were iterated without the
CallbackFunction returning an error
@retval RETURN_OUT_OF_RESOURCES - There we not enough resources to
iterate through the variables
@return Any of RETURN_ERROR indicates an error reading the variable
or an error was returned from CallbackFunction
**/
RETURN_STATUS
EFIAPI
SerializeVariablesIterateInstanceVariables (
IN EFI_HANDLE Handle,
IN VARIABLE_SERIALIZATION_ITERATION_CALLBACK CallbackFunction,
IN VOID *Context
);
/**
Sets all variables found in the variable serialization instance
@param[in] Handle - Handle for a variable serialization instance
@retval RETURN_SUCCESS - All variables were set successfully
@retval RETURN_OUT_OF_RESOURCES - There we not enough resources to
set all the variables
@return Any of RETURN_ERROR indicates an error reading the variables
or in attempting to set a variable
**/
RETURN_STATUS
EFIAPI
SerializeVariablesSetSerializedVariables (
IN EFI_HANDLE Handle
);
/**
Adds a variable to the variable serialization instance
@param[in] Handle - Handle for a variable serialization instance
@param[in] VariableName - Refer to RuntimeServices GetVariable
@param[in] VendorGuid - Refer to RuntimeServices GetVariable
@param[in] Attributes - Refer to RuntimeServices GetVariable
@param[in] DataSize - Refer to RuntimeServices GetVariable
@param[in] Data - Refer to RuntimeServices GetVariable
@retval RETURN_SUCCESS - All variables were set successfully
@retval RETURN_OUT_OF_RESOURCES - There we not enough resources to
add the variable
**/
RETURN_STATUS
EFIAPI
SerializeVariablesAddVariable (
IN EFI_HANDLE Handle,
IN CHAR16 *VariableName,
IN EFI_GUID *VendorGuid,
IN UINT32 Attributes,
IN UINTN DataSize,
IN VOID *Data
);
/**
Serializes the variables known to this instance into the
provided buffer.
@param[in] Handle - Handle for a variable serialization instance
@param[out] Buffer - A buffer to store the binary representation
of the variables.
@param[in,out] Size - On input this is the size of the buffer.
On output this is the size of the binary representation
of the variables.
@retval RETURN_SUCCESS - The binary representation was successfully
completed and returned in the buffer.
@retval RETURN_OUT_OF_RESOURCES - There we not enough resources to
save the variables to the buffer.
@retval RETURN_INVALID_PARAMETER - Handle was not a valid
variable serialization instance or
Size or Buffer were NULL.
**/
RETURN_STATUS
EFIAPI
SerializeVariablesToBuffer (
IN EFI_HANDLE Handle,
OUT VOID *Buffer,
IN OUT UINTN *Size
);