Introduce a new KVM device that represents an ARM Interrupt Translation Service (ITS) controller. Since there can be multiple of this per guest, we can't piggy back on the existing GICv3 distributor device, but create a new type of KVM device. On the KVM_CREATE_DEVICE ioctl we allocate and initialize the ITS data structure and store the pointer in the kvm_device data. Upon an explicit init ioctl from userland (after having setup the MMIO address) we register the handlers with the kvm_io_bus framework. Any reference to an ITS thus has to go via this interface.
Showing the changes to include/uapi/linux (1 of 9 files). Show all
Unified · Split
| @@ -1077,6 +1077,8 @@ enum kvm_device_type { · 1076 unmodified lines | |||
| 1077 | #define KVM_DEV_TYPE_FLIC KVM_DEV_TYPE_FLIC | 1077 | #define KVM_DEV_TYPE_FLIC KVM_DEV_TYPE_FLIC |
| 1078 | KVM_DEV_TYPE_ARM_VGIC_V3, | 1078 | KVM_DEV_TYPE_ARM_VGIC_V3, |
| 1079 | #define KVM_DEV_TYPE_ARM_VGIC_V3 KVM_DEV_TYPE_ARM_VGIC_V3 | 1079 | #define KVM_DEV_TYPE_ARM_VGIC_V3 KVM_DEV_TYPE_ARM_VGIC_V3 |
| 1080 | KVM_DEV_TYPE_ARM_VGIC_ITS, | ||
| 1081 | #define KVM_DEV_TYPE_ARM_VGIC_ITS KVM_DEV_TYPE_ARM_VGIC_ITS | ||
| 1080 | KVM_DEV_TYPE_MAX, | 1082 | KVM_DEV_TYPE_MAX, |
| 1081 | }; | 1083 | }; |
| 1082 | 1084 | ||