From: David Matlack <dmatlack@google.com>
To: pbonzini@redhat.com
Cc: seanjc@google.com, vkuznets@redhat.com, wanpengli@tencent.com,
jmattson@google.com, joro@8bytes.org, kvm@vger.kernel.org,
David Matlack <dmatlack@google.com>
Subject: [PATCH 0/5] KVM: x86/mmu: Clean up {Host,MMU}-writable documentation and validation
Date: Tue, 25 Jan 2022 23:05:13 +0000 [thread overview]
Message-ID: <20220125230518.1697048-1-dmatlack@google.com> (raw)
This series cleans up some documentation and WARNings related to
MMU-writable and Host-writable bits based on suggestions from Sean on
another patch [1].
[1] https://lore.kernel.org/kvm/YeH5QlwgGcpStZyp@google.com/
David Matlack (5):
KVM: x86/mmu: Move SPTE writable invariant checks to a helper function
KVM: x86/mmu: Check SPTE writable invariants when setting leaf SPTEs
KVM: x86/mmu: Move is_writable_pte() to spte.h
KVM: x86/mmu: Rename DEFAULT_SPTE_MMU_WRITEABLE to
DEFAULT_SPTE_MMU_WRITABLE
KVM: x86/mmu: Consolidate comments about {Host,MMU}-writable
arch/x86/kvm/mmu.h | 38 -------------
arch/x86/kvm/mmu/mmu.c | 11 ++--
arch/x86/kvm/mmu/spte.c | 13 +----
arch/x86/kvm/mmu/spte.h | 113 +++++++++++++++++++++++++++----------
arch/x86/kvm/mmu/tdp_mmu.c | 3 +
5 files changed, 93 insertions(+), 85 deletions(-)
base-commit: e2e83a73d7ce66f62c7830a85619542ef59c90e4
--
2.35.0.rc0.227.g00780c9af4-goog
next reply other threads:[~2022-01-25 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 23:05 David Matlack [this message]
2022-01-25 23:05 ` [PATCH 1/5] KVM: x86/mmu: Move SPTE writable invariant checks to a helper function David Matlack
2022-01-25 23:05 ` [PATCH 2/5] KVM: x86/mmu: Check SPTE writable invariants when setting leaf SPTEs David Matlack
2022-01-25 23:05 ` [PATCH 3/5] KVM: x86/mmu: Move is_writable_pte() to spte.h David Matlack
2022-01-25 23:16 ` [PATCH 0/5] KVM: x86/mmu: Clean up {Host,MMU}-writable documentation and validation David Matlack
2022-02-01 12:22 ` 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=20220125230518.1697048-1-dmatlack@google.com \
--to=dmatlack@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@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: 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).