Re: kvm: qemu: stop/start cpus before/after devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Marcelo Tosatti wrote:
You're right, they can't. But its not bad to make it explicit, instead
of relying on the locking behaviour?

You could say that we should depend on proper locking instead the order of things shutting down and starting up :)

It's not just a cpu that can access a device; another device could dma into it, so we need to quiesce the system first (including vcpus) and then pause all devices.

--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux