Roger Pau Monné baa006f342 xen: introduce a per-arch scratch mapping ranges ... The current approach is to create foreign mappings in any unpopulated address on the memory map. This however can cause issues, as late-loaded drivers could then found their MMIO region has been stolen to be used as foreign mapping scratch space (due to the Xen drivers having started first). Add a local resource manager to the xenpv bus driver, architectures can add suitable resources to that resource manager at boot in order to be used in preference of the generic MMIO resource allocator. No functional change, as the introduced scratch mapping range is not yet populated. Sponsored by: Cloud Software Group MFC after: 1 week Reviewed by: Elliott Mitchell <ehem+freebsd@m5p.com> Differential revision: https://reviews.freebsd.org/D46122		2024-07-30 09:39:38 +02:00
..
evtchn	x86/xen: fix out of bounds access to the event channel masks on resume	2024-02-22 11:08:03 +01:00
xenbus	newbus: globally replace device_add_child(..., -1) with DEVICE_UNIT_ANY	2024-07-24 22:22:58 -06:00
xenmem
xenstore
blkif.h
error.h
evtchn.h
features.c
features.h
gntdev.h
gnttab.h	xen: add SPDX license tags to Xen headers	2023-12-15 14:59:25 +01:00
hvm.h
hypervisor.h
privcmd.h	xen: add SPDX license tags to Xen headers	2023-12-15 14:59:25 +01:00
xen_common.c
xen_intr.h
xen_pv.h
xen-os.h	xen: introduce a per-arch scratch mapping ranges	2024-07-30 09:39:38 +02:00