| commit | a2eb94f6307b1de1a16b14d625fc14a1df138965 | [log] [tgz] |
|---|---|---|
| author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Wed May 05 02:44:28 2021 -0500 |
| committer | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Mon Jul 19 08:25:59 2021 -0500 |
| tree | 1e1f80e3fa4880d22cecbaf844f307df2931eda6 | |
| parent | c6f2d7a7f1e68c63d242f1adef729fc57cb49c94 [diff] |
Add hardware dump entry interface and type
Hardware dumps get collected during a critical
failure on the hardware units like processor
chips.
This commits add following:
- The interface for hardware dump entry.
- Updated the arguments list with following
- Hardware: A new dump type to list of supported
dumps
- FailingUnitId: Id of the hardware unit failed
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
Change-Id: Id209cca5d4ff167d21c45c752a687280aa469830
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 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