From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] KVM: x86: MMU changes for 6.9
Date: Thu, 14 Mar 2024 11:38:08 -0700 [thread overview]
Message-ID: <ZfNEEFmTkx-RVuix@google.com> (raw)
In-Reply-To: <CABgObfa3By9GU9_8FmqHQK-AxWU3ocbBkQK0xXwx2XRDP828dg@mail.gmail.com>
On Thu, Mar 14, 2024, Paolo Bonzini wrote:
> On Fri, Mar 8, 2024 at 11:37 PM Sean Christopherson <seanjc@google.com> wrote:
> >
> > - Zap TDP MMU roots at 4KiB granularity to minimize the delay in yielding if
> > a reschedule is needed, e.g. if a high priority task needs to run. Because
> > KVM doesn't support yielding in the middle of processing a zapped non-leaf
> > SPTE, zapping at 1GiB granularity can result in multi-millisecond lag when
> > attempting to schedule in a high priority.
> >
>
> Would 2 MiB provide a nice middle ground?
Not really?
Zapping at 2MiB definitely fixes the worst of the tail latencies, but there is
still a measurable difference between 2MiB and 4KiB. And on the other side of the
coing, I was unable to observe a meaningful difference in total runtime by zapping
at 2MiB, or even 1GiB, versus 4KiB.
In other words, AFAICT, there's no need to shoot for a middle ground because trying
to zap at larger granularities doesn't buy us anything.
next prev parent reply other threads:[~2024-03-14 18:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 22:36 [GIT PULL] KVM: x86 pull requests for 6.9 Sean Christopherson
2024-03-08 22:36 ` [GIT PULL] KVM: Async #PF changes " Sean Christopherson
2024-03-11 14:23 ` Paolo Bonzini
2024-03-08 22:36 ` [GIT PULL] KVM: Common MMU " Sean Christopherson
2024-03-11 14:23 ` Paolo Bonzini
2024-03-08 22:36 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2024-03-11 14:28 ` Paolo Bonzini
2024-03-08 22:36 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2024-03-11 14:30 ` Paolo Bonzini
2024-03-14 18:31 ` Paolo Bonzini
2024-03-14 18:38 ` Sean Christopherson [this message]
2024-03-14 18:43 ` Paolo Bonzini
2024-03-08 22:36 ` [GIT PULL] KVM: x86: PMU " Sean Christopherson
2024-03-11 14:40 ` Paolo Bonzini
2024-03-08 22:36 ` [GIT PULL] KVM: x86: Selftests " Sean Christopherson
2024-03-11 14:21 ` Paolo Bonzini
2024-03-11 14:35 ` Paolo Bonzini
2024-03-12 23:00 ` Sean Christopherson
2024-03-14 18:40 ` Sean Christopherson
2024-03-08 22:37 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2024-03-11 14:42 ` Paolo Bonzini
2024-03-08 22:37 ` [GIT PULL] KVM: Xen and gfn_to_pfn_cache " Sean Christopherson
2024-03-11 14:02 ` Janosch Frank
2024-03-11 14:43 ` Paolo Bonzini
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=ZfNEEFmTkx-RVuix@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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;
as well as URLs for NNTP newsgroup(s).