mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2024-08-22 16:01:15 +00:00
06dc708515
The reset system is asynchronous with an I/O event (PIO or MMIO) for ACPI/i8042/CMOS triggering a write to the reset_evt event handler. The VMM thread will pick up this event on the VMM main loop and then trigger a shutdown in the CpuManager. However since there is some delay between the CPU threads being marked to be killed (through the CpuManager::cpus_kill_signalled bool) it is possible for the guest vCPU that triggered the exit to be re-entered when the vCPU KVM_RUN is called after the I/O exit is completed. This is undesirable and in particular the Linux kernel will attempt to jump to real mode after a CMOS based exit - this is unsupported in nested KVM on AMD on Azure and will trigger an error in KVM_RUN. Solve this problem by spinning in the device that has triggered the reset until the vcpus_kill_signalled boolean has been updated indicating that the VMM thread has received the event and called CpuManager::shutdown(). In particular if this bool is set then the vCPU threads will not re-enter the guest. Signed-off-by: Rob Bradford <rbradford@rivosinc.com> |
||
|---|---|---|
| .. | ||
| balloon.rs | ||
| block.rs | ||
| cmos.rs | ||
| console.rs | ||
| http_api.rs | ||
| iommu.rs | ||
| linux_loader_cmdline.rs | ||
| linux_loader.rs | ||
| mem.rs | ||
| net.rs | ||
| pmem.rs | ||
| qcow.rs | ||
| rng.rs | ||
| serial.rs | ||
| vhdx.rs | ||
| watchdog.rs | ||