From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.linux.dev, Gavin Shan <gshan@redhat.com>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org, oliver.upton@linux.dev,
linux-kernel@vger.kernel.org, zhenyzha@redhat.com,
peterx@redhat.com, kvmarm@lists.cs.columbia.edu,
ricarkol@google.com, mail@maciej.szmigiero.name,
shan.gavin@gmail.com, shuah@kernel.org, seanjc@google.com,
ajones@ventanamicro.com
Subject: Re: [PATCH v3 0/6] KVM: selftests: memslot_perf_test: aarch64 cleanup/fixes
Date: Thu, 10 Nov 2022 19:00:38 +0000 [thread overview]
Message-ID: <166810681799.3361246.8104966072193072364.b4-ty@kernel.org> (raw)
In-Reply-To: <20221020071209.559062-1-gshan@redhat.com>
On Thu, 20 Oct 2022 15:12:03 +0800, Gavin Shan wrote:
> kvm/selftests/memslots_perf_test doesn't work with 64KB-page-size-host
> and 4KB-page-size-guest on aarch64. In the implementation, the host and
> guest page size have been hardcoded to 4KB. It's ovbiously not working
> on aarch64 which supports 4KB, 16KB, 64KB individually on host and guest.
>
> This series tries to fix it. After the series is applied, the test runs
> successfully with 64KB-page-size-host and 4KB-page-size-guest.
>
> [...]
Applied to next, thanks!
[1/6] KVM: selftests: memslot_perf_test: Use data->nslots in prepare_vm()
commit: 3bfadb2325891d122771ce534336af531e93d7b2
[2/6] KVM: selftests: memslot_perf_test: Consolidate loop conditions in prepare_vm()
commit: 2aae5e6795e1407334bb849f96f11c9051b959e2
[3/6] KVM: selftests: memslot_perf_test: Probe memory slots for once
commit: 34396437b11f904fc61b272e3974f4c92868451b
[4/6] KVM: selftests: memslot_perf_test: Support variable guest page size
commit: 8675c6f226986ddb67752be22279a0e2385b197e
[5/6] KVM: selftests: memslot_perf_test: Consolidate memory
commit: 88a64e65484ef6b5cb09fe545d0dd00c950a1131
[6/6] KVM: selftests: memslot_perf_test: Report optimal memory slots
commit: a69170c65acdf430e24fc1b6174dcc3aa501fe2f
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2022-11-10 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 7:12 Gavin Shan
2022-10-20 7:12 ` [PATCH v3 1/6] KVM: selftests: memslot_perf_test: Use data->nslots in prepare_vm() Gavin Shan
2022-10-20 7:12 ` [PATCH v3 2/6] KVM: selftests: memslot_perf_test: Consolidate loop conditions " Gavin Shan
2022-10-20 7:12 ` [PATCH v3 3/6] KVM: selftests: memslot_perf_test: Probe memory slots for once Gavin Shan
2022-10-20 7:12 ` [PATCH v3 4/6] KVM: selftests: memslot_perf_test: Support variable guest page size Gavin Shan
2022-10-20 7:12 ` [PATCH v3 5/6] KVM: selftests: memslot_perf_test: Consolidate memory Gavin Shan
2022-10-20 7:12 ` [PATCH v3 6/6] KVM: selftests: memslot_perf_test: Report optimal memory slots Gavin Shan
2022-10-24 23:18 ` [PATCH v3 0/6] KVM: selftests: memslot_perf_test: aarch64 cleanup/fixes Maciej S. Szmigiero
2022-11-04 23:57 ` Gavin Shan
2022-11-10 10:54 ` Gavin Shan
2022-11-10 19:00 ` Marc Zyngier [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=166810681799.3361246.8104966072193072364.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=gshan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=ricarkol@google.com \
--cc=seanjc@google.com \
--cc=shan.gavin@gmail.com \
--cc=shuah@kernel.org \
--cc=zhenyzha@redhat.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®