Lines Matching full:will

69 - Both IPMI and PLDM stacks will give the host a set amount of time to respond.
70   Lack of response within this time limit will result in the BMC potentially
73 - IPMI and PLDM will implement a phosphor-dbus-interface interface,
74   `xyz.openbmc_project.Condition.HostFirmware`, which will have a
80 - IPMI will continue to utilize the SMS_ATN command to indicate to the host that
82   command, it will be considered up and running
86 - PLDM will utilize a GetTID command to the host to determine if it is running
87 - Where applicable, PLDM will provide a mechanism to distinguish between
91     firmware and talking PLDM but the BMC recovery paths will differ based on
107 IPMI and PLDM software will be started as applicable. A combination of systemd
108 services and applications within phosphor-state-manager will coordinate the
111 software in phosphor-state-manager will take the appropriate action of creating
115 The systemd targets responsible for this and any common services will be hosted
124 A separate service and application will be created within phosphor-state-manager
138 IBM systems will utilize a processor CFAM register. The specific register is
142 via IPMI or PLDM, then the BMC will read this processor CFAM register.
144 The Host code will write `0xA5000001` to this register to indicate when it has
146 BMC. If the BMC sees this value written in the CFAM register, then it will leave
148 PLDM. It will log an error indicating it was unable to communicate with the host
149 but it will also show the host state as `Running`.
151 If the register is not `0xA5000001`, then the BMC will follow whatever recovery
156 during the boot of the system. Host firmware will clear this register in
157 shutdown scenarios. To handle different host crash scenarios, the register will
167 or PLDM path will be fine, and as a backup option, system owners can put their
176 The normal path of IPMI and PLDM will be simple to test. Boot your system and
180 The more complicated tests will be error paths: