From: Chao Peng <chao.p.peng@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Preparation for fd-based guest private memory
Date: Tue, 16 Aug 2022 20:53:20 +0800 [thread overview]
Message-ID: <20220816125322.1110439-1-chao.p.peng@linux.intel.com> (raw)
These two are separated from fd-based guest private memory v7
(https://lkml.org/lkml/2022/7/6/253) and include pure renaming
preparation for that whole patchset.
Send it separately here with wish it can make review/merge easier.
There is no functional change for these two patches.
Chao Peng (2):
KVM: Rename KVM_PRIVATE_MEM_SLOTS to KVM_INTERNAL_MEM_SLOTS
KVM: Rename mmu_notifier_* to mmu_invalidate_*
arch/arm64/kvm/mmu.c | 8 +--
arch/mips/include/asm/kvm_host.h | 2 +-
arch/mips/kvm/mmu.c | 12 ++---
arch/powerpc/include/asm/kvm_book3s_64.h | 2 +-
arch/powerpc/kvm/book3s_64_mmu_host.c | 4 +-
arch/powerpc/kvm/book3s_64_mmu_hv.c | 4 +-
arch/powerpc/kvm/book3s_64_mmu_radix.c | 6 +--
arch/powerpc/kvm/book3s_hv_nested.c | 2 +-
arch/powerpc/kvm/book3s_hv_rm_mmu.c | 8 +--
arch/powerpc/kvm/e500_mmu_host.c | 4 +-
arch/riscv/kvm/mmu.c | 4 +-
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/kvm/mmu/mmu.c | 14 ++---
arch/x86/kvm/mmu/paging_tmpl.h | 4 +-
include/linux/kvm_host.h | 66 ++++++++++++------------
virt/kvm/kvm_main.c | 52 ++++++++++---------
virt/kvm/pfncache.c | 17 +++---
17 files changed, 108 insertions(+), 103 deletions(-)
--
2.25.1
next reply other threads:[~2022-08-16 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 12:53 Chao Peng [this message]
2022-08-16 12:53 ` [PATCH 1/2] KVM: Rename KVM_PRIVATE_MEM_SLOTS to KVM_INTERNAL_MEM_SLOTS Chao Peng
2022-08-17 11:05 ` Paolo Bonzini
2022-08-18 5:53 ` Chao Peng
2022-08-16 12:53 ` [PATCH 2/2] KVM: Rename mmu_notifier_* to mmu_invalidate_* Chao Peng
2022-08-17 11:12 ` [PATCH 0/2] Preparation for fd-based guest private memory 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=20220816125322.1110439-1-chao.p.peng@linux.intel.com \
--to=chao.p.peng@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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®