Avi Kivity wrote:
I have emulated a PCI device on Qemu and hooked my sample/simple
driver to that virtio device on the guest.
This is independent of the existing virtio PCI device?
As a part of "Kick" routine in my guest driver I could see the
notification happening from Guest-Qemu and In the Qemu process as a
part of handle output for the emulated device I am simply doing
"virtio_notify(vdev, vq)" but I don't see my callback getting called
which is already registered as a part of "find_vq" in guest driver's
probe.
You need to enable notifications, not sure how exactly.
By default, if you zeroed the memory for the ring, notifications are
enabled. You have to set a bit to disable notifications. It sounds
like you aren't properly injecting the IRQ which is hard to assess
without more detail about what the particular device you've added to QEMU.
Are you reusing the existing virtio PCI infrastructure in QEMU?
BTW, the emulated device is allocated with "GSI 11" where as for
other emulated devices like "virtio-blk" is associated with GSI 10
which I found in "dmesg's". Is this a reason why interrupt is not
delivered from Qemu-Guest?
Interrupts for PCI devices are assigned based on the slots where they
sit. Both GSI 10 and GSI 11 are PCI link interrupts.
virtio-pci always uses LNK A. How it gets mapped to GSI depends on the
slot as Avi mentioned.
Regards,
Anthony Liguori
--
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
