From: David Stevens <stevensd@chromium.org>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org, Peter Xu <peterx@redhat.com>,
Yu Zhang <yu.c.zhang@linux.intel.com>,
Isaku Yamahata <isaku.yamahata@gmail.com>,
kvmarm@lists.linux.dev, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
David Stevens <stevensd@chromium.org>
Subject: [PATCH v8 8/8] KVM: mmu: remove __gfn_to_pfn_memslot
Date: Thu, 24 Aug 2023 17:04:08 +0900 [thread overview]
Message-ID: <20230824080408.2933205-9-stevensd@google.com> (raw)
In-Reply-To: <20230824080408.2933205-1-stevensd@google.com>
From: David Stevens <stevensd@chromium.org>
All callers have been migrated to __kvm_follow_pfn.
Signed-off-by: David Stevens <stevensd@chromium.org>
---
virt/kvm/kvm_main.c | 33 ---------------------------------
1 file changed, 33 deletions(-)
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index fa1848c6c84f..aebaf4a7340e 100644
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -2728,39 +2728,6 @@ kvm_pfn_t __kvm_follow_pfn(struct kvm_follow_pfn *foll)
}
EXPORT_SYMBOL_GPL(__kvm_follow_pfn);
-kvm_pfn_t __gfn_to_pfn_memslot(const struct kvm_memory_slot *slot, gfn_t gfn,
- bool atomic, bool interruptible, bool *async,
- bool write_fault, bool *writable, hva_t *hva)
-{
- kvm_pfn_t pfn;
- struct kvm_follow_pfn foll = {
- .slot = slot,
- .gfn = gfn,
- .flags = FOLL_GET,
- .atomic = atomic,
- .try_map_writable = !!writable,
- };
-
- if (write_fault)
- foll.flags |= FOLL_WRITE;
- if (async)
- foll.flags |= FOLL_NOWAIT;
- if (interruptible)
- foll.flags |= FOLL_INTERRUPTIBLE;
-
- pfn = __kvm_follow_pfn(&foll);
- if (pfn == KVM_PFN_ERR_NEEDS_IO) {
- *async = true;
- pfn = KVM_PFN_ERR_FAULT;
- }
- if (hva)
- *hva = foll.hva;
- if (writable)
- *writable = foll.writable;
- return pfn;
-}
-EXPORT_SYMBOL_GPL(__gfn_to_pfn_memslot);
-
kvm_pfn_t gfn_to_pfn_prot(struct kvm *kvm, gfn_t gfn, bool write_fault,
bool *writable)
{
--
2.42.0.rc1.204.g551eb34607-goog
prev parent reply other threads:[~2023-08-24 8:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 8:04 [PATCH v8 0/8] KVM: allow mapping non-refcounted pages David Stevens
2023-08-24 8:04 ` [PATCH v8 1/8] KVM: Assert that a page's refcount is elevated when marking accessed/dirty David Stevens
2023-08-24 8:04 ` [PATCH v8 2/8] KVM: mmu: Introduce __kvm_follow_pfn function David Stevens
2023-08-24 8:04 ` [PATCH v8 3/8] KVM: mmu: Make __kvm_follow_pfn not imply FOLL_GET David Stevens
2023-08-24 8:04 ` [PATCH v8 4/8] KVM: x86/mmu: Migrate to __kvm_follow_pfn David Stevens
2023-08-24 8:04 ` [PATCH v8 5/8] KVM: x86/mmu: Don't pass FOLL_GET " David Stevens
2023-08-24 9:13 ` Mika Penttilä
2023-08-24 8:04 ` [PATCH v8 6/8] KVM: arm64: Migrate " David Stevens
2023-08-24 8:04 ` [PATCH v8 7/8] KVM: PPC: " David Stevens
2023-08-24 8:04 ` David Stevens [this message]
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=20230824080408.2933205-9-stevensd@google.com \
--to=stevensd@chromium.org \
--cc=isaku.yamahata@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maz@kernel.org \
--cc=peterx@redhat.com \
--cc=seanjc@google.com \
--cc=yu.c.zhang@linux.intel.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).