[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [v5][PATCH 0/10] xen: reserve RMRR to avoid conflicting MMIO/RAM
v5: * Add patch #2 to introduce a global count, acpi_rmrr_unit_entries. * Refine hypercall return value to make sure the caller can distinguish clearly between "xen filled in N entries" and "xen said you need N entries for all information". * Refine some structures * Then Rebase v4: * Drop the original patch #1. Instead, we use acpi_rmrr_units to get rmrr info directly. * Refine the hypercall definition to make sure we can use it safely. * Introduce introduce nr_reserved_device_memory_map in hvm_info_table, then we can avoid issue unnecessary hypercall, even we can know current RMRR entries to issue hypercall one time. * Cleanup and rebase v3: * Use XENMEM_reserved_device_memory_map to replace XENMEM_RMRR_memory_map * Then rebase all patches v2: * Don't use e820map to define RMRR maps directly to avoid any confusion. * In patch #3 we introduce construct_rmrr_e820_maps() to check if we can insert RMRR maps and then we will sort all e820 entries. * Clean patch #4 * In patch #5 we reuse check_mmio_hole() to check if current mmio range is fine to RMRR maps. If not, we just issue error to notify the user since mostly mmio should be configured again. While we work for supporting RMRR mapping for Windows GFX driver in case shared table, http://osdir.com/ml/general/2014-07/msg55347.html http://osdir.com/ml/general/2014-07/msg55348.html we realize we should reserve RMRR range to avoid any potential MMIO/RAM overlap with our discussion so here these preliminary patches are intended to cover this. ---------------------------------------------------------------- Tiejun Chen (10): xen:vtd:rmrr: export acpi_rmrr_units xen:vtd:rmrr: introduce acpi_rmrr_unit_entries xen:x86: define a new hypercall to get RMRR mappings tools:libxc: introduce hypercall for xc_reserved_device_memory_map tools:libxc: check if mmio BAR is out of RMRR mappings hvm_info_table: introduce nr_reserved_device_memory_map xen:x86:: support xc_reserved_device_memory_map in compat case tools:firmware:hvmloader: introduce hypercall for xc_reserved_device_memory_map tools:firmware:hvmloader: check to reserve RMRR mappings in e820 xen:vtd: make USB RMRR mapping safe tools/firmware/hvmloader/e820.c | 101 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ tools/firmware/hvmloader/util.c | 22 ++++++++++++++++++++++ tools/firmware/hvmloader/util.h | 11 +++++++++++ tools/libxc/xc_domain.c | 29 +++++++++++++++++++++++++++++ tools/libxc/xc_hvm_build_x86.c | 83 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-- tools/libxc/xenctrl.h | 4 ++++ xen/arch/x86/mm.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++++ xen/arch/x86/x86_64/compat/mm.c | 40 ++++++++++++++++++++++++++++++++++++++++ xen/drivers/passthrough/vtd/dmar.c | 2 ++ xen/drivers/passthrough/vtd/dmar.h | 16 +--------------- xen/drivers/passthrough/vtd/iommu.c | 8 -------- xen/drivers/passthrough/vtd/iommu.h | 1 - xen/include/asm-x86/acpi.h | 18 ++++++++++++++++++ xen/include/public/hvm/hvm_info_table.h | 3 +++ xen/include/public/memory.h | 39 ++++++++++++++++++++++++++++++++++++++- 15 files changed, 399 insertions(+), 27 deletions(-) Thanks Tiejun _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |