From: Quentin Perret <qperret@google.com>
To: maz@kernel.org, will@kernel.org, james.morse@arm.com,
alexandru.elisei@arm.com, catalin.marinas@arm.com,
suzuki.poulose@arm.com
Cc: kernel-team@android.com, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/7] KVM: arm64: Reduce hyp_vmemmap overhead
Date: Wed, 2 Jun 2021 09:43:40 +0000 [thread overview]
Message-ID: <20210602094347.3730846-1-qperret@google.com> (raw)
Hi all,
This is a v2 of the patch series previously posted here:
https://lore.kernel.org/r/20210527125134.2116404-1-qperret@google.com/
Please refer to the cover letter of v1 for the context and motivation
behind the series.
Changes since v1:
- Added comment/doc in page_alloc.c explaining the locking expectations;
- Removed unnecessary casts in the 'page-to-list-node' helpers;
- A few other cosmetic changes in the allocator.
Thanks,
Quentin
Quentin Perret (7):
KVM: arm64: Move hyp_pool locking out of refcount helpers
KVM: arm64: Use refcount at hyp to check page availability
KVM: arm64: Remove list_head from hyp_page
KVM: arm64: Unify MMIO and mem host stage-2 pools
KVM: arm64: Remove hyp_pool pointer from struct hyp_page
KVM: arm64: Use less bits for hyp_page order
KVM: arm64: Use less bits for hyp_page refcount
arch/arm64/kvm/hyp/include/nvhe/gfp.h | 45 +------
arch/arm64/kvm/hyp/include/nvhe/mem_protect.h | 2 +-
arch/arm64/kvm/hyp/include/nvhe/memory.h | 7 +-
arch/arm64/kvm/hyp/include/nvhe/mm.h | 13 +-
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 60 +++++-----
arch/arm64/kvm/hyp/nvhe/page_alloc.c | 112 +++++++++++++-----
arch/arm64/kvm/hyp/nvhe/setup.c | 30 +++--
arch/arm64/kvm/hyp/reserved_mem.c | 3 +-
8 files changed, 145 insertions(+), 127 deletions(-)
--
2.32.0.rc0.204.g9fa02ecfa5-goog
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next reply other threads:[~2021-06-02 9:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 9:43 Quentin Perret [this message]
2021-06-02 9:43 ` [PATCH v2 1/7] KVM: arm64: Move hyp_pool locking out of refcount helpers Quentin Perret
2021-06-02 9:43 ` [PATCH v2 2/7] KVM: arm64: Use refcount at hyp to check page availability Quentin Perret
2021-06-02 9:43 ` [PATCH v2 3/7] KVM: arm64: Remove list_head from hyp_page Quentin Perret
2021-06-02 9:43 ` [PATCH v2 4/7] KVM: arm64: Unify MMIO and mem host stage-2 pools Quentin Perret
2021-06-06 10:31 ` Marc Zyngier
2021-06-07 8:04 ` Quentin Perret
2021-06-02 9:43 ` [PATCH v2 5/7] KVM: arm64: Remove hyp_pool pointer from struct hyp_page Quentin Perret
2021-06-02 9:43 ` [PATCH v2 6/7] KVM: arm64: Use less bits for hyp_page order Quentin Perret
2021-06-02 9:43 ` [PATCH v2 7/7] KVM: arm64: Use less bits for hyp_page refcount Quentin Perret
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=20210602094347.3730846-1-qperret@google.com \
--to=qperret@google.com \
--cc=alexandru.elisei@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.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).