Re: [PATCH v2] Shared memory device with interrupt support

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

 



Cam Macdonell wrote:

My usual noob questions: Do I need to run Greg's tree on the host for the necessary irqfd/eventfd suppport?

Yes (though irqfd will be merged real soon, and iosignalfd somewhat afterwards).

Are there any examples to work from aside from Greg's unit tests?

No.

You don't really need to irqfd and iosignalfd to implement all of this, they're just optimizations. You can still pass the eventfds around. If you don't have irqfd, have qemu poll the eventfd, and when something happens, inject and interrupt. Likewise, if you don't have iosignalfd, register a pio/mmio handler for the command register, and when they fire touch all of the relevant irqfds. You'll need that anyway for backwards compatibility and for level-triggered pci interrupts, which irqfd doesn't support.

--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

--
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