| commit | d67b2627fd1d16ad96866c6288d54bcf63a992e3 | [log] [tgz] |
|---|---|---|
| author | Claire Weinan <cweinan@google.com> | Sun Apr 17 10:29:12 2022 -0700 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Thu Sep 01 00:59:10 2022 +0000 |
| tree | e577389b98f8260f056e14aadb145eb63732a57b | |
| parent | bcb24e1338cf2818d9e4d389eaba46b871ba60c1 [diff] |
FaultLog: Add new FaultLog dump entry interface Fault Log is a new type of dump in openbmc/phosphor-debug-collector. For details please see https://github.com/openbmc/docs/blob/master/designs/hw-fault-monitor.md This new interface (xyz.openbmc_project.Dump.Entry.FaultLog) contains properties that are specific to Fault Log entries. Fault log entries can contain references to fault data captured and stored by other code modules (e.g. see the PrimaryLogId property). A fault log entry represents a bundle of data from various sources that correspond to the same fault event (additional properties such as references to secondary logs may be added later). Change-Id: I491b8fc58c752513d9066c908bf91999380e17c5 Signed-off-by: Claire Weinan <cweinan@google.com>
YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.
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.
Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:
-Ddata_com_ibm=true-Ddata_org_open_power=trueExample: meson builddir -Ddata_com_ibm=true && ninja -C builddir