When a CPU receives an Interrupt Request (IRQ), it first checks if it must react to the interrupt. So-called Maskable Interrupts allow a programmer to specify that the CPU does ignore it, while Non-Maskeable Interrupt requests must be serviced.
It is important to note that an Interrupt is a way to communicate asynchronously with the CPU - very much like sending an email.
When you send an email to a person, you cannot know at which time the person reads the message, let alone when the person reacts.
A phone call, on the other hand is synchronous (happening at the same time): when I call you, you must answer right now.
Interrupts where introduced to allow tgis email-like communication with slower hardware, like a hard-disk. This way, the CPU can order something from the HD, like "go to this location", the CPU can then return to more important stuff, while the HD seeks. When the HD is done, it sends the CPU an IRQ, which tells the CPU "I am done, talk to me".
The CPU then does a so-called contex-switch, which is a rather costly operation: it must store all the data it was working on earlier in some secure way, normally on the stack and then begin to execute the so-called Interrupt Handler, a piece of software associated with the number of the IRQ.
After executing it, it can carry on doing what it did earlier (after having loaded all the data back into its registers).
The concept of IRQs make multi-tasking possible, here, the OS interrupts each process after its time-slice has expired.
In a DMA while the data is transferred between the memory and the device, if it is stopped or interrupted by any other device like CPU, it would result into a Data loss, since DMA doesnt have a program counter unlike CPU which stores it current position. In CPU if it is interrupted, it suspends it s operation without any data loss. Hence DMA has a higher priority than CPU.
The POST runs
goes into the computer's hardware.
When the circuit is interrupted, the current stops flowing.
The chemical reaction is interrupted.
Preemptive scheduling allows a process to be interrupted in the midst of its execution, taking the CPU away and allocating it to another process.Non-preemptive scheduling ensures that a process relinquishes control of the CPU only when it finishes with its current CPU burst.
Will not be interrupted is correct
The CPU will overheat (safety shutdown usually happens at around 69 degrees C), and you will be unable to use the computer for prolonged periods unless it is running with less than 50% CPU usage in a very cool environment. Side effects of constant CPU overheat can include the capacitors blowing on the motherboard if they are near the CPU heatsink.
The circuit current is interrupted and all the lights will go out.
It reluctantly moves and then shuts off
The CPU does not "know" it is not a thinking being. What happens is that the interrupt flag ( a binary true or false register) is detected by the operating system which is being executed by the CPU and the code of the operating system runs a routine in response.
there are about 50 episodes that, that happens you have to explain more