From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753950AbdF0Wte (ORCPT ); Tue, 27 Jun 2017 18:49:34 -0400 Received: from mail-oi0-f53.google.com ([209.85.218.53]:36690 "EHLO mail-oi0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753461AbdF0Wt3 (ORCPT ); Tue, 27 Jun 2017 18:49:29 -0400 MIME-Version: 1.0 In-Reply-To: References: <1498528021-5115-1-git-send-email-wanpeng.li@hotmail.com> <1498528021-5115-5-git-send-email-wanpeng.li@hotmail.com> From: Wanpeng Li Date: Wed, 28 Jun 2017 06:49:28 +0800 Message-ID: Subject: Re: [PATCH v5 4/4] KVM: async_pf: Let host know whether the guest support delivery async_pf as #PF vmexit To: Paolo Bonzini Cc: "linux-kernel@vger.kernel.org" , kvm , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Wanpeng Li Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2017-06-27 21:19 GMT+08:00 Paolo Bonzini : > > > On 27/06/2017 03:47, Wanpeng Li wrote: >> - wrmsrl(MSR_KVM_ASYNC_PF_EN, pa | KVM_ASYNC_PF_ENABLED); >> + pa |= KVM_ASYNC_PF_DELIVERY_AS_PF_VMEXIT | KVM_ASYNC_PF_ENABLED; >> + wrmsr_safe(MSR_KVM_ASYNC_PF_EN, pa & 0xffffffff, pa >> 32); >> __this_cpu_write(apf_reason.enabled, 1); > > Better: > > pa |= KVM_ASYNC_PF_ENABLED; > > /* Async page fault support for L1 hypervisor is optional. */ > if (wrmsr_safe(MSR_KVM_ASYNC_PF_EN, > pa | KVM_ASYNC_PF_DELIVERY_AS_PF_VMEXIT) < 0) > wrmsrl(MSR_KVM_ASYNC_PF_EN, pa); Good point. :) Regards, Wanpeng Li