From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: x86: Documentation updates for 6.7
Date: Fri, 27 Oct 2023 13:49:26 -0700 [thread overview]
Message-ID: <20231027204933.3651381-3-seanjc@google.com> (raw)
In-Reply-To: <20231027204933.3651381-1-seanjc@google.com>
Doc updates for 6.7. The bulk is a cleanup of the kvm_mmu_page docs, which are
sadly already stale because I neglected to update the docs when removing the
TDP MMU's async root zapping :-(
The following changes since commit 5804c19b80bf625c6a9925317f845e497434d6d3:
Merge tag 'kvm-riscv-fixes-6.6-1' of https://github.com/kvm-riscv/linux into HEAD (2023-09-23 05:35:55 -0400)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-docs-6.7
for you to fetch changes up to b35babd3abea081de0611ce0d5b85281c18c52c7:
KVM: x86/pmu: Add documentation for fixed ctr on PMU filter (2023-09-27 14:23:51 -0700)
----------------------------------------------------------------
KVM x86 Documentation updates for 6.7:
- Fix various typos, notably a confusing reference to the non-existent
"struct kvm_vcpu_event" (the actual structure is kvm_vcpu_events, plural).
- Update x86's kvm_mmu_page documentation to bring it closer to the code
(this raced with the removal of async zapping and so the documentation is
already stale; my bad).
- Document the behavior of x86 PMU filters on fixed counters.
----------------------------------------------------------------
Jinrong Liang (1):
KVM: x86/pmu: Add documentation for fixed ctr on PMU filter
Michal Luczaj (1):
KVM: Correct kvm_vcpu_event(s) typo in KVM API documentation
Mingwei Zhang (6):
KVM: Documentation: Add the missing description for guest_mode in kvm_mmu_page_role
KVM: Documentation: Update the field name gfns and its description in kvm_mmu_page
KVM: Documentation: Add the missing description for ptep in kvm_mmu_page
KVM: Documentation: Add the missing description for tdp_mmu_root_count into kvm_mmu_page
KVM: Documentation: Add the missing description for mmu_valid_gen into kvm_mmu_page
KVM: Documentation: Add the missing description for tdp_mmu_page into kvm_mmu_page
Documentation/virt/kvm/api.rst | 36 +++++++++++++++++++++++--------
Documentation/virt/kvm/x86/mmu.rst | 43 ++++++++++++++++++++++++++++++--------
2 files changed, 61 insertions(+), 18 deletions(-)
next prev parent reply other threads:[~2023-10-27 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 20:49 [GIT PULL] KVM: x86 pull requests " Sean Christopherson
2023-10-27 20:49 ` [GIT PULL] KVM: x86: APIC changes " Sean Christopherson
2023-10-31 14:15 ` Paolo Bonzini
2023-10-27 20:49 ` Sean Christopherson [this message]
2023-10-31 14:14 ` [GIT PULL] KVM: x86: Documentation updates " Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2023-10-31 14:21 ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2023-10-31 14:20 ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: PMU change " Sean Christopherson
2023-10-27 20:49 ` [GIT PULL] KVM: x86: SVM changes " Sean Christopherson
2023-10-31 14:55 ` Paolo Bonzini
2023-10-27 20:49 ` [GIT PULL] KVM: x86: Xen " Sean Christopherson
2023-10-31 14: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=20231027204933.3651381-3-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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®