There are some differences in how L1VH partitions must map stats and vp state pages, some of which are due to differences across hypervisor versions. Detect and handle these cases.
Patch 1: Fix for the logic of when to map the vp stats page. Patch 2: Compatibility fix for configurations where hypervisor does not provide a "PARENT" stats area, only "SELF". Fall back to just using "SELF". Patches 3-6: On newer hypervisors L1VH partitions must allocate and free stats and vp state pages, and use a new hypercall HVCALL_MAP_VP_STATS_PAGE2 to map the stats page. Add HVCALL_GET_PARTITION_PROPERTY_EX to query a feature bit to determine whether to allocate the pages and use the new stats hypercall. Jinank Jain (2): mshv: Allocate vp state page for HVCALL_MAP_VP_STATE_PAGE on L1VH mshv: Introduce new hypercall to map stats page for L1VH partitions Nuno Das Neves (1): mshv: Only map vp->vp_stats_pages if on root scheduler Purna Pavan Chandra Aekkaladevi (3): mshv: Ignore second stats page map result failure mshv: Add the HVCALL_GET_PARTITION_PROPERTY_EX hypercall mshv: Get the vmm capabilities offered by the hypervisor drivers/hv/mshv_root.h | 24 ++-- drivers/hv/mshv_root_hv_call.c | 227 ++++++++++++++++++++++++++++++--- drivers/hv/mshv_root_main.c | 140 ++++++++++++-------- include/hyperv/hvgdk_mini.h | 2 + include/hyperv/hvhdk.h | 40 ++++++ include/hyperv/hvhdk_mini.h | 33 +++++ 6 files changed, 390 insertions(+), 76 deletions(-) -- 2.34.1
