Dump: Add token to host dump entries

This commit introduces a token field to the
xyz.openbmc_project.Dump.Entry.System and
com.ibm.Dump.Entry.Resource interfaces. This token is
exchanged from the host when a request to create a dump
is made. The token can be used to identify the dump
entry once the collection is completed. This addition
enhances the tracking of dump entries for the dumps
collected in the host.

Change-Id: Ic4ad9d10bb0b8afd73d2b8d58a920ae5d2b131b8
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
2 files changed
tree: 1af053b7a3c99724f4de93562695df7bcf48fd8b
  1. gen/
  2. subprojects/
  3. yaml/
  4. .gitignore
  5. .markdownlint.yaml
  6. .prettierrc.yaml
  7. .shellcheck
  8. LICENSE
  9. meson.build
  10. meson_options.txt
  11. OWNERS
  12. README.md
  13. requirements.md
README.md

phosphor-dbus-interfaces

YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.

Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.

Building

This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.

The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.

Configuration

Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References