From: Sean Christopherson <seanjc@google.com>
To: "Shahin, Md Shahadat Hossain" <shahinmd@amazon.de>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Szczepanek, Bartosz" <bsz@amazon.de>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"bgardon@google.com" <bgardon@google.com>
Subject: Re: Subject: [RFC PATCH] kvm/x86: Fix 'lpages' kvm stat for TDM MMU
Date: Thu, 29 Apr 2021 16:49:13 +0000 [thread overview]
Message-ID: <YIrjiXja3/5e6frs@google.com> (raw)
In-Reply-To: <1619700409955.15104@amazon.de>
On Thu, Apr 29, 2021, Shahin, Md Shahadat Hossain wrote:
> Large pages not being created properly may result in increased memory
> access time. The 'lpages' kvm stat used to keep track of the current
> number of large pages in the system, but with TDP MMU enabled the stat
> is not showing the correct number.
>
> This patch extends the lpages counter to cover the TDP case.
>
> Signed-off-by: Md Shahadat Hossain Shahin <shahinmd@amazon.de>
> Cc: Bartosz Szczepanek <bsz@amazon.de>
> ---
> arch/x86/kvm/mmu/tdp_mmu.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/x86/kvm/mmu/tdp_mmu.c b/arch/x86/kvm/mmu/tdp_mmu.c
> index 34207b874886..1e2a3cb33568 100644
> --- a/arch/x86/kvm/mmu/tdp_mmu.c
> +++ b/arch/x86/kvm/mmu/tdp_mmu.c
> @@ -425,6 +425,12 @@ static void __handle_changed_spte(struct kvm *kvm, int as_id, gfn_t gfn,
>
> if (old_spte == new_spte)
> return;
> +
> + if (is_large_pte(old_spte))
> + --kvm->stat.lpages;
> +
> + if (is_large_pte(new_spte))
> + ++kvm->stat.lpages;
Hrm, kvm->stat.lpages could get corrupted when __handle_changed_spte() is called
under read lock, e.g. if multiple vCPUs are faulting in memory.
next prev parent reply other threads:[~2021-04-29 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 12:46 Subject: [RFC PATCH] kvm/x86: Fix 'lpages' kvm stat for TDM MMU Shahin, Md Shahadat Hossain
2021-04-29 15:39 ` Paolo Bonzini
2021-04-29 16:49 ` Sean Christopherson [this message]
2021-04-29 17:04 ` Paolo Bonzini
2021-04-29 17:25 ` Ben Gardon
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=YIrjiXja3/5e6frs@google.com \
--to=seanjc@google.com \
--cc=bgardon@google.com \
--cc=bsz@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=shahinmd@amazon.de \
/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