Searched hist:"1 f971f2d" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/HardwareIsolation/ |
| H A D | Entry.interface.yaml | 1f971f2d Mon May 17 06:13:25 CDT 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 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
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/HardwareIsolation/Entry/ |
| H A D | meson.build | 1f971f2d Mon May 17 06:13:25 CDT 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 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
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/HardwareIsolation/ |
| H A D | meson.build | 1f971f2d Mon May 17 06:13:25 CDT 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 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
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/ |
| H A D | meson.build | 1f971f2d Mon May 17 06:13:25 CDT 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 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
|