On 30/08/2016 12:45, Charls D. Chap wrote: > It needs to change context and jump to interrupt handler. > How is this change from non-root process context to non-root interrupt > context happens? > 1) In full-virtualization block io > 2) in virtio-blk io > > For example the issue path in the second case, is clearer, it's a write to > a register in pci configuration space (kick). > > Maybe it's implemented in the following calls(?) > msix_notify or pci_set_irq or in the implementation of the ioctls that > these two calls invokes in the end. Yes, it's in the ioctls. I already wrote the call paths leading to the ioctls to you: http://marc.info/?l=kvm&m=147024149120990 and I have also already explained that interrupt injections happens through ioctls on the KVM file descriptors: http://marc.info/?i=346384966.13112634.1470159219285.JavaMail.zimbra@xxxxxxxxxx Thanks, Paolo -- 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
