keep it there until the interrupt is serviced The CPU can’t miss edges The device can “stack” interrupt reasons - leave the voltage until all reasons are ACK’ed This is “level triggered”
is more useful than events Level-driven software is about asserting state Clients can check and re-check state at any time This is the heart of Kubernetes’ controller model