| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/State/Decorator/ |
| H A D | meson.build | 2 subdir('Availability') subdir
5 …input: [ '../../../../../yaml/xyz/openbmc_project/State/Decorator/Availability.interface.yaml', ],
6 output: [ 'Availability.md' ],
13 'xyz/openbmc_project/State/Decorator/Availability',
|
| /openbmc/linux/drivers/ras/ |
| H A D | Kconfig | 3 bool "Reliability, Availability and Serviceability (RAS) features"
16 Availability is the probability a system is operational at a given
24 Note that Reliability and Availability are distinct concepts:
26 correctly, including avoiding data corruption, whereas Availability
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/State/Decorator/Availability/ |
| H A D | meson.build | 4 …input: [ '../../../../../../yaml/xyz/openbmc_project/State/Decorator/Availability.interface.yaml',…
12 'xyz/openbmc_project/State/Decorator/Availability',
|
| /openbmc/pldm/platform-mc/ |
| H A D | sensor_manager.hpp | 53 void updateAvailableState(pldm_tid_t tid, Availability state) in updateAvailableState()
109 std::map<pldm_tid_t, Availability> availableState;
|
| H A D | event_manager.hpp | 82 void updateAvailableState(pldm_tid_t tid, Availability state) in updateAvailableState()
212 std::unordered_map<pldm_tid_t, Availability> availableState;
|
| H A D | manager.hpp | 88 void updateAvailableState(pldm_tid_t tid, Availability state) in updateAvailableState()
|
| H A D | numeric_sensor.hpp | 43 sdbusplus::xyz::openbmc_project::State::Decorator::server::Availability>;
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-extended/kronosnet/ |
| H A D | kronosnet_1.24.bb | 5 designed for High Availability use cases, where redundancy, security, \
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | dbus_sensor.hpp | 54 sdbusplus::xyz::openbmc_project::State::Decorator::server::Availability;
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/keepalived/ |
| H A D | keepalived_2.2.8.bb | 1 SUMMARY = "High Availability monitor built upon LVS, VRRP and service pollers"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/perl-layer/recipes-support/rasdaemon/ |
| H A D | rasdaemon_0.8.0.bb | 1 DESCRIPTION = "Tools to provide a way to get Platform Reliability, Availability and Serviceability …
|
| /openbmc/linux/Documentation/virt/kvm/x86/ |
| H A D | msr.rst | 56 Availability of this MSR must be checked via bit 3 in 0x4000001 cpuid
127 coordinated between the guest and the hypervisor. Availability
144 Availability of this MSR must be checked via bit 3 in 0x4000001 cpuid
157 Availability of this MSR must be checked via bit 0 in 0x4000001 cpuid
169 Availability of this MSR must be checked via bit 0 in 0x4000001 cpuid
|
| /openbmc/pldm/common/ |
| H A D | types.hpp | 17 using Availability = bool; typedef
|
| /openbmc/linux/Documentation/power/ |
| H A D | opp.rst | 12 4. OPP Availability Control Functions
67 Note on OPP Availability
201 4. OPP Availability Control Functions
|
| /openbmc/phosphor-power/phosphor-power-supply/ |
| H A D | power_supply.hpp | 57 sdbusplus::xyz::openbmc_project::State::Decorator::server::Availability;
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-daemons/opensaf/ |
| H A D | opensaf_5.22.01.bb | 3 middleware consistent with Service Availability Forum (SA Forum) \
|
| /openbmc/dbus-sensors/ |
| H A D | README.md | 31 xyz.openbmc_project.State.Decorator.Availability
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | qe_firmware.rst | 12 II - Microcode Availability
34 II - Microcode Availability
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/licenses/ |
| H A D | AOM-Patent-License-1.0 | 14 1.2.1. Availability. As a condition to the grant of rights to Licensee to make,
|
| /openbmc/linux/Documentation/networking/ |
| H A D | bonding.rst | 83 11. Configuring Bonding for High Availability
84 11.1 High Availability in a Single Switch Topology
85 11.2 High Availability in a Multiple Switch Topology
568 determined. See the High Availability section for additional
2222 11. Configuring Bonding for High Availability
2225 High Availability refers to configurations that provide
2232 11.1 High Availability in a Single Switch Topology
2246 11.2 High Availability in a Multiple Switch Topology
2831 Availability and the documentation for each mode for additional
2846 6. Can bonding be used for High Availability?
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | design.md | 118 - xyz.openbmc_project.State.Decorator.Availability
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | emulation.rst | 182 - RAS (Reliability, Serviceability and Availability): "minimum RAS Extension" only
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | memory-hotplug.rst | 291 Availability depends on the CONFIG_ARCH_MEMORY_PROBE
300 Availability depends on the CONFIG_MEMORY_HOTPLUG kernel
377 Availability depends on the CONFIG_MEMORY_HOTREMOVE
|
| /openbmc/docs/security/ |
| H A D | network-security-considerations.md | 22 - Availability: If an agent can overwhelm the BMC's resources, either by
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | ras.rst | 4 Reliability, Availability and Serviceability
10 Reliability, Availability and Serviceability (RAS) is a concept used on
19 Availability
|