From: linmiaohe <linmiaohe@huawei.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
"wanpengli@tencent.com" <wanpengli@tencent.com>,
"jmattson@google.com" <jmattson@google.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>, "hpa@zytor.com" <hpa@zytor.com>
Subject: Re: [PATCH] KVM: nVMX: Fix some comment typos and coding style
Date: Fri, 7 Feb 2020 04:05:36 +0000 [thread overview]
Message-ID: <bc72431b89444fa3a127cf71065f71db@huawei.com> (raw)
Hi:
Sean Christopherson <sean.j.christopherson@intel.com> wrote:
> On Thu, Feb 06, 2020 at 12:32:38PM +0100, Vitaly Kuznetsov wrote:
>> linmiaohe <linmiaohe@huawei.com> writes:
>>
>>
>> I have to admit that shadow MMU in KVM is not my strong side but this
>> comment reads weird, I'd appreciate if someone could suggest a better
>> alternative.
>
> /* One off flag for a stupid corner case in shadow paging. */
>>
>> > */
>
> /*
> * Indicates the guest is trying to write a gfn that contains one or
> * more of the PTEs used to translate the write itself, i.e. the access
> * is changing its own translation in the guest page tables. KVM exits
> * to userspace if emulation of the faulting instruction fails and this
> * flag is set, as KVM cannot make forward progress.
> *
> * If emulation fails for a write to guest page tables, KVM unprotects
> * (zaps) the shadow page for the target gfn and resumes the guest to
> * retry the non-emulatable instruction (on hardware). Unprotecting the
> * gfn doesn't allow forward progress for a self-changing access because
> * doing so also zaps the translation for the gfn, i.e. retrying the
> * instruction will hit a !PRESENT fault, which results in a new shadow
> * page and sends KVM back to square one.
> */
>> > bool write_fault_to_shadow_pgtable;
Thanks for your detail comment. This field confused me once.
Thanks to both for review! Will send v2.
next reply other threads:[~2020-02-07 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 4:05 linmiaohe [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-06 2:29 [PATCH] KVM: nVMX: Fix some comment typos and coding style linmiaohe
2020-02-06 11:32 ` Vitaly Kuznetsov
2020-02-06 15:35 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bc72431b89444fa3a127cf71065f71db@huawei.com \
--to=linmiaohe@huawei.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox