Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp427852imm; Tue, 9 Oct 2018 21:23:33 -0700 (PDT) X-Google-Smtp-Source: ACcGV61KFCQ+U7aGpcPlLaU1rdXMKjl/G2TsQ3mgqzoI32uxnX/P4Fy8weweE9gAITSDs3G1wH2a X-Received: by 2002:a17:902:3181:: with SMTP id x1-v6mr30847464plb.71.1539145413294; Tue, 09 Oct 2018 21:23:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539145413; cv=none; d=google.com; s=arc-20160816; b=FsDNYD1XtJdZl+ZflCqvAh434e2AEZL88lZ2Xop7F0PjhFvsBmZMrwqWUjKuJpDNwR qB3suJdBvVBkS0PzrVdtnEp2eoOYfUxQwfncdgJMBAlQ7hjL5336A/bCrx2FMtxczKi/ o8UbaWGRzi+81pyj2EhfICKdDteIoTAU8mfkFPOpv/oXt8QMxHyrbOoWTM+5MZ1+V5qp TtPzz2R8F03MKuO/R3bDfubjv50tnD+a6IEioeR+qKbXJTCjAIABnab1biomtOxIWjOq ipq6HYZvLzv5jGgUote6dfBwK9HLWwQIFlZASYv6FSxmmp5ZxtypDsU12bbv1FcBGjYD yf7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject; bh=78QfvvBAsD52Kug1hFbyhFcniuNasX04K+lmdqnWUPY=; b=BrOG97YJy7ErbwMRDQvVxv5Ba0xzvWYRQxulA9w/Ijf8I1g4tgXWBrguBYHIfB07fT RgA1OZNSvrNuHs9opskLnm1Oomzez69jIFDhy6jkb4i1zVaYWo2XW/YfZd4EkEbZByOL /M7RJ+nax4nN3J+6GRpg8jCiDdoC12hi5RUpqfnNdtCsfx948kAaq4Jj6j56bFJjP/H7 2PooTQfqap7Ljlytu7QIVxYn7KPSVpp16jNQ4ElquS2OpnZkKVJhtQsBHOY3fV7KxTF4 udkhqUvC6pW0SgPEHSEH4g920ILb2cGesLhO44Yb7OnhDsRjVeljNCseYwzaALV1tCz/ KCBQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r144-v6si29252421pfr.100.2018.10.09.21.23.18; Tue, 09 Oct 2018 21:23:33 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727051AbeJJLm7 (ORCPT + 99 others); Wed, 10 Oct 2018 07:42:59 -0400 Received: from szxga06-in.huawei.com ([45.249.212.32]:56401 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725860AbeJJLm7 (ORCPT ); Wed, 10 Oct 2018 07:42:59 -0400 Received: from DGGEMS412-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id 01944186D29EE; Wed, 10 Oct 2018 12:22:43 +0800 (CST) Received: from [127.0.0.1] (10.142.68.147) by DGGEMS412-HUB.china.huawei.com (10.3.19.212) with Microsoft SMTP Server id 14.3.399.0; Wed, 10 Oct 2018 12:22:42 +0800 Subject: Re: [PATCH v2 2/2] arm/arm64: KVM: enable 32 bits kvm vcpu events support To: Suzuki K Poulose , , , , , , , , , References: <1539002088-21215-1-git-send-email-gengdongjiu@huawei.com> <1539002088-21215-3-git-send-email-gengdongjiu@huawei.com> <3e6a7a5f-3ff9-b7db-b1f6-87a8fdf5c20c@arm.com> From: gengdongjiu Message-ID: Date: Wed, 10 Oct 2018 12:22:40 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <3e6a7a5f-3ff9-b7db-b1f6-87a8fdf5c20c@arm.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 8bit X-Originating-IP: [10.142.68.147] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Suzuki On 2018/10/10 1:22, Suzuki K Poulose wrote: > > > On 08/10/18 13:34, Dongjiu Geng wrote: >> The commit 539aee0edb9f ("KVM: arm64: Share the parts of >> get/set events useful to 32bit") shares the get/set events >> helper for arm64 and arm32, it is better also share the check >> for vcpu events capability to enable 32 bit kvm vcpu events >> support. >> >> User space will check whether KVM supports vcpu events through >> KVM_CAP_VCPU_EVENTS IOCTL. > > nit: User space will check whether KVM supports vcpu events by checking > the KVM_CAP_VCPU_EVENTS extension. Thanks for the pointing out, I will update it. > >> >> Cc: James Morse >> Signed-off-by: Dongjiu Geng > > Reviewed-by : Suzuki K Poulose > >> --- >> For the 32 bits kvm migration, it needs to enable the vcpu events, >> this patch will enable it. The user space QEMU patch is here: >> https://patchwork.ozlabs.org/patch/975615/ >> --- >>   arch/arm64/kvm/reset.c | 1 - >>   virt/kvm/arm/arm.c     | 1 + >>   2 files changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/arch/arm64/kvm/reset.c b/arch/arm64/kvm/reset.c >> index fd37c53..e50245e 100644 >> --- a/arch/arm64/kvm/reset.c >> +++ b/arch/arm64/kvm/reset.c >> @@ -82,7 +82,6 @@ int kvm_arch_vm_ioctl_check_extension(struct kvm *kvm, long ext) >>           break; >>       case KVM_CAP_SET_GUEST_DEBUG: >>       case KVM_CAP_VCPU_ATTRIBUTES: >> -    case KVM_CAP_VCPU_EVENTS: >>           r = 1; >>           break; >>       default: >> diff --git a/virt/kvm/arm/arm.c b/virt/kvm/arm/arm.c >> index 40e79ea..64e5d97 100644 >> --- a/virt/kvm/arm/arm.c >> +++ b/virt/kvm/arm/arm.c >> @@ -212,6 +212,7 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext) >>       case KVM_CAP_READONLY_MEM: >>       case KVM_CAP_MP_STATE: >>       case KVM_CAP_IMMEDIATE_EXIT: >> +    case KVM_CAP_VCPU_EVENTS: >>           r = 1; >>           break; >>       case KVM_CAP_ARM_SET_DEVICE_ADDR: >> > > . >