Home
last modified time | relevance | path

Searched full:escalate (Results 1 – 25 of 32) sorted by relevance

12

/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/drbd/drbd-utils/
H A D0001-drbd-utils-support-usrmerge.patch13 scripts/drbd-demote-or-escalate@.service | 2 +-
56 diff --git a/scripts/drbd-demote-or-escalate@.service b/scripts/drbd-demote-or-escalate@.service
58 --- a/scripts/drbd-demote-or-escalate@.service
59 +++ b/scripts/drbd-demote-or-escalate@.service
62 # and then only escalate to FailureAction if that did not help.
64 -ExecStart=/lib/drbd/scripts/drbd-service-shim.sh secondary-or-escalate %I
65 +ExecStart=@nonarch_libdir@/drbd/scripts/drbd-service-shim.sh secondary-or-escalate %I
/openbmc/qemu/docs/devel/
H A Dconflict-resolution.rst13 after that fails to escalate further. This approach gives people more
61 events. The cooling off period is voluntary but may escalate to a
/openbmc/docs/designs/
H A Dbmc-service-failure-debug-and-recovery.md180 The need to escalate above mechanism 1 should come with data that captures why
188 The need to escalate to 3 would indicate that the BMC's own mechanisms for
216 1. The host make use of a timeout to escalate to recovery mechanism 3 as it's
328 1. If the `Ready` bit in STR is clear, escalate to recovery mechanism 3.
331 2. If the `IBF` bit in STR is set, escalate to recovery mechanism 3. Otherwise,
346 8. Escalate to recovery mechanism 3 if the escalation timer expires at any point
/openbmc/linux/tools/testing/selftests/arm64/signal/testcases/
H A Dmangle_pstate_invalid_mode_el1h.c6 * the mode bit to escalate exception level: this attempt must be spotted
H A Dmangle_pstate_invalid_mode_el3h.c6 * the mode bit to escalate exception level: this attempt must be spotted
H A Dmangle_pstate_invalid_mode_el2t.c6 * the mode bit to escalate exception level: this attempt must be spotted
H A Dmangle_pstate_invalid_mode_el1t.c6 * the mode bit to escalate exception level: this attempt must be spotted
H A Dmangle_pstate_invalid_mode_el2h.c6 * the mode bit to escalate exception level: this attempt must be spotted
H A Dmangle_pstate_invalid_mode_el3t.c6 * the mode bit to escalate exception level: this attempt must be spotted
/openbmc/qemu/hw/intc/
H A Darmv7m_nvic.c612 * This all means we can identify whether to escalate based only on in do_armv7m_nvic_set_pending()
617 bool escalate = false; in do_armv7m_nvic_set_pending() local
621 escalate = true; in do_armv7m_nvic_set_pending()
624 escalate = true; in do_armv7m_nvic_set_pending()
627 if (escalate) { in do_armv7m_nvic_set_pending()
629 /* We need to escalate this exception to a synchronous HardFault. in do_armv7m_nvic_set_pending()
630 * If BFHFNMINS is set then we escalate to the banked HF for in do_armv7m_nvic_set_pending()
643 /* We want to escalate to HardFault but we can't take the in do_armv7m_nvic_set_pending()
649 "Lockup: can't escalate %d to HardFault " in do_armv7m_nvic_set_pending()
679 * whether we should escalate depends on the saved context in armv7m_nvic_set_pending_lazyfp()
[all …]
H A Dpnv_xive.c57 * 2 - First escalate,
58 * 3 - Second escalate,
H A Dtrace-events282 …8_t esc_blk, uint32_t esc_idx, uint32_t end_data) "END 0x%02x/0x%04x -> escalate END 0x%02x/0x%04x…
H A Dxive2.c949 * If activated, escalate notification using the ESe PQ bits and in xive2_router_end_notify()
H A Dxive.c1925 * If activated, escalate notification using the ESe PQ bits and in xive_router_end_notify()
/openbmc/linux/Documentation/userspace-api/
H A Dno_new_privs.rst55 escalate its privileges by directly attacking setuid, setgid, and
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/drbd/
H A Ddrbd-utils_9.28.0.bb54 …nonarch_libdir@#${nonarch_libdir}#g' ${D}${systemd_unitdir}/system/drbd-demote-or-escalate@.service
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/
H A Dpinmux-node.yaml82 "function" properties can quickly escalate and become hard to write and
/openbmc/linux/drivers/scsi/isci/
H A Dtask.c426 /* If the device is gone, escalate to I_T_Nexus_Reset. */ in isci_task_lu_reset()
642 * correctly escalate the failed abort to a LUN or target reset (this is
H A Drequest.c2690 case SCU_TASK_DONE_SMP_RESP_TO_ERR: /* Escalate to dev reset? */ in isci_request_handle_controller_specific_errors()
/openbmc/linux/drivers/gpu/drm/vc4/
H A Dvc4_validate_shaders.c28 * with access to execute shaders could escalate privilege by
H A Dvc4_validate.c28 * with access to execute command lists could escalate privilege by
/openbmc/linux/drivers/scsi/libfc/
H A Dfc_fcp.c1372 * scsi-eh will escalate for when either happens. in fc_tm_done()
1701 * scsi command timer fire and scsi-ml escalate. in fc_fcp_recovery()
/openbmc/linux/arch/powerpc/mm/book3s64/
H A Dradix_tlb.c647 * this workaround is required - escalate all RIC=0 IS=1/2/3 flushes in mm_needs_flush_escalation()
/openbmc/linux/drivers/scsi/
H A Dscsi_error.c241 * Retry after abort failed, escalate to next level. in scsi_abort_command()
/openbmc/linux/arch/powerpc/kernel/
H A Dexceptions-64s.S206 * Interrupts that are taken in MSR[HV]=0 and escalate to MSR[HV]=1 are always

12