| #
0e78828c |
| 31-Jan-2025 |
Patrick Williams <patrick@stwcx.xyz> |
regenerate-meson: enable meson formatting
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I5bc2c84cf2ebb3a8d64c96bf3c02e4f34d1f28dd
|
| #
7f154004 |
| 03-Jan-2025 |
Patrick Williams <patrick@stwcx.xyz> |
build: support registry generation
sdbus++-gen-meson version 10 adds support for redfish registry
generation and greatly simplifies the install directives.
Regenerate the YAML meson files and modif
build: support registry generation
sdbus++-gen-meson version 10 adds support for redfish registry
generation and greatly simplifies the install directives.
Regenerate the YAML meson files and modify the base meson.build
as necessary. Also, format meson.build with `meson format`.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I77586fca7742d5468803913cb45276ca57271655
show more ...
|
| #
11335246 |
| 12-Sep-2022 |
Patrick Williams <patrick@stwcx.xyz> |
gen: update due to sdbusplus-gen-meson change
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I9491eb608d9c6849b3e39fe212054a3651bfb824
|
| #
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 ...
|
| #
b96ed610 |
| 26-Jun-2021 |
Ramesh Iyyar <rameshi1@in.ibm.com> |
HardwareIsolation: Added the error code
Added the error code which is specific to hardware isolation
interfaces.
Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com>
Change-Id: I787bc1a422d197f016d010
HardwareIsolation: Added the error code
Added the error code which is specific to hardware isolation
interfaces.
Signed-off-by: Ramesh Iyyar <rameshi1@in.ibm.com>
Change-Id: I787bc1a422d197f016d0102f5ad659ab679f2b6e
show more ...
|
| #
1f971f2d |
| 17-May-2021 |
Ramesh Iyyar <rameshi1@in.ibm.com> |
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 h
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
show more ...
|