commit | 3a77dc425f5eb9237de4d78f7099b1f0a3062ab7 | [log] [tgz] |
---|---|---|
author | Andrew Geissler <geissonator@yahoo.com> | Mon Jan 25 14:36:47 2021 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Feb 10 20:10:39 2021 +0000 |
tree | b5d55664df86cc46a4beae330411d872459afff9 | |
parent | 9969a5b4016bc8ae62e5f23aad476c6352dfac86 [diff] |
clarify quiesce use cases for host This interface will be utilized on some systems to represent the hypervisor state. Clarify that Quiesce can represent different host states based on which object is implementing it. Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Change-Id: Ib5abc5f95dedbdb6e6184cf18f50aca1bb267852
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=true
Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir