ae56dbca | 17-May-2021 |
Ramesh Iyyar <rameshi1@in.ibm.com> |
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
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
show more ...
|