xen: fetch dom0 video console information from XenIt's possible for Xen to switch the video mode set by the boot loader,so that the information passed in the kernel metadata is no longervalid. F
xen: fetch dom0 video console information from XenIt's possible for Xen to switch the video mode set by the boot loader,so that the information passed in the kernel metadata is no longervalid. Fetch the video mode used by Xen using an hypercall and updatethe medatada for the kernel to use the correct video mode.Sponsored by: Citrix Systems R&D
show more ...
xen/acpi: upload Cx and Px data to XenWhen FreeBSD is running as dom0 (initial domain) on a Xen system ithas access to the native ACPI tables and is the OSPM. However thehypervisor is the entity
xen/acpi: upload Cx and Px data to XenWhen FreeBSD is running as dom0 (initial domain) on a Xen system ithas access to the native ACPI tables and is the OSPM. However thehypervisor is the entity in charge of the CPU idle and frequencystates, and in order to perform this duty it requires informationfound the ACPI dynamic tables that can only be parsed by the OSPM.Introduce a new Xen specific ACPI driver to fetch the Processorrelated information and upload it to Xen. Note that this driver needsto take precedence over the generic ACPI CPU driver when running asdom0, so downgrade the probe score of the native driver toBUS_PROBE_DEFAULT in order for the Xen specific driver to useBUS_PROBE_SPECIFIC.Tested on an Intel NUC to successfully parse and upload both the Cx andPx states to Xen.Sponsored by: Citrix Systems R&DReviewed by: jhb kibDifferential revision: https://reviews.freebsd.org/D34841
xen: import Xen 4.16 public headers in sys/contrib/The current path of the Xen headers at /sys/xen/interface/ is notcorrect, as those headers are imported verbatim from the Xen sourcesand shouldn
xen: import Xen 4.16 public headers in sys/contrib/The current path of the Xen headers at /sys/xen/interface/ is notcorrect, as those headers are imported verbatim from the Xen sourcesand shouldn't be modified, as any modifications would be lost when anew version is imported.Changes to the public headers must be first done in Xen upstream sothat they can be backported and new imports will already carry them.Import Xen 4.16 headers in sys/contrib/xen/. It's unlikely that wewill import different Xen code, so don't place them inside of anysubdirectory. If in the future other pieces of Xen code need to beimported the headers will need to move into an include/ subdirectory.Note that this commit does not yet modify the include path to use thenewly imported headers.Sponsored by: Citrix Systems R&D