From: Janosch Frank <frankja@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, kvm@vger.kernel.org
Cc: borntraeger@de.ibm.com, david@redhat.com, cohuck@redhat.com,
linux-s390@vger.kernel.org
Subject: Re: [PATCH v8 3/4] selftests: KVM: s390x: Add reset tests
Date: Thu, 30 Jan 2020 12:32:10 +0100 [thread overview]
Message-ID: <0993d789-5cfd-d4c3-a39e-28d22d82dd43@linux.ibm.com> (raw)
In-Reply-To: <e0f72503-d292-edc4-67e1-abe1cbab3f96@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 6457 bytes --]
On 1/30/20 11:51 AM, Thomas Huth wrote:
> On 29/01/2020 21.03, Janosch Frank wrote:
>> Test if the registers end up having the correct values after a normal,
>> initial and clear reset.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> ---
>> tools/testing/selftests/kvm/Makefile | 1 +
>> tools/testing/selftests/kvm/s390x/resets.c | 165 +++++++++++++++++++++
>> 2 files changed, 166 insertions(+)
>> create mode 100644 tools/testing/selftests/kvm/s390x/resets.c
>>
>> diff --git a/tools/testing/selftests/kvm/Makefile b/tools/testing/selftests/kvm/Makefile
>> index 3138a916574a..fe1ea294730c 100644
>> --- a/tools/testing/selftests/kvm/Makefile
>> +++ b/tools/testing/selftests/kvm/Makefile
>> @@ -36,6 +36,7 @@ TEST_GEN_PROGS_aarch64 += kvm_create_max_vcpus
>>
>> TEST_GEN_PROGS_s390x = s390x/memop
>> TEST_GEN_PROGS_s390x += s390x/sync_regs_test
>> +TEST_GEN_PROGS_s390x += s390x/resets
>> TEST_GEN_PROGS_s390x += dirty_log_test
>> TEST_GEN_PROGS_s390x += kvm_create_max_vcpus
>>
>> diff --git a/tools/testing/selftests/kvm/s390x/resets.c b/tools/testing/selftests/kvm/s390x/resets.c
>> new file mode 100644
>> index 000000000000..2b2378cc9e80
>> --- /dev/null
>> +++ b/tools/testing/selftests/kvm/s390x/resets.c
>> @@ -0,0 +1,165 @@
>> +// SPDX-License-Identifier: GPL-2.0-or-later
>> +/*
>> + * Test for s390x CPU resets
>> + *
>> + * Copyright (C) 2020, IBM
>> + */
>> +
>> +#include <stdio.h>
>> +#include <stdlib.h>
>> +#include <string.h>
>> +#include <sys/ioctl.h>
>> +
>> +#include "test_util.h"
>> +#include "kvm_util.h"
>> +
>> +#define VCPU_ID 3
>> +
>> +struct kvm_vm *vm;
>> +struct kvm_run *run;
>> +struct kvm_sync_regs *regs;
>> +static uint64_t regs_null[16];
>> +
>> +static uint64_t crs[16] = { 0x40000ULL,
>> + 0x42000ULL,
>> + 0, 0, 0, 0, 0,
>> + 0x43000ULL,
>> + 0, 0, 0, 0, 0,
>> + 0x44000ULL,
>> + 0, 0
>> +};
>> +
>> +static void guest_code_initial(void)
>> +{
>> + /* Round toward 0 */
>> + uint32_t fpc = 0x11;
>> +
>> + /* Dirty registers */
>> + asm volatile (
>> + " lctlg 0,15,%0\n"
>> + " sfpc %1\n"
>> + : : "Q" (crs), "d" (fpc));
>
> I'd recommend to add a GUEST_SYNC(0) here ... otherwise the guest code
> tries to return from this function and will cause a crash - which will
> also finish execution of the guest, but might have unexpected side effects.
Ok
>
>> +}
>> +
>> +static void test_one_reg(uint64_t id, uint64_t value)
>> +{
>> + struct kvm_one_reg reg;
>> + uint64_t eval_reg;
>> +
>> + reg.addr = (uintptr_t)&eval_reg;
>> + reg.id = id;
>> + vcpu_get_reg(vm, VCPU_ID, ®);
>> + TEST_ASSERT(eval_reg == value, "value == %s", value);
>> +}
>> +
>> +static void assert_clear(void)
>> +{
>> + struct kvm_sregs sregs;
>> + struct kvm_regs regs;
>> + struct kvm_fpu fpu;
>> +
>> + vcpu_regs_get(vm, VCPU_ID, ®s);
>> + TEST_ASSERT(!memcmp(®s.gprs, regs_null, sizeof(regs.gprs)), "grs == 0");
>> +
>> + vcpu_sregs_get(vm, VCPU_ID, &sregs);
>> + TEST_ASSERT(!memcmp(&sregs.acrs, regs_null, sizeof(sregs.acrs)), "acrs == 0");
>> +
>> + vcpu_fpu_get(vm, VCPU_ID, &fpu);
>> + TEST_ASSERT(!memcmp(&fpu.fprs, regs_null, sizeof(fpu.fprs)), "fprs == 0");
>> +}
>> +
>> +static void assert_initial(void)
>> +{
>> + struct kvm_sregs sregs;
>> + struct kvm_fpu fpu;
>> +
>> + vcpu_sregs_get(vm, VCPU_ID, &sregs);
>> + TEST_ASSERT(sregs.crs[0] == 0xE0UL, "cr0 == 0xE0");
>> + TEST_ASSERT(sregs.crs[14] == 0xC2000000UL, "cr14 == 0xC2000000");
>> + TEST_ASSERT(!memcmp(&sregs.crs[1], regs_null, sizeof(sregs.crs[1]) * 12),
>> + "cr1-13 == 0");
>> + TEST_ASSERT(sregs.crs[15] == 0, "cr15 == 0");
>> +
>> + vcpu_fpu_get(vm, VCPU_ID, &fpu);
>> + TEST_ASSERT(!fpu.fpc, "fpc == 0");
>> +
>> + test_one_reg(KVM_REG_S390_GBEA, 1);
>> + test_one_reg(KVM_REG_S390_PP, 0);
>> + test_one_reg(KVM_REG_S390_TODPR, 0);
>> + test_one_reg(KVM_REG_S390_CPU_TIMER, 0);
>> + test_one_reg(KVM_REG_S390_CLOCK_COMP, 0);
>> +}
>> +
>> +static void assert_normal(void)
>> +{
>> + test_one_reg(KVM_REG_S390_PFTOKEN, KVM_S390_PFAULT_TOKEN_INVALID);
>> +}
>> +
>> +static void test_normal(void)
>> +{
>> + printf("Testing notmal reset\n");
>> + /* Create VM */
>> + vm = vm_create_default(VCPU_ID, 0, guest_code_initial);
>> + run = vcpu_state(vm, VCPU_ID);
>> + regs = &run->s.regs;
>> +
>> + _vcpu_run(vm, VCPU_ID);
>
> Could you use vcpu_run() instead of _vcpu_run() ?
Done.
>
>> + vcpu_ioctl(vm, VCPU_ID, KVM_S390_NORMAL_RESET, 0);
>> + assert_normal();
>> + kvm_vm_free(vm);
>> +}
>> +
>> +static int test_initial(void)
>> +{
>> + int rv;
>> +
>> + printf("Testing initial reset\n");
>> + /* Create VM */
>> + vm = vm_create_default(VCPU_ID, 0, guest_code_initial);
>> + run = vcpu_state(vm, VCPU_ID);
>> + regs = &run->s.regs;
>> +
>> + rv = _vcpu_run(vm, VCPU_ID);
>
> Extra bonus points if you check here that the registers contain the
> values that have been set by the guest ;-)
I started working on that yesterday
>
>> + vcpu_ioctl(vm, VCPU_ID, KVM_S390_INITIAL_RESET, 0);
>> + assert_normal();
>> + assert_initial();
>> + kvm_vm_free(vm);
>> + return rv;
>> +}
>> +
>> +static int test_clear(void)
>> +{
>> + int rv;
>> +
>> + printf("Testing clear reset\n");
>> + /* Create VM */
>> + vm = vm_create_default(VCPU_ID, 0, guest_code_initial);
>> + run = vcpu_state(vm, VCPU_ID);
>> + regs = &run->s.regs;
>> +
>> + rv = _vcpu_run(vm, VCPU_ID);
>> +
>> + vcpu_ioctl(vm, VCPU_ID, KVM_S390_CLEAR_RESET, 0);
>> + assert_normal();
>> + assert_initial();
>> + assert_clear();
>> + kvm_vm_free(vm);
>> + return rv;
>> +}
>> +
>> +int main(int argc, char *argv[])
>> +{
>> + int addl_resets;
>> +
>> + setbuf(stdout, NULL); /* Tell stdout not to buffer its content */
>> + addl_resets = kvm_check_cap(KVM_CAP_S390_VCPU_RESETS);
>> +
>> + test_initial();
>> + if (addl_resets) {
>
> I think you could still fit this into one line, without the need to
> declare the addl_resets variable:
The other question is if we still need to check that if the test is
bundled with the kernel anyway?
>
> if (kvm_check_cap(KVM_CAP_S390_VCPU_RESETS)) {
>
>> + test_normal();
>> + test_clear();
>> + }
>> + return 0;
>> +}
>
> Apart from the nits, this looks pretty good already, thanks for putting
> it together!
>
> Thomas
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-01-30 11:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 20:03 [PATCH v8 0/4] KVM: s390: Add new reset vcpu API Janosch Frank
2020-01-29 20:03 ` [PATCH v8 1/4] " Janosch Frank
2020-01-30 8:55 ` [PATCH/FIXUP FOR STABLE BEFORE THIS SERIES] KVM: s390: do not clobber user space fpc during guest reset Christian Borntraeger
2020-01-30 9:49 ` David Hildenbrand
2020-01-30 10:39 ` Cornelia Huck
2020-01-30 10:56 ` Thomas Huth
2020-01-30 11:07 ` Christian Borntraeger
2020-01-30 11:01 ` Christian Borntraeger
2020-01-30 11:14 ` Christian Borntraeger
2020-01-30 11:20 ` David Hildenbrand
2020-01-30 11:27 ` Christian Borntraeger
2020-01-30 11:42 ` [PATCH v2] KVM: s390: do not clobber user space registers during guest reset/store status Christian Borntraeger
2020-01-30 11:44 ` Christian Borntraeger
2020-01-30 12:01 ` Christian Borntraeger
2020-01-30 12:38 ` David Hildenbrand
2020-01-30 9:00 ` [PATCH v8 1/4] KVM: s390: Add new reset vcpu API Thomas Huth
2020-01-30 9:58 ` Christian Borntraeger
2020-01-29 20:03 ` [PATCH v8 2/4] selftests: KVM: Add fpu and one reg set/get library functions Janosch Frank
2020-01-30 10:36 ` Thomas Huth
2020-01-30 13:55 ` Andrew Jones
2020-01-30 14:10 ` Janosch Frank
2020-01-30 14:30 ` Andrew Jones
2020-01-30 14:58 ` Janosch Frank
2020-01-30 15:04 ` Andrew Jones
2020-01-29 20:03 ` [PATCH v8 3/4] selftests: KVM: s390x: Add reset tests Janosch Frank
2020-01-30 10:51 ` Thomas Huth
2020-01-30 11:32 ` Janosch Frank [this message]
2020-01-30 11:36 ` Thomas Huth
2020-01-29 20:03 ` [PATCH v8 4/4] selftests: KVM: testing the local IRQs resets Janosch Frank
2020-01-30 10:55 ` Cornelia Huck
2020-01-30 11:18 ` Janosch Frank
2020-01-30 11:28 ` Cornelia Huck
2020-01-30 11:34 ` Janosch Frank
2020-01-30 11:10 ` Thomas Huth
2020-01-30 11:33 ` Janosch Frank
2020-01-30 9:10 ` [PATCH] KVM: s390: Cleanup initial cpu reset Janosch Frank
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=0993d789-5cfd-d4c3-a39e-28d22d82dd43@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=thuth@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