| commit | ae56dbca7a01e4da52093c2b0231620e41e88927 | [log] [tgz] |
|---|---|---|
| author | Ramesh Iyyar <rameshi1@in.ibm.com> | Mon May 17 06:40:00 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Tue Jul 27 22:00:56 2021 +0000 |
| tree | dd554ce3c977873843746b59e6c2ce88c667087f | |
| parent | b96ed610b5ea5014830a809309c7b4df7eb7d429 [diff] |
HardwareIsolation: Added the "Create" interface
In an OpenPOWER based system, the user can isolate hardware,
and the respective isolated hardware part will be ignored
to init during the next boot of the host.
This interface can be used by a user to manually isolate
hardware and we don't have/generate the event log because
this is not an error case and the user voluntarily tried to
isolate hardware.
The added method will throw below exceptions.
- xyz.openbmc_project.Common.Error.InvalidArgument
- If the given parameters are invalid.
- If the given hardware is not found to isolate.
- xyz.openbmc_project.Common.Error.TooManyResources
- If the platforms are not allowed to isolate hardware
when the isolated hardware count is reached to the maximum
allowed size.
- xyz.openbmc_project.HardwareIsolation.Error.IsolatedAlready
- If the isolating hardware is already isolated.
- xyz.openbmc_project.Common.Error.NotAllowed
- If the given hardware cannot be isolated permanently.
- xyz.openbmc_project.Common.Error.Unavailable
- If the given hardware cannot be isolated temporarily.
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: I8868e0f7e07694a902b790a909ee7ff20272ca81
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