[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH 0/3] Separate the functions of the memory_mapping and iomem_permission DOMCTLs
Hello, this patchset originates from the twelfth version of the series "Implement the XEN_DOMCTL_memory_mapping hypercall for ARM" ([1]). It includes only the last three patches, whose aim was to separate the functions of the memory_mapping and iomem_permission DOMCTLs. The memory_mapping DOMCTL's behavior, in fact, currently defaults to implicitly granting to a domain access permission to an I/O-memory range that was to be mapped in its guest address space, while a specific hypercall for granting access permissions to I/O-memory ranges exists. With respect to v12 of the original patchset, the main change concerns the use of libxl_defbool_val() to access the value of the gfx_passthru configuration option, as indicated by Ian Campbell. Also, the description of commit 0002 has been fixed in its lack of clarity pointed out by Ian Campbell. The patches have been tested on a cubieboard2, with Linux v3.15 as a dom0 and both ERIKA Enterprise ([2]) and Linux v3.15 as a domU. It has also been tested on an x86_64 machine with Linux v3.15 as both dom0 and domU. Any feedback is, as usual, welcome. Thank you, Arianna [1] http://markmail.org/thread/cx2q7vhlwuzssmzp [2] http://erika.tuxfamily.org/drupal/ Arianna Avanzini (3): tools/libxl: explicitly grant access to needed I/O-memory ranges tools/libxl: cleanup the do_pci_add() function xen/common: do not implicitly permit access to mapped I/O memory tools/libxl/libxl_create.c | 9 ++ tools/libxl/libxl_internal.h | 2 + tools/libxl/libxl_pci.c | 213 +++++++++++++++++++++++++++---------------- xen/common/domctl.c | 36 ++------ 4 files changed, 157 insertions(+), 103 deletions(-) -- 2.1.0 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |