From: Yu Zhang <yu.c.zhang@linux.intel.com>
To: pbonzini@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
seanjc@google.com, vkuznets@redhat.com, wanpengli@tencent.com,
jmattson@google.com, joro@8bytes.org
Subject: Re: [PATCH] KVM: x86/MMU: Do not check unsync status for root SP.
Date: Tue, 26 Jan 2021 21:45:31 +0800 [thread overview]
Message-ID: <20210126134531.ctj326k3xwvmniwd@linux.intel.com> (raw)
In-Reply-To: <20210116002100.17339-1-yu.c.zhang@linux.intel.com>
Hi Paolo,
Any comments? Thanks!
B.R.
Yu
On Sat, Jan 16, 2021 at 08:21:00AM +0800, Yu Zhang wrote:
> In shadow page table, only leaf SPs may be marked as unsync.
> And for non-leaf SPs, we use unsync_children to keep the number
> of the unsynced children. In kvm_mmu_sync_root(), sp->unsync
> shall always be zero for the root SP, hence no need to check it.
>
> Signed-off-by: Yu Zhang <yu.c.zhang@linux.intel.com>
> ---
> arch/x86/kvm/mmu/mmu.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
> index 6d16481a..1a6bb03 100644
> --- a/arch/x86/kvm/mmu/mmu.c
> +++ b/arch/x86/kvm/mmu/mmu.c
> @@ -3412,8 +3412,7 @@ void kvm_mmu_sync_roots(struct kvm_vcpu *vcpu)
> * mmu_need_write_protect() describe what could go wrong if this
> * requirement isn't satisfied.
> */
> - if (!smp_load_acquire(&sp->unsync) &&
> - !smp_load_acquire(&sp->unsync_children))
> + if (!smp_load_acquire(&sp->unsync_children))
> return;
>
> spin_lock(&vcpu->kvm->mmu_lock);
> --
> 1.9.1
>
next prev parent reply other threads:[~2021-01-26 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 0:21 [PATCH] KVM: x86/MMU: Do not check unsync status for root SP Yu Zhang
2021-01-26 13:45 ` Yu Zhang [this message]
2021-02-05 17:50 ` 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=20210126134531.ctj326k3xwvmniwd@linux.intel.com \
--to=yu.c.zhang@linux.intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
/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