From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: sean.j.christopherson@intel.com, vkuznets@redhat.com
Subject: [PATCH 0/5] KVM: some x86 MMU cleanup and new tracepoints
Date: Thu, 4 Jul 2019 11:32:51 +0200 [thread overview]
Message-ID: <20190704093256.12989-1-pbonzini@redhat.com> (raw)
Given the attention to pgprintk, here are the patches I had locally
to add new tracepoints to __direct_map, FNAME(fetch) and mmu_set_spte().
These tracepoints actually come from a recent debugging session, so they
have proved their usefulness. :) And because I'm feeling both lazy *and*
generous, I'm including a couple free cleanups from the series that I was
debugging!
Paolo
Junaid Shahid (1):
kvm: x86: Do not release the page inside mmu_set_spte()
Paolo Bonzini (4):
KVM: x86: make FNAME(fetch) and __direct_map more similar
KVM: x86: remove now unneeded hugepage gfn adjustment
KVM: x86: change kvm_mmu_page_get_gfn BUG_ON to WARN_ON
KVM: x86: add tracepoints around __direct_map and FNAME(fetch)
arch/x86/kvm/mmu.c | 105 ++++++++++++++++++-------------------
arch/x86/kvm/mmutrace.h | 59 +++++++++++++++++++++
arch/x86/kvm/paging_tmpl.h | 42 +++++++--------
3 files changed, 129 insertions(+), 77 deletions(-)
--
2.21.0
next reply other threads:[~2019-07-04 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 9:32 Paolo Bonzini [this message]
2019-07-04 9:32 ` [PATCH 1/5] kvm: x86: Do not release the page inside mmu_set_spte() Paolo Bonzini
2019-07-04 9:32 ` [PATCH 2/5] KVM: x86: make FNAME(fetch) and __direct_map more similar Paolo Bonzini
2019-07-04 9:32 ` [PATCH 3/5] KVM: x86: remove now unneeded hugepage gfn adjustment Paolo Bonzini
2019-07-04 9:32 ` [PATCH 4/5] KVM: x86: change kvm_mmu_page_get_gfn BUG_ON to WARN_ON Paolo Bonzini
2019-07-04 9:32 ` [PATCH 5/5] KVM: x86: add tracepoints around __direct_map and FNAME(fetch) 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=20190704093256.12989-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@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
all inboxes | Powered by JetHome®