diff options
| author | Christoffer Dall <christoffer.dall@arm.com> | 2019-10-11 13:07:06 +0200 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2019-10-21 18:59:51 +0100 |
| commit | da345174ceca052469e4775e4ae263b5f27a9355 (patch) | |
| tree | ff6d547063fac8b6e847edd70a987dfbb965d613 /virt | |
| parent | c726200dd106d4c58a281eea7159b8ba28a4ab34 (diff) | |
| download | linux-da345174ceca052469e4775e4ae263b5f27a9355.tar.gz linux-da345174ceca052469e4775e4ae263b5f27a9355.tar.bz2 linux-da345174ceca052469e4775e4ae263b5f27a9355.zip | |
KVM: arm/arm64: Allow user injection of external data aborts
In some scenarios, such as buggy guest or incorrect configuration of the
VMM and firmware description data, userspace will detect a memory access
to a portion of the IPA, which is not mapped to any MMIO region.
For this purpose, the appropriate action is to inject an external abort
to the guest. The kernel already has functionality to inject an
external abort, but we need to wire up a signal from user space that
lets user space tell the kernel to do this.
It turns out, we already have the set event functionality which we can
perfectly reuse for this.
Signed-off-by: Christoffer Dall <christoffer.dall@arm.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'virt')
| -rw-r--r-- | virt/kvm/arm/arm.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/virt/kvm/arm/arm.c b/virt/kvm/arm/arm.c index e6d56f60e4b6..12064780f1d8 100644 --- a/virt/kvm/arm/arm.c +++ b/virt/kvm/arm/arm.c @@ -218,6 +218,7 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext) case KVM_CAP_VCPU_EVENTS: case KVM_CAP_ARM_IRQ_LINE_LAYOUT_2: case KVM_CAP_ARM_NISV_TO_USER: + case KVM_CAP_ARM_INJECT_EXT_DABT: r = 1; break; case KVM_CAP_ARM_SET_DEVICE_ADDR: |