Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
Documentation: KVM: Introduce documentation for VGICv5
Now that it is possible to create a VGICv5 device, provide initial
documentation for it. At this stage, there is little to document.
Signed-off-by: Sascha Bischoff <sascha.bischoff@arm.com>
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Link: https://patch.msgid.link/20260319154937.3619520-39-sascha.bischoff@arm.com
Signed-off-by: Marc Zyngier <maz@kernel.org>
authored by
Sascha Bischoff
and committed by
Marc Zyngier
eb3c4d2c
9b7aa055
+38
+37
Documentation/virt/kvm/devices/arm-vgic-v5.rst
+37
Documentation/virt/kvm/devices/arm-vgic-v5.rst
···
1
+
.. SPDX-License-Identifier: GPL-2.0
2
+
3
+
====================================================
4
+
ARM Virtual Generic Interrupt Controller v5 (VGICv5)
5
+
====================================================
6
+
7
+
8
+
Device types supported:
9
+
- KVM_DEV_TYPE_ARM_VGIC_V5 ARM Generic Interrupt Controller v5.0
10
+
11
+
Only one VGIC instance may be instantiated through this API. The created VGIC
12
+
will act as the VM interrupt controller, requiring emulated user-space devices
13
+
to inject interrupts to the VGIC instead of directly to CPUs.
14
+
15
+
Creating a guest GICv5 device requires a host GICv5 host. The current VGICv5
16
+
device only supports PPI interrupts. These can either be injected from emulated
17
+
in-kernel devices (such as the Arch Timer, or PMU), or via the KVM_IRQ_LINE
18
+
ioctl.
19
+
20
+
Groups:
21
+
KVM_DEV_ARM_VGIC_GRP_CTRL
22
+
Attributes:
23
+
24
+
KVM_DEV_ARM_VGIC_CTRL_INIT
25
+
request the initialization of the VGIC, no additional parameter in
26
+
kvm_device_attr.addr. Must be called after all VCPUs have been created.
27
+
28
+
Errors:
29
+
30
+
======= ========================================================
31
+
-ENXIO VGIC not properly configured as required prior to calling
32
+
this attribute
33
+
-ENODEV no online VCPU
34
+
-ENOMEM memory shortage when allocating vgic internal data
35
+
-EFAULT Invalid guest ram access
36
+
-EBUSY One or more VCPUS are running
37
+
======= ========================================================