linux-kernel - [PATCH 0/5] KVM: some x86 MMU cleanup and new tracepoints

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20190704093256.12989-1-pbonzini@redhat.com>
Date:   Thu,  4 Jul 2019 11:32:51 +0200
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Cc:     sean.j.christopherson@...el.com, vkuznets@...hat.com
Subject: [PATCH 0/5] KVM: some x86 MMU cleanup and new tracepoints

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