From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH] KVM: add KVM_CAP_VMX_APICV to advertise hardware apic-v support Date: Thu, 11 Dec 2014 12:48:44 +0100 Message-ID: <5489849C.4010308@redhat.com> References: <1418285221-14256-1-git-send-email-zhang.zhanghailiang@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: gleb@kernel.org, peter.huangpeng@huawei.com To: zhanghailiang , kvm@vger.kernel.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:43987 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750854AbaLKLs4 (ORCPT ); Thu, 11 Dec 2014 06:48:56 -0500 In-Reply-To: <1418285221-14256-1-git-send-email-zhang.zhanghailiang@huawei.com> Sender: kvm-owner@vger.kernel.org List-ID: On 11/12/2014 09:07, zhanghailiang wrote: > User space (i.e. QEMU) should be able to check whether KVM > supports apic-v. User space will use this to decide whether enable > emulated MSR-based APIC (i.e. hyperv-vapic). Did you see an improvement in some workload? I think it's a Windows bug---it should prefer x2apic to hv-vapic if both are available. Paolo