Skip to contentSkip to conversation

x86/pvh: declare PVH dom0 supported with caveats

PATCH Superseded Roger Pau Monne 3 participants 4 messages Jun 7, 2024 – Jun 10, 2024

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 x86/pvh: declare PVH dom0 supported with caveats

PVH dom0 is functionally very similar to PVH domU except for the domain builder and the added set of hypercalls available to it.

The main concern with declaring it "Supported" is the lack of some features when compared to classic PV dom0, hence switch it's status to supported with caveats. List the known missing features, there might be more features missing or not working as expected apart from the ones listed.

Note there's some (limited) PVH dom0 testing on both osstest and gitlab.

---
Hopefully this will attract more testing an resources to PVH dom0 in order to try to finish the missing features.

---
 CHANGELOG.md |  1 +
 SUPPORT.md   | 15 ++++++++++++++-
 2 files changed, 15 insertions(+), 1 deletion(-)
CHANGELOG.md +1 -0
index 201478aa1c0e..1778419cae64 100644
@@ -14,6 +14,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
    - HVM PIRQs are disabled by default.
    - Reduce IOMMU setup time for hardware domain.
    - Allow HVM/PVH domains to map foreign pages.
+   - Declare PVH dom0 supported with caveats.
  - xl/libxl configures vkb=[] for HVM domains with priority over vkb_device.
  - Increase the maximum number of CPUs Xen can be built for from 4095 to
    16383.
SUPPORT.md +14 -1
index d5d60c62ec11..711aacf34662 100644
@@ -161,7 +161,20 @@ Requires hardware virtualisation support (Intel VMX / AMD SVM).
 Dom0 support requires an IOMMU (Intel VT-d / AMD IOMMU).
 
     Status, domU: Supported
-    Status, dom0: Experimental
+    Status, dom0: Supported, with caveats
+
+PVH dom0 hasn't received the same test coverage as PV dom0, so it can exhibit
+unexpected behavior or issues on some hardware.
+
+At least the following features are missing on a PVH dom0:
+
+  * PCI SR-IOV and Resizable BARs.
+
+  * Native NMI forwarding (nmi=dom0 command line option).
+
+  * MCE handling.
+
+  * PCI Passthrough to any kind of domUs.
 
 ### ARM
 
Signature · 1 line
2.44.0
Acked-by on v1 1/1
#1 lore raw
Quoted 8 lines · Roger Pau Monne

PVH dom0 is functionally very similar to PVH domU except for the domain builder and the added set of hypercalls available to it.

The main concern with declaring it "Supported" is the lack of some features when compared to classic PV dom0, hence switch it's status to supported with caveats. List the known missing features, there might be more features missing or not working as expected apart from the ones listed.

Quoted 6 lines

Note there's some (limited) PVH dom0 testing on both osstest and gitlab.

---
Hopefully this will attract more testing an resources to PVH dom0 in order to try to finish the missing features.

As agreed in the XenSummit session on the topic.

#2 lore raw
In reply to Roger Pau Monne
Quoted 10 lines · Roger Pau Monne

PVH dom0 is functionally very similar to PVH domU except for the domain builder and the added set of hypercalls available to it.

The main concern with declaring it "Supported" is the lack of some features when compared to classic PV dom0, hence switch it's status to supported with caveats. List the known missing features, there might be more features missing or not working as expected apart from the ones listed.

Note there's some (limited) PVH dom0 testing on both osstest and gitlab.

Quoted 7 lines

---
Hopefully this will attract more testing an resources to PVH dom0 in order to try to finish the missing features.

---
 CHANGELOG.md |  1 +
 SUPPORT.md   | 15 ++++++++++++++-

Bah, forgot to remove the boot warning message, will send v2.

Sorry, Roger.

#3 lore raw
In reply to Roger Pau Monne
Quoted 12 lines · Roger Pau Monne

PVH dom0 is functionally very similar to PVH domU except for the domain
builder and the added set of hypercalls available to it.

The main concern with declaring it "Supported" is the lack of some features
when compared to classic PV dom0, hence switch it's status to supported with
caveats.  List the known missing features, there might be more features missing
or not working as expected apart from the ones listed.

Quoted 4 lines

Note there's some (limited) PVH dom0 testing on both osstest and gitlab.

~ Oleksii

Quoted 52 lines

---
Hopefully this will attract more testing an resources to PVH dom0 in order to
try to finish the missing features.
---
 CHANGELOG.md |  1 +
 SUPPORT.md   | 15 ++++++++++++++-

 2 files changed, 15 insertions(+), 1 deletion(-)
CHANGELOG.md +0 -0
index 201478aa1c0e..1778419cae64 100644
@@ -14,6 +14,7 @@ The format is based on [Keep a
 Changelog](https://keepachangelog.com/en/1.0.0/)

    - HVM PIRQs are disabled by default.
    - Reduce IOMMU setup time for hardware domain.
    - Allow HVM/PVH domains to map foreign pages.
+   - Declare PVH dom0 supported with caveats.
  - xl/libxl configures vkb=[] for HVM domains with priority over vkb_device.
  - Increase the maximum number of CPUs Xen can be built for from 4095 to
    16383.

SUPPORT.md +0 -0
index d5d60c62ec11..711aacf34662 100644
@@ -161,7 +161,20 @@ Requires hardware virtualisation support (Intel

VMX / AMD SVM).
 Dom0 support requires an IOMMU (Intel VT-d / AMD IOMMU).
     Status, domU: Supported
-    Status, dom0: Experimental
+    Status, dom0: Supported, with caveats

SUPPORT.md +2 -0
+
+PVH dom0 hasn't received the same test coverage as PV dom0, so it

can exhibit

SUPPORT.md +11 -0
+unexpected behavior or issues on some hardware.
+
+At least the following features are missing on a PVH dom0:
+
+  * PCI SR-IOV and Resizable BARs.
+
+  * Native NMI forwarding (nmi=dom0 command line option).
+
+  * MCE handling.
+
+  * PCI Passthrough to any kind of domUs.


 ### ARM