commit | acf5cdf3a1da1be760bd289a4485269a049cb3f3 | [log] [tgz] |
---|---|---|
author | Elie Kheirallah <khei@google.com> | Mon Jun 12 22:42:04 2023 +0000 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 13 20:04:55 2023 +0000 |
tree | 1fff93c817a33d04a1bd83ecf9013b236aacaf6c | |
parent | 659252d10328bf4bd2e59ca573f30b9d8c8e14e3 [diff] |
devices: virtio_pci_device: restore fix Restore right now tries to restore interrupts at all times. If the device was not previously activated, the interrupt will always be null which will cause the restore to always fail. Add a check to see if the device was previously activated before restoring the interrupt. BUG=N/A Test=presubmit Change-Id: Ifddc27f2a63bab7b1509b934a9c14d129977a401 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4610691 Reviewed-by: Richard Zhang <rizhang@google.com> Commit-Queue: Elie Kheirallah <khei@google.com> Reviewed-by: Frederick Mayle <fmayle@google.com>
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the ChromeOS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on ChromeOS devices.