config_tools: change MMIOResourcesConfiguration to xs:all
The "MMIO resources" section of a VM definition may contain different nodes depending on the VM load order, but the schema slicer cannot convert the complex type specifying this section because the schema requires those nodes to be a strictly-ordered sequence (by xs:sequence), not a set (by xs:all). As there is no requirement on this strict ordering, this patch converts that complex type to be an unordered set instead. Tracked-On: #6690 Signed-off-by: Junjie Mao <junjie.mao@intel.com>
This commit is contained in:
parent
3ce76a3395
commit
44f0c32735
|
@ -205,7 +205,7 @@ CLOSID 0 and the second is mapped to virtual CLOSID 1, etc.</xs:documentation>
|
|||
</xs:complexType>
|
||||
|
||||
<xs:complexType name="MMIOResourcesConfiguration">
|
||||
<xs:sequence>
|
||||
<xs:all>
|
||||
<xs:element name="TPM2" type="Boolean" default="n" minOccurs="0">
|
||||
<xs:annotation acrn:title="Trusted Platform Module passthrough" acrn:applicable-vms="pre-launched, post-launched">
|
||||
<xs:documentation>Passthrough the Trusted Platform Module (TPM2) device to this VM. (Optional) (Default value is n)</xs:documentation>
|
||||
|
@ -216,7 +216,7 @@ CLOSID 0 and the second is mapped to virtual CLOSID 1, etc.</xs:documentation>
|
|||
<xs:documentation>Passthrough the P2SB (Primary-to-Sideband) bridge register access BAR to the this VM. (Optional) (Default value is n)</xs:documentation>
|
||||
</xs:annotation>
|
||||
</xs:element>
|
||||
</xs:sequence>
|
||||
</xs:all>
|
||||
</xs:complexType>
|
||||
|
||||
<xs:complexType name="PCIDevsConfiguration">
|
||||
|
|
Loading…
Reference in New Issue