diff options
author | Radim Krčmář <rkrcmar@redhat.com> | 2016-07-12 22:09:27 +0200 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2016-07-14 09:03:57 +0200 |
commit | 3713131345fbea291cbd859d248e06ed77815962 (patch) | |
tree | fb712d5c0b49b53984a3b01d0df29c7dfee62e4e /arch/frv | |
parent | c63cf538eb4bf6a5ffd3750366d8d56f023645a5 (diff) | |
download | linux-stable-3713131345fbea291cbd859d248e06ed77815962.tar.gz linux-stable-3713131345fbea291cbd859d248e06ed77815962.tar.bz2 linux-stable-3713131345fbea291cbd859d248e06ed77815962.zip |
KVM: x86: add KVM_CAP_X2APIC_API
KVM_CAP_X2APIC_API is a capability for features related to x2APIC
enablement. KVM_X2APIC_API_32BIT_FORMAT feature can be enabled to
extend APIC ID in get/set ioctl and MSI addresses to 32 bits.
Both are needed to support x2APIC.
The feature has to be enableable and disabled by default, because
get/set ioctl shifted and truncated APIC ID to 8 bits by using a
non-standard protocol inspired by xAPIC and the change is not
backward-compatible.
Changes to MSI addresses follow the format used by interrupt remapping
unit. The upper address word, that used to be 0, contains upper 24 bits
of the LAPIC address in its upper 24 bits. Lower 8 bits are reserved as
0. Using the upper address word is not backward-compatible either as we
didn't check that userspace zeroed the word. Reserved bits are still
not explicitly checked, but non-zero data will affect LAPIC addresses,
which will cause a bug.
Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/frv')
0 files changed, 0 insertions, 0 deletions