LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Shameer Kolothum <email@example.com>
Cc: <firstname.lastname@example.org>, <email@example.com>, <firstname.lastname@example.org>,
Subject: [PATCH v3 0/4] kvm/arm: New VMID allocator based on asid
Date: Thu, 29 Jul 2021 11:40:05 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
Major changes since v2 (Based on Will's feedback)
-Dropped adding a new static key and cpufeature for retrieving
supported VMID bits. Instead, we now make use of the
kvm_arm_vmid_bits variable (patch #2).
-Since we expect less frequent rollover in the case of VMIDs,
the TLB invalidation is now broadcasted on rollover instead
of keeping per CPU flush_pending info and issuing a local
-Clear active_vmids on vCPU schedule out to avoid unnecessarily
reserving the VMID space(patch #3).
-I have kept the struct kvm_vmid as it is for now(instead of a
typedef as suggested), as we may soon add another variable to
it when we introduce Pinned KVM VMID support.
Sanity tested on HiSilicon D06 board.
RFCv1 --> v2
- Dropped "pinned VMID" support for now.
- Dropped RFC tag.
History(from RFC v1):
Please find the RFC series here,
This is based on a suggestion from Will  to try out the asid
based kvm vmid solution as a separate VMID allocator instead of
the shared lib approach attempted in v4.
The idea is to compare both the approaches and see whether the
shared lib solution with callbacks make sense or not.
Though we are not yet using the pinned vmids yet, patch #2 has
code for pinned vmid support. This is just to help the comparison.
The measurement was made with maxcpus set to 8 and with the
number of VMID limited to 4-bit. The test involves running
concurrently 40 guests with 2 vCPUs. Each guest will then
execute hackbench 5 times before exiting.
The performance difference between the current algo and the
new one are(avg. of 10 runs):
- 1.9% less entry/exit from the guest
- 0.5% faster
This is more or less comparable to v4 numbers.
For the complete series, please see,
and for the shared asid lib v4 solution,
As you can see there are ofcourse code duplication with this
approach but may be it is more easy to maintain considering
the complexity involved.
Please take a look and let me know your feedback.
Julien Grall (1):
KVM: arm64: Align the VMID allocation with the arm64 ASID one
Shameer Kolothum (3):
KVM: arm64: Introduce a new VMID allocator for KVM
KVM: arm64: Make VMID bits accessible outside of allocator
KVM: arm64: Clear active_vmids on vCPU schedule out
arch/arm64/include/asm/kvm_host.h | 10 +-
arch/arm64/include/asm/kvm_mmu.h | 4 +-
arch/arm64/kernel/image-vars.h | 3 +
arch/arm64/kvm/Makefile | 2 +-
arch/arm64/kvm/arm.c | 122 +++++------------
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 3 +-
arch/arm64/kvm/mmu.c | 1 -
arch/arm64/kvm/vmid.c | 182 ++++++++++++++++++++++++++
8 files changed, 228 insertions(+), 99 deletions(-)
create mode 100644 arch/arm64/kvm/vmid.c
next reply other threads:[~2021-07-29 10:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 10:40 Shameer Kolothum [this message]
2021-07-29 10:40 ` [PATCH v3 1/4] KVM: arm64: Introduce a new VMID allocator for KVM Shameer Kolothum
2021-08-03 11:38 ` Will Deacon
2021-08-03 12:12 ` Shameerali Kolothum Thodi
2021-07-29 10:40 ` [PATCH v3 2/4] KVM: arm64: Make VMID bits accessible outside of allocator Shameer Kolothum
2021-07-29 10:40 ` [PATCH v3 3/4] KVM: arm64: Align the VMID allocation with the arm64 ASID one Shameer Kolothum
2021-07-29 14:59 ` kernel test robot
2021-07-29 10:40 ` [PATCH v3 4/4] KVM: arm64: Clear active_vmids on vCPU schedule out Shameer Kolothum
2021-08-03 11:40 ` Will Deacon
2021-08-03 12:55 ` Shameerali Kolothum Thodi
2021-08-03 15:30 ` Will Deacon
2021-08-03 15:56 ` Shameerali Kolothum Thodi
2021-08-06 12:24 ` Shameerali Kolothum Thodi
2021-08-09 13:09 ` Will Deacon
2021-08-09 13:48 ` Shameerali Kolothum Thodi
2021-08-11 8:47 ` Shameerali Kolothum Thodi
2021-10-11 6:06 ` Shameerali Kolothum Thodi
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [PATCH v3 0/4] kvm/arm: New VMID allocator based on asid' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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).