[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH v3 0/3] Qemu: add Xen vIOMMU interrupt remapping function support
This patchset is to deal with MSI interrupt remapping request when guest updates MSI registers. In case of conflicts, this series also can be found in my personal github: Xen: https://github.com/gc1008/viommu_xen.git vIOMMU4 Qemu: https://github.com/gc1008/viommu_qemu.git vIOMMU3 Any comments would be highly appreciated. And below is the change histroy Changes from v2: In last version, a new interface is used for binding a guest remappable msi with a physical interrupt, while the old interface is used for binding non-remappable msi. But for AMD, only from the MSI message itself, the interrupt format cannot be infered. To address this, we decide to pass the whole guest msi message to Xen and let vIOMMUs in Xen detemine whether an given interrupt is remappable or not. So the following changes are made: - Instead of introducing a new interface for binding remapping format msi, the exist interface is modified to support msi of both format. - In patch 3, define MSI_ADDR_IF_MASK inside a function because it is intel-specific. It is improper to define it in a common header. Chao Gao (3): i386/msi: Correct mask of destination ID in MSI address xen/pt: Pass the whole msi addr/data to Xen msi: Handle remappable format interrupt request hw/i386/xen/xen-hvm.c | 10 ++++++++- hw/pci/msi.c | 5 +++-- hw/pci/msix.c | 4 +++- hw/xen/xen_pt_msi.c | 49 ++++++++++++------------------------------- include/hw/i386/apic-msidef.h | 2 +- include/hw/xen/xen.h | 2 +- stubs/xen-hvm.c | 2 +- 7 files changed, 31 insertions(+), 43 deletions(-) -- 1.8.3.1 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |