From nobody Tue Apr 30 05:39:27 2024
Delivered-To: importer@patchew.org
Received-SPF: pass (zohomail.com: domain of redhat.com designates
63.128.21.124 as permitted sender) client-ip=63.128.21.124;
envelope-from=libvir-list-bounces@redhat.com;
helo=us-smtp-delivery-124.mimecast.com;
Authentication-Results: mx.zohomail.com;
spf=pass (zohomail.com: domain of redhat.com designates 63.128.21.124 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
dmarc=fail(p=none dis=none) header.from=linux.ibm.com
ARC-Seal: i=1; a=rsa-sha256; t=1605031784; cv=none;
d=zohomail.com; s=zohoarc;
b=NLZxbN0wdlHDErWkit1DcmD1gTmAVaohLuh/DE0Yo1j8yYi0Brl3OhBYEFQYen79Tq1/6BI/ruyXoA2mirAygHkbHpwBsikuNOGL8T/vN3Djfnx50HOEGuWTc3FnTkZJn8wfaED5CtrZomLh+EK018XDpKFX77B/UKr8YY2qY+U=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com;
s=zohoarc;
t=1605031784;
h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To;
bh=ZnpRo2sF29NmHq5TBB2K2x5ts2DitCcr0nnmm8UlF5w=;
b=Z43GeFIZHi0vPw8gOR0mgAbiDb3g1Jw1RY8nKF+6GbsO50frywX5djk3SE+q9L8c0YFR3YzZGyy/E99JShHj8CqVTtYs6f4Ia1FUgEDVRiMUJ65dhFGQ4uC2s5f/rM8IsLwNHdGF4wnV2qgaY1/oygO/BHUyyhoDmHSttWhx3o8=
ARC-Authentication-Results: i=1; mx.zohomail.com;
spf=pass (zohomail.com: domain of redhat.com designates 63.128.21.124 as
permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com;
dmarc=fail header.from=
+ PCI devices can be capable of
+ creating mediated devices.
+ If they are capable the attribute mdev_types
type
- elements, which list all mdev types supported on the
- physical device. Since 3.4.0
- Each type
element has a single id=
code>
- attribute that holds an official vendor-supplied ident=
ifier
- for the type. It supports the following sub-elements:
-
-
- name
name
element holds a vendor-sup=
plied
- code name for the given mediated device type. Th=
is is
- an optional element.
- deviceAPI
availableInstances
mdev_types capability
+
+ type
of the
+ element capability
is mdev_types
.
+ This capability will contain a list of type
+ elements, which list all mdev types supported on the
+ physical device. Since 3.4.0
+ Each type
element has a single id
+ attribute that holds an official vendor-supplied identifier
+ for the type. It supports the following sub-elements:
+
+
+ name
name
element holds a vendor-supplied
+ code name for the given mediated device type. This is
+ an optional element.
+ deviceAPI
availableInstances
The following are some example node device XML outputs:
--=20 2.26.2 From nobody Tue Apr 30 05:39:27 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 63.128.21.124 as permitted sender) client-ip=63.128.21.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; spf=pass (zohomail.com: domain of redhat.com designates 63.128.21.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=fail(p=none dis=none) header.from=linux.ibm.com ARC-Seal: i=1; a=rsa-sha256; t=1605031786; cv=none; d=zohomail.com; s=zohoarc; b=P0C6NE1lB8vpX7yAQEuJLWyr6+7gxBNR2Uwdjmi7yqjPCFXI7LOiwhqTZlXlAcl9ek/0lMIfN9H4WYNHg5dlte/yVFFddbPhkf52tUYkEs9VlrTW00Hq2Z2EHCkPDS5TKyMeHFLgfX2WNQE8Y4up4INL9EAMPrxE4LftjFX/nho= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1605031786; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=HRLqvMPDqWPcZbAYK4LCCQLgVEbrsnBSXf7DPBVneWE=; b=XFPvSJYXkZLmzEVlLFnoy3kfXUt3hL7jTL2p6+IQlLlMwtQBHnK2v6CPPXiPC3PPmu8xyenlysTaclxhGu1XU6zDxl5cnYiyASCncQIfdAXWs6YjvagnEwoMJgaoMAs8mkhEof6zE6JRmCrCwh/BausGApnF5IY8L3FNLB6bUGU= ARC-Authentication-Results: i=1; mx.zohomail.com; spf=pass (zohomail.com: domain of redhat.com designates 63.128.21.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=fail header.from=
- A PCI device capable of creating mediated devices will include a nes=
ted
+ A device capable of creating mediated devices will include a nested
capability mdev_types
which enumerates all supported md=
ev
types on the physical device, along with the type attributes availab=
le
through sysfs. A detailed description of the XML format for the
mdev_types
capability can be found
- here.
+ here for PCI or
+ here for CSS.
The following example shows how we might represent an NVIDIA GPU dev= ice diff --git a/docs/formatnode.html.in b/docs/formatnode.html.in index bd3112c5a8..d9abba0efa 100644 --- a/docs/formatnode.html.in +++ b/docs/formatnode.html.in @@ -405,6 +405,21 @@
devno
capability
type
attribute
+ which will be set to:
+ mdev_types
vdpa
- PCI devices can be capable of
- creating mediated devices.
+ PCI and CSS
+ devices can be capable of creating mediated devices.
If they are capable the attribute type
of the
element capability
is mdev_types
.
This capability will contain a list of type
diff --git a/docs/schemas/nodedev.rng b/docs/schemas/nodedev.rng
index 231afa0218..b3e986659e 100644
--- a/docs/schemas/nodedev.rng
+++ b/docs/schemas/nodedev.rng
@@ -654,6 +654,9 @@