Home
last modified time | relevance | path

Searched hist:a92e2543d6a8653a8ab45cf5df7ef07dafcf3f3e (Results 1 – 3 of 3) sorted by relevance

/openbmc/linux/arch/x86/kvm/
H A Dlapic.hdiff a92e2543d6a8653a8ab45cf5df7ef07dafcf3f3e Tue Jul 12 15:09:22 CDT 2016 Radim Krčmář <rkrcmar@redhat.com> KVM: x86: use hardware-compatible format for APIC ID register

We currently always shift APIC ID as if APIC was in xAPIC mode.
x2APIC mode wants to use more bits and storing a hardware-compabible
value is the the sanest option.

KVM API to set the lapic expects that bottom 8 bits of APIC ID are in
top 8 bits of APIC_ID register, so the register needs to be shifted in
x2APIC mode.

Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
H A Dlapic.cdiff a92e2543d6a8653a8ab45cf5df7ef07dafcf3f3e Tue Jul 12 15:09:22 CDT 2016 Radim Krčmář <rkrcmar@redhat.com> KVM: x86: use hardware-compatible format for APIC ID register

We currently always shift APIC ID as if APIC was in xAPIC mode.
x2APIC mode wants to use more bits and storing a hardware-compabible
value is the the sanest option.

KVM API to set the lapic expects that bottom 8 bits of APIC ID are in
top 8 bits of APIC_ID register, so the register needs to be shifted in
x2APIC mode.

Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
H A Dx86.cdiff a92e2543d6a8653a8ab45cf5df7ef07dafcf3f3e Tue Jul 12 15:09:22 CDT 2016 Radim Krčmář <rkrcmar@redhat.com> KVM: x86: use hardware-compatible format for APIC ID register

We currently always shift APIC ID as if APIC was in xAPIC mode.
x2APIC mode wants to use more bits and storing a hardware-compabible
value is the the sanest option.

KVM API to set the lapic expects that bottom 8 bits of APIC ID are in
top 8 bits of APIC_ID register, so the register needs to be shifted in
x2APIC mode.

Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>