| commit | cb01cd402e2c76bc7206317977706f2fd2073218 | [log] [tgz] |
|---|---|---|
| author | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Mon Jul 10 02:20:18 2023 -0500 |
| committer | Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com> | Tue Jul 18 14:31:14 2023 -0500 |
| tree | 48d9b8170cf83259573c32aa3b1e8990f17949b4 | |
| parent | 2117deabad40f9ac63815f3338e7ac3e1e3fe397 [diff] |
Dump: Add user-challenge to System Dump entry This commit introduces a 'UserChallenge' field to the xyz.openbmc_project.Dump.Entry.System interface. This update specifically addresses the requirement for non-disruptive system dumps. Non-disruptive dumps are requested to the host and do not disrupt the current system state. However, as they consume significant host resources and involve the collection of host memory data, they must be executed by authorized personnel. To enforce this, the host requires user-challenge validation to process the dump request. If the provided user-challenge is incorrect, the host rejects the operation. Change-Id: Ia9871a7264e036715a3ebe10f9054a2302e64c32 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