Skip to main content

in_guest_signal_delivery_gate

Function in_guest_signal_delivery_gate 

Source
pub fn in_guest_signal_delivery_gate(
    config: &DetConfig,
    backend: Backend,
    owns_guest_pid_namespace: bool,
) -> bool
Expand description

The in-guest delivery gate (detcore::Config::in_guest_signal_delivery, D35 of the A5 step 3c design) for a run of backend on Hermit’s default in-guest route, from its final prepared configuration and the launcher’s PID-namespace ownership: an in-guest backend, site patching off, sequentialized threads, no configuration in which the two-phase delivery protocol cannot be kept (detcore::two_phase_refusal: a timeslice, a recorded or replayed schedule, an in-effect pipe hand-off, and the rows no in-guest backend reaches), and a scheduler that owns the guest’s PID namespace (owns_guest_pid_namespace, which the launch sites compute with scheduler_owns_guest_pid_namespace). The in-guest loader route never asks (D26, D43): its configuration keeps the gate off.