qemu/hw/device-assignment: questions about msix_table_page

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

 



Sheng, Marcelo,
I've been reading code in qemu/hw/device-assignment.c, and
I have a couple of questions about msi-x implementation:
1. What is the reason that msix_table_page is allocated
   with mmap and not with e.g. malloc?
2. msix_table_page has the guest view of the msix table for the device.
   However, even this memory isn't mapped into guest directly, instead
   msix_mmio_read/msix_mmio_write perform the write in qemu.
   Won't it be possible to map this page directly into
   guest memory, reducing the overhead for table writes?

Could you shed light on this for me please?
Thanks,

( ------)
( Resending with a sane subject/reply-to address. )
( Sorry about multiple copies.)

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