From: Gavin Shan <gshan@redhat.com>
To: kvmarm@lists.linux.dev
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
pbonzini@redhat.com, shuah@kernel.org, maz@kernel.org,
oliver.upton@linux.dev, maciej.szmigiero@oracle.com,
seanjc@google.com, shan.gavin@gmail.com
Subject: [PATCH 1/2] KVM: selftests: Remove duplicate VM in memslot_perf_test
Date: Wed, 18 Jan 2023 17:21:32 +0800 [thread overview]
Message-ID: <20230118092133.320003-2-gshan@redhat.com> (raw)
In-Reply-To: <20230118092133.320003-1-gshan@redhat.com>
There are two VMs created in prepare_vm(), which isn't necessary.
To remove the second created and unnecessary VM.
Signed-off-by: Gavin Shan <gshan@redhat.com>
---
tools/testing/selftests/kvm/memslot_perf_test.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/tools/testing/selftests/kvm/memslot_perf_test.c b/tools/testing/selftests/kvm/memslot_perf_test.c
index e6587e193490..adbbcca3e354 100644
--- a/tools/testing/selftests/kvm/memslot_perf_test.c
+++ b/tools/testing/selftests/kvm/memslot_perf_test.c
@@ -308,8 +308,6 @@ static bool prepare_vm(struct vm_data *data, int nslots, uint64_t *maxslots,
data->hva_slots = malloc(sizeof(*data->hva_slots) * data->nslots);
TEST_ASSERT(data->hva_slots, "malloc() fail");
- data->vm = __vm_create_with_one_vcpu(&data->vcpu, mempages, guest_code);
-
pr_info_v("Adding slots 1..%i, each slot with %"PRIu64" pages + %"PRIu64" extra pages last\n",
data->nslots, data->pages_per_slot, rempages);
--
2.23.0
next prev parent reply other threads:[~2023-01-18 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 9:21 [PATCH 0/2] KVM: selftests: Remove duplicate VM in memslot_perf_test Gavin Shan
2023-01-18 9:21 ` Gavin Shan [this message]
2023-01-23 23:56 ` [PATCH 1/2] " Maciej S. Szmigiero
2023-01-27 0:08 ` Gavin Shan
2023-01-18 9:21 ` [PATCH 2/2] KVM: selftests: Assign guest page size in sync area early " Gavin Shan
2023-01-23 23:57 ` Maciej S. Szmigiero
2023-02-08 2:07 ` [PATCH 0/2] KVM: selftests: Remove duplicate VM " Sean Christopherson
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=20230118092133.320003-2-gshan@redhat.com \
--to=gshan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=maciej.szmigiero@oracle.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shan.gavin@gmail.com \
--cc=shuah@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