Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965235AbbBDCJw (ORCPT ); Tue, 3 Feb 2015 21:09:52 -0500 Received: from mail-la0-f54.google.com ([209.85.215.54]:35160 "EHLO mail-la0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753261AbbBDCJs (ORCPT ); Tue, 3 Feb 2015 21:09:48 -0500 MIME-Version: 1.0 In-Reply-To: <54D0F43E.5050206@redhat.com> References: <1422978415-2006-1-git-send-email-fanwenyi0529@gmail.com> <54D0F43E.5050206@redhat.com> From: Wincy Van Date: Wed, 4 Feb 2015 10:09:26 +0800 Message-ID: Subject: Re: [PATCH resend v5 0/6] KVM: nVMX: Enable nested apicv support To: Paolo Bonzini Cc: "gleb@kernel.org" , "Zhang, Yang Z" , Wanpeng Li , "kvm@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Jan Kiszka Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1189 Lines: 36 On Wed, Feb 4, 2015 at 12:15 AM, Paolo Bonzini wrote: > > > On 03/02/2015 16:46, Wincy Van wrote: >> v1 ---> v2: >> Use spin lock to ensure vmcs12 is safe when doing nested >> posted interrupt delivery. >> >> v2 ---> v3: >> 1. Add a new field in nested_vmx to avoid the spin lock in v2. >> 2. Drop send eoi to L1 when doing nested interrupt delivery. >> 3. Use hardware MSR bitmap to enable nested virtualize x2apic >> mode. >> >> v3 ---> v4: >> 1. Optimize nested msr bitmap merging. >> 2. Allocate nested msr bitmap only when nested == 1. >> 3. Inline the nested vmx control checking functions. >> >> v4 ---> v5: >> 1. Move EXIT_REASON_APIC_WRITE to the apic register >> virtualization patch. >> 2. Accomplish nested posted interrupts manually if >> they are not recognized by hardware. > > Thanks, will apply soon to kvm/queue. > Thanks a lot for your review, Paolo and Yang! Wincy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/