2010/4/8 Avi Kivity <a...@redhat.com>: > On 04/08/2010 12:14 PM, Yoshiaki Tamura wrote: >>> >>> I don't think you can in the general case. But if you gate output at the >>> device level, instead of the instruction level, the problem goes away, >>> no? >> >> Yes, it should. >> To implement this, we need to make No.3 to be called asynchronously. If >> qemu is already handling I/O asynchronously, it would be relatively easy to >> make this. > > Yes, you can release the I/O from the iothread instead of the vcpu thread. > You can make virtio_net_handle_tx() disable virtio notifications and > initiate state sync and return, when state sync continues you can call the > original virtio_net_handle_tx(). If the secondary takes over, it needs to > call the original virtio_net_handle_tx() as well.
Agreed. Let me try it. Meanwhile, I'll post what I have done including the hack preventing rip to proceed. I would appreciate if you could comment on that too, to keep things in a good direction. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
