Use default SectionDescriptor constructor.

Makes it easier to write tests.

Tested: Unit tests
Google-Bug-Id: 322561358
Change-Id: I2bd16915cb61b29c24519d313400ce8f82a90b95
Signed-off-by: Aryk Ledet <arykledet@google.com>
1 file changed
tree: c03da11da02c7ce5414fe5049ddcdafc3176dbe8
  1. include/
  2. test/
  3. .clang-format
  4. LICENSE
  5. meson.build
  6. meson.options
  7. README.md
README.md

cper-lib

This is a header-only library which provides a generic interface for users to write application specific UEFI CPER log encoders.

How to use this library

The UEFI specification for CPER logs allows for many combinations of Record Header and Section Descriptor properties based on the application. However, the underlying data structure does not change from application to application. To make it easier for gBMC applications to log faults in the CPER format the user only needs to specify the type of Record and Section type(s) that the encoder will need to create.

When developing and testing your application specific encoders, you will need to install this library into your development container.

Below is some pseudo code of how a user would setup their application specific CPER encoder which takes in char array types.

class MyCperEncoder : public CperEncoder<char>
{
    RecordHeader createRecordHeader(...) override
    {...}

    SectionDescriptor createSectionDescriptor(...) override
    {
        if (sectionType == kPlatformMemory)
        {
            return createPlatformMemoryDescriptor();
        }
        else if (sectionType == kOemSection)
        {
            return createOemDescriptor();
        }
        ...
    }

    SectionDescriptor createPlatformMemoryDescriptor()
    {...}

    SectionDescriptor createOemDescriptor()
    {...}
}

To install

meson setup -C builddir
meson install -C builddir

To run unit tests

meson test -C builddir