| commit | 2117deabad40f9ac63815f3338e7ac3e1e3fe397 | [log] [tgz] |
|---|---|---|
| author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Sat Jul 08 13:28:06 2023 -0500 |
| committer | Dhruvaraj S <dhruvaraj@gmail.com> | Sun Jul 16 18:52:40 2023 +0000 |
| tree | 5937eb83e001eb014deb1eb26013cea9745ad474 | |
| parent | 27afd1f20f489d3c0eda82c18455a8ddfb291ed9 [diff] |
Dump: Add 'SystemImpact' to System Dump entry This commit introduces 'SystemImpact' to the system dump entry. This new enum field indicates whether a system dump is 'Disruptive' or 'NonDisruptive'. 'Disruptive' dumps alter the system state and capture extensive data, making them useful for diagnosing system crashes. In contrast, 'NonDisruptive' dumps do not disturb the system state while still providing valuable data for analysis. Change-Id: I03810e86e1db9d2b46891dbe2e00e436e76b2cc2 Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
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.
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