LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Mingwei Zhang <mizhang@google.com> To: Paolo Bonzini <pbonzini@redhat.com> Cc: Sean Christopherson <seanjc@google.com>, Vitaly Kuznetsov <vkuznets@redhat.com>, Wanpeng Li <wanpengli@tencent.com>, Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Ben Gardon <bgardon@google.com>, David Matlack <dmatlack@google.com>, Mingwei Zhang <mizhang@google.com>, Jing Zhang <jingzhangos@google.com> Subject: [PATCH v4 0/3] Add detailed page size stats in KVM stats Date: Mon, 2 Aug 2021 21:46:04 -0700 [thread overview] Message-ID: <20210803044607.599629-1-mizhang@google.com> (raw) This commit basically adds detailed (large and regular) page size info to KVM stats and deprecate the old one: lpages. To support legacy MMU and TDP mmu, we use atomic type for all page stats. v3 -> v4: - rebase to origin/queue. [sean] - replace the lpages with page stats in place to avoid conflicts. [sean] v2 -> v3: - move kvm_update_page_stats to mmu.h as a static inline function. [sean] - remove is_last_spte check in mmu_spte_clear_track_bits. [bgardon] - change page_stats union by making it anonymous. [dmatlack] v1 -> v2: - refactor kvm_update_page_stats and remove 'spte' argument. [sean] - remove 'lpages' as it can be aggregated by user level [sean] - fix lpages stats update issue in __handle_change_pte [sean] - fix style issues and typos. [ben/sean] pre-v1 (internal reviewers): - use atomic in all page stats and use 'level' as index. [sean] - use an extra argument in kvm_update_page_stats for atomic/non-atomic. [bgardon] - should be careful on the difference between legacy mmu and tdp mmu. [jingzhangos] Mingwei Zhang (2): KVM: x86/mmu: Remove redundant spte present check in mmu_set_spte KVM: x86/mmu: Add detailed page size stats Sean Christopherson (1): KVM: x86/mmu: Avoid collision with !PRESENT SPTEs in TDP MMU lpage stats arch/x86/include/asm/kvm_host.h | 10 ++++++- arch/x86/kvm/mmu.h | 4 +++ arch/x86/kvm/mmu/mmu.c | 50 +++++++++++++++------------------ arch/x86/kvm/mmu/tdp_mmu.c | 9 ++---- arch/x86/kvm/x86.c | 5 +++- 5 files changed, 42 insertions(+), 36 deletions(-) -- 2.32.0.554.ge1b32706d8-goog
next reply other threads:[~2021-08-03 4:46 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-03 4:46 Mingwei Zhang [this message] 2021-08-03 4:46 ` [PATCH v4 1/3] KVM: x86/mmu: Remove redundant spte present check in mmu_set_spte Mingwei Zhang 2021-08-03 4:46 ` [PATCH v4 2/3] KVM: x86/mmu: Avoid collision with !PRESENT SPTEs in TDP MMU lpage stats Mingwei Zhang 2021-08-03 4:46 ` [PATCH v4 3/3] KVM: x86/mmu: Add detailed page size stats Mingwei Zhang 2021-08-09 22:26 ` Jim Mattson 2021-08-09 23:39 ` Mingwei Zhang 2021-08-10 0:01 ` Mingwei Zhang 2021-08-10 23:22 ` Peter Xu 2021-08-11 1:06 ` Mingwei Zhang 2021-08-11 13:12 ` Peter Xu 2021-08-12 17:44 ` Mingwei Zhang 2021-08-11 11:36 ` 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=20210803044607.599629-1-mizhang@google.com \ --to=mizhang@google.com \ --cc=bgardon@google.com \ --cc=dmatlack@google.com \ --cc=jingzhangos@google.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: linkBe 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).