> I think we shouldn't read it like that. It seems that KVM is always
> returning the VAPIC capability except when the CPU is providing a
> special acceleration [0].
>
> I would say you can't really refer yourself at this bit to enable or
> not kvmapic in QEMU.
>
> Does that make sense?
>
> [0
On Thu, Apr 06, 2017 at 06:18:33PM +, Xu, Anthony wrote:
> > > --- a/kvm-all.c
> > > +++ b/kvm-all.c
> > > @@ -2232,6 +2232,10 @@ int kvm_has_sync_mmu(void)
> > > return kvm_check_extension(kvm_state, KVM_CAP_SYNC_MMU);
> > > }
> > >
> > > +int kvm_has_vapic(void){
> > > +return !kvm_
> > --- a/kvm-all.c
> > +++ b/kvm-all.c
> > @@ -2232,6 +2232,10 @@ int kvm_has_sync_mmu(void)
> > return kvm_check_extension(kvm_state, KVM_CAP_SYNC_MMU);
> > }
> >
> > +int kvm_has_vapic(void){
> > +return !kvm_check_extension(kvm_state, KVM_CAP_VAPIC);
> > +}
> > +
>
> Is that function
On Wed, Apr 05, 2017 at 12:52:25AM +, Xu, Anthony wrote:
> In KVM mode, enable kvmvapic only when host doesn't support
> VAPIC capability.
>
> Save the time to set up kvmvapic in some hosts.
>
>
> Signed-off -by: Anthony Xu
>
s/Signed-off -by/Signed-off-by
nit: I think we do prefer a sin
In KVM mode, enable kvmvapic only when host doesn't support
VAPIC capability.
Save the time to set up kvmvapic in some hosts.
Signed-off -by: Anthony Xu
diff --git a/hw/intc/apic_common.c b/hw/intc/apic_common.c
index c3829e3..d5c53af 100644
--- a/hw/intc/apic_common.c
+++ b/hw/intc/apic_com
