| commit | 1f971f2d647b6d301208c4e39b3bbfb94eb1d029 | [log] [tgz] |
|---|---|---|
| author | Ramesh Iyyar <rameshi1@in.ibm.com> | Mon May 17 06:13:25 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Jun 29 19:47:56 2021 +0000 |
| tree | e401acf9bbc6e8b9ea3614d76daf48544613769b | |
| parent | 3a11b99bfe63b2128e01786c78e4247f9d45bfcc [diff] |
HardwareIsolation: Added the "Entry" interface In an OpenPOWER based system, a user or an application (in the error path if the hardware is faulty) can isolate hardware and the respective isolated hardware part will be ignored to init during the next boot of the host. This entry interface will be used to maintain the isolated hardware information. Please refer https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/27804 to get more details of hardware isolation. Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com> Change-Id: I61cfdc757dd281e8b0b746304f7e5eafd6ef421d
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