From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Yznaga <anthony.yznaga@oracle.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: 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,
x86@kernel.org, hpa@zytor.com, steven.sistare@oracle.com
Subject: Re: [PATCH 0/3] avoid unnecessary memslot rmap walks
Date: Thu, 4 Jun 2020 20:42:49 +0200 [thread overview]
Message-ID: <2d440118-4325-6f68-75e7-dd5a74c4a7eb@redhat.com> (raw)
In-Reply-To: <1591128450-11977-1-git-send-email-anthony.yznaga@oracle.com>
On 02/06/20 22:07, Anthony Yznaga wrote:
> While investigating optimizing qemu start time for large memory guests
> I found that kvm_mmu_slot_apply_flags() is walking rmaps to update
> existing sptes when creating or moving a slot but that there won't be
> any existing sptes to update and any sptes inserted once the new memslot
> is visible won't need updating. I can't find any reason for this not to
> be the case, but I've taken a more cautious approach to fixing this by
> dividing things into three patches.
>
> Anthony Yznaga (3):
> KVM: x86: remove unnecessary rmap walk of read-only memslots
> KVM: x86: avoid unnecessary rmap walks when creating/moving slots
> KVM: x86: minor code refactor and comments fixup around dirty logging
>
> arch/x86/kvm/x86.c | 106 +++++++++++++++++++++++++----------------------------
> 1 file changed, 49 insertions(+), 57 deletions(-)
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-06-04 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 20:07 Anthony Yznaga
2020-06-02 20:07 ` [PATCH 1/3] KVM: x86: remove unnecessary rmap walk of read-only memslots Anthony Yznaga
2020-06-02 20:07 ` [PATCH 2/3] KVM: x86: avoid unnecessary rmap walks when creating/moving slots Anthony Yznaga
2020-06-02 20:07 ` [PATCH 3/3] KVM: x86: minor code refactor and comments fixup around dirty logging Anthony Yznaga
2020-06-04 18:42 ` Paolo Bonzini [this message]
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=2d440118-4325-6f68-75e7-dd5a74c4a7eb@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony.yznaga@oracle.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=sean.j.christopherson@intel.com \
--cc=steven.sistare@oracle.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
all inboxes | Powered by JetHome®