Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp9298603ybl; Wed, 25 Dec 2019 18:36:18 -0800 (PST) X-Google-Smtp-Source: APXvYqzt3Y6vKnefH4M0vnT0ccT2Q80JZtFLF0jfnCu5c1Z19BJApPA/9eEtsEstxDhnbH7LnnDI X-Received: by 2002:a05:6830:1116:: with SMTP id w22mr48934987otq.216.1577327777855; Wed, 25 Dec 2019 18:36:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577327777; cv=none; d=google.com; s=arc-20160816; b=B5NsH22qDy+qdWbLD086Hw5e+5fiyQvT02uTJu6py9cF6U9jjRg5Ggbf42f7/EufQQ 0KixrvE3x84IaxoRK+F3l1CutBPggQRMqCSPaTkWIx+j68hMBOC4lQTlLYv9U7oL/Qx9 2vArUaWRPua6PzJumdS4hf0gL6pOtYbvsyoPMzoomqtQmpBKx8p6YvBnqcr8fRvtyLmz 9IUptZ1OyeUPM/m3ibKdU8uPfhK98ncZm5GTPO/tjR8TVLx08EfAVYUmIUosYmxl/srm gVPbTbJt/zxMkKD2Z1H+i86izHJdbrT0v78Uo6Mi7d3bVb+Wj3Ry/8SR3LWKadgwDUQ0 kkMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=wFW6PwbhpwDHaE85ZcsN3eRZyhhib4+0nJ3fxwBkdbQ=; b=l2sM115+iX9rgCYIsGJyiXVkhK8yzzdEe2YRcOl//7q7eEF/6XDMmkakHHVTvR8+8w 21V11Y975cuqXjKbvi5UHTVHEX9zQQXq8trMDdOItAqOYcJKnXZRQWX5ffrWBu9Joaua D2k+RNUi3O/7YyER9iYEp/ZHsBOg/EpSG7ZScGDvcsfRw0lGgJGDwX+jnujSy7WOYzry EYTR4LATOtadqI96yN8zkXjfS3++/2cdKM60DZiFgyEoCeF8kGUETdlzHO8z1b0Oz2A5 JS3/8KZ2gAxZg0RUkWyqCapnByZDi2ARALKZHBJU+tDvwozNr3MP6spNZaPL7grsI7KB v3Rg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=s17YA35e; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h24si9724876oie.151.2019.12.25.18.36.05; Wed, 25 Dec 2019 18:36:17 -0800 (PST) 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; dkim=pass header.i=@gmail.com header.s=20161025 header.b=s17YA35e; 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; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726935AbfLZCfW (ORCPT + 99 others); Wed, 25 Dec 2019 21:35:22 -0500 Received: from mail-ot1-f66.google.com ([209.85.210.66]:44093 "EHLO mail-ot1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726885AbfLZCfW (ORCPT ); Wed, 25 Dec 2019 21:35:22 -0500 Received: by mail-ot1-f66.google.com with SMTP id h9so28265396otj.11; Wed, 25 Dec 2019 18:35:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wFW6PwbhpwDHaE85ZcsN3eRZyhhib4+0nJ3fxwBkdbQ=; b=s17YA35ez9d8oUT+5ziW2uwqnJZChzC2qjILhPLVrrr/W66l4jWJ4NtZlpatnZ7pq6 RZiXcd5CoW5OIxEcpjbLJ8M5b/EO/CUbGinvNb+HG3lqSRhHigsIFA4YhdTbgmmWNzAX 4fTRcKQD+SEFXBSz+WzxVfHxBkReFcIzvt1iP4s3xxWaGnuV/t7Z6FlvLHWzQsrKzs6V 0qjrxkspMs87NIsqAR+zCQrrIFXBogAfQ6IPBhHfJTyW31e6KV4WCVJryY8orNT4Xsy4 xzFtNagzYJ1INykIzBlMf85YX+ZGuijJ3iEUzf/hlYJy/RO2sBozaBb5Vjh1FVvNDWwo J7Tg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wFW6PwbhpwDHaE85ZcsN3eRZyhhib4+0nJ3fxwBkdbQ=; b=hAYD1/tSZruxEdLHoJnxgJ+Eam6ZRoYiuSTPl5tlz2/KVywfX1iPnd0CQUCprESKD7 0gboVF3i6ofzifTNIlU+FuB8W/EIqLZPkfLvX840BsTl8WMHa7/bDJ1u5rUzYQW+WE32 lZWUW8V1n8o/j8ZQ7Dn0kWvtYmwx53x1lQW7U8QukRFjdy49tfbgY+imuScQC0+CePlY 7dylBJrT4WGpceZgNDEX5cXsA3W9cDw+SqHsuivSs0kH71lFRrVhhiH/oxFd7ZK1uIyH q3ktxHVwfKSItzetVSgSiCz9qER/aTudALkt0hNOEyeAFxK5cV24PjggnwNKsKc09iJ1 jyYQ== X-Gm-Message-State: APjAAAXGuvcRleieqYhgjU1YrddORlJIesHuV4Rloll9yVbDKvZbLvZG G+XF+n6cv0JsqETFFPydavD35/N176h4KTfRln8= X-Received: by 2002:a9d:3f61:: with SMTP id m88mr31944549otc.56.1577327721351; Wed, 25 Dec 2019 18:35:21 -0800 (PST) MIME-Version: 1.0 References: <5744632b88b44369a68c0b0704bfb48e@huawei.com> In-Reply-To: <5744632b88b44369a68c0b0704bfb48e@huawei.com> From: Wanpeng Li Date: Thu, 26 Dec 2019 10:35:10 +0800 Message-ID: Subject: Re: [PATCH] KVM: nvmx: retry writing guest memory after page fault injected To: linmiaohe Cc: Liran Alon , "pbonzini@redhat.com" , "rkrcmar@redhat.com" , "sean.j.christopherson@intel.com" , "vkuznets@redhat.com" , "wanpengli@tencent.com" , "jmattson@google.com" , "joro@8bytes.org" , "tglx@linutronix.de" , "mingo@redhat.com" , "bp@alien8.de" , "hpa@zytor.com" , "kvm@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "x86@kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 26 Dec 2019 at 10:32, linmiaohe wrote: > > Hi, > > Liran Alon wrote: > >> On 25 Dec 2019, at 4:21, linmiaohe wrote: > >> > >> From: Miaohe Lin > >> > >> We should retry writing guest memory when > >> kvm_write_guest_virt_system() failed and page fault is injected in handle_vmread(). > >> > >> Signed-off-by: Miaohe Lin > > > >Patch fix seems correct to me: > >Reviewed-by: Liran Alon > > Thanks for your review. > > >However, I suggest to rephrase commit title & message as follows: > > > >""" > >KVM: nVMX: vmread should not set rflags to specify success in case of #PF > > > >In case writing to vmread destination operand result in a #PF, vmread should not call nested_vmx_succeed() to set rflags to specify success. Similar to as done in for VMPTRST (See handle_vmptrst()). > >""" > > Thanks for your sueestion, I would rephrase commit title & message accordingly. > > > > >In addition, it will be appreciated if you would also submit kvm-unit-test that verifies this condition. > > I'd like to submit kvm-unit-test that verifies this condition, but I am not familiar with the kvm-unit-test code yet and > also not in my recent todo list. So such a patch may come late. It would be appreciated too if you could submit this > kvm-unit-test patch. :) Hmm, did you verify your own patch? Please give the testcase.