From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
kvmarm@lists.cs.columbia.edu, linux-mm@kvack.org
Cc: Sean Christopherson <seanjc@google.com>,
Matthew Wilcox <willy@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Will Deacon <will@kernel.org>,
Quentin Perret <qperret@google.com>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
kernel-team@android.com
Subject: [PATCH 0/5] KVM: Remove kvm_is_transparent_hugepage() and friends
Date: Sat, 17 Jul 2021 10:55:36 +0100 [thread overview]
Message-ID: <20210717095541.1486210-1-maz@kernel.org> (raw)
A while ago, Willy and Sean pointed out[1] that arm64 is the last user
of kvm_is_transparent_hugepage(), and that there would actually be
some benefit in looking at the userspace mapping directly instead.
This small series does exactly that, although it doesn't try to
support more than a PMD-sized mapping yet for THPs. We could probably
look into unifying this with the huge PUD code, and there is still
some potential use of the contiguous hint.
As a consequence, it removes kvm_is_transparent_hugepage(),
PageTransCompoundMap() and kvm_get_pfn(), all of which have no user
left after this rework.
This has been lightly tested on an Altra box. Although nothing caught
fire, it requires some careful reviewing on the arm64 side.
[1] https://lore.kernel.org/r/YLpLvFPXrIp8nAK4@google.com
Marc Zyngier (5):
KVM: arm64: Walk userspace page tables to compute the THP mapping size
KVM: arm64: Avoid mapping size adjustment on permission fault
KVM: Remove kvm_is_transparent_hugepage() and PageTransCompoundMap()
KVM: arm64: Use get_page() instead of kvm_get_pfn()
KVM: Get rid of kvm_get_pfn()
arch/arm64/kvm/mmu.c | 57 +++++++++++++++++++++++++++++++++-----
include/linux/kvm_host.h | 1 -
include/linux/page-flags.h | 37 -------------------------
virt/kvm/kvm_main.c | 19 +------------
4 files changed, 51 insertions(+), 63 deletions(-)
--
2.30.2
next reply other threads:[~2021-07-17 9:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 9:55 Marc Zyngier [this message]
2021-07-17 9:55 ` [PATCH 1/5] KVM: arm64: Walk userspace page tables to compute the THP mapping size Marc Zyngier
2021-07-19 6:31 ` Paolo Bonzini
2021-07-19 9:31 ` Marc Zyngier
2021-07-20 17:23 ` Alexandru Elisei
2021-07-20 20:33 ` Sean Christopherson
2021-07-21 14:58 ` Will Deacon
2021-07-21 15:56 ` Sean Christopherson
2021-07-21 16:37 ` Alexandru Elisei
2021-07-23 8:48 ` Marc Zyngier
2021-07-17 9:55 ` [PATCH 2/5] KVM: arm64: Avoid mapping size adjustment on permission fault Marc Zyngier
2021-07-23 15:55 ` Alexandru Elisei
2021-07-23 16:18 ` Marc Zyngier
2021-07-17 9:55 ` [PATCH 3/5] KVM: Remove kvm_is_transparent_hugepage() and PageTransCompoundMap() Marc Zyngier
2021-07-19 6:31 ` Paolo Bonzini
2021-07-17 9:55 ` [PATCH 4/5] KVM: arm64: Use get_page() instead of kvm_get_pfn() Marc Zyngier
2021-07-17 9:55 ` [PATCH 5/5] KVM: Get rid " Marc Zyngier
2021-07-19 6:31 ` 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=20210717095541.1486210-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=pbonzini@redhat.com \
--cc=qperret@google.com \
--cc=seanjc@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
/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).