Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-vpd-parser / 0fb5c3bfccf50feed38da9798fe2a57fcd4523b5
commit0fb5c3bfccf50feed38da9798fe2a57fcd4523b5[log] [tgz]
authorSouvik Roy <souvikroyofficial10@gmail.com>Mon Sep 15 08:18:25 2025 +0000
committerSouvik Roy <souvikroyofficial10@gmail.com>Thu Oct 09 15:26:39 2025 +0000
treea00e5f740add40c3b152a7597286af56fc920df8
parentd7c7cb5d2369e179361302f281b10af131260d0f [diff]
FileLogger:async file logging stub

This commit implements a class to handle asynchronous file logging. It
extends the LogFileHandler class. Logging messages to file from multiple
VPD collection threads synchronously affects the overall VPD collection
time, hence these logs need to be handled asynchronously. This commit
includes stub changes only and actual implementation will be handled in
future commit(s).

Change-Id: I81342e20a10015364d7de5b77531688aeabe6000
Signed-off-by: Souvik Roy <souvikroyofficial10@gmail.com>
2 files changed
tree: a00e5f740add40c3b152a7597286af56fc920df8
  1. configuration/
  2. docs/
  3. service_files/
  4. test/
  5. vpd-manager/
  6. vpd-tool/
  7. vpdecc/
  8. wait-vpd-parser/
  9. .clang-format
  10. .gitignore
  11. LICENSE
  12. meson.build
  13. meson.options
  14. OWNERS
  15. README.md
README.md

Overview

This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both OpenPower VPD and IPZ VPD formats are structured binaries that consist of records and keywords. A record is a collection of multiple keywords. More information about the format can be found at a broken link.

The repository consists of two distinct applications, which are:

OpenPower VPD Parser

This is a build-time YAML driven application that parses the OpenPower VPD format and uses the YAML configuration (see extra-properties-example.yaml and writefru.yaml) to determine:

  • The supported records and keywords.
  • How VPD data is translated into D-Bus interfaces and properties.

The application instance must be passed in the file path to the VPD (this can, for example, be a sysfs path exposed by the EEPROM device driver) and also the D-Bus object path(s) that EEPROM data needs to be published under.

IBM VPD Parser

This parser is can be built by passing in the --enable-ibm-parser configure option. This parser differs from the OpenPower VPD parser in the following ways:

  • It parses all the records and keywords from the VPD, including large keywords (Keywords that begin with a # and are > 255 bytes in length).
  • It relies on a runtime JSON configuration (see examples/inventory.json) to determine the D-Bus object path(s) that hold interfaces and properties representing the VPD for a given VPD file path.

Making the application runtime JSON driven allows us to support multiple systems (with different FRU configurations) to be supported in a single code image as well as making the application more flexible for future improvements.

TODOs and Future Improvements

  1. The long-term goal is to completely do away with the build time YAML driven configurations and instead reconcile the OpenPower VPD parser and the IBM VPD parser applications into a single runtime JSON driven application.
  2. Add details to the README on how to configure and build the application.
  3. More JSON documentation.
  4. Support for more IBM VPD formats.
  5. VPD Write and tool documentation.