[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH 0/6] IOMMU, vtd and iotlb flush rework
In one of my previous email I detailed a bug I was seeing when passing through a Intel GPU on a guest that has more that 4G or RAM. Allen suggested that I go for the Plan B but after a discussion with Tim we agreed that Plan B was way to disruptive in term of code change. This patch series implements Plan A. http://xen.1045712.n5.nabble.com/VTD-Intel-iommu-IOTLB-flush-really-slow-td4952866.html Jean Guyader (6): vtd: Refactor iotlb flush code iommu: Introduce iommu_flush and iommu_flush_all. add_to_physmap: Move the code for XENMEM_add_to_physmap. mm: Add new map space for add_to_physmap, XENMAPSPACE_gmfn_range. hvmloader: Change memory relocation loop when overlap with PCI hole. Introduce domain flag (dont_flush_iotlb) to avoid unnecessary iotlb flush. tools/firmware/hvmloader/pci.c | 20 +++- xen/arch/x86/mm.c | 197 ++++++++++++++++++++--------------- xen/drivers/passthrough/iommu.c | 26 +++++ xen/drivers/passthrough/vtd/iommu.c | 100 ++++++++++-------- xen/include/public/memory.h | 4 + xen/include/xen/iommu.h | 5 + xen/include/xen/sched.h | 1 + 7 files changed, 222 insertions(+), 131 deletions(-) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |