From: Janosch Frank <frankja@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: kvm@vger.kernel.org, thuth@redhat.com, david@redhat.com,
borntraeger@de.ibm.com, imbrenda@linux.ibm.com,
linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v2 5/7] s390x: sie: Add first SIE test
Date: Mon, 30 Nov 2020 13:42:44 +0100 [thread overview]
Message-ID: <e312e141-5cee-9e4d-9e2c-d4770e77473d@linux.ibm.com> (raw)
In-Reply-To: <20201130114532.6fea10ac.cohuck@redhat.com>
On 11/30/20 11:45 AM, Cornelia Huck wrote:
> On Fri, 27 Nov 2020 08:06:27 -0500
> Janosch Frank <frankja@linux.ibm.com> wrote:
>
>> Let's check if we get the correct interception data on a few
>> diags. This commit is more of an addition of boilerplate code than a
>> real test.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> ---
>> s390x/Makefile | 1 +
>> s390x/sie.c | 125 ++++++++++++++++++++++++++++++++++++++++++++
>> s390x/unittests.cfg | 3 ++
>> 3 files changed, 129 insertions(+)
>> create mode 100644 s390x/sie.c
>>
>
> (...)
>
>> +static void sie(struct vm *vm)
>> +{
>> + while (vm->sblk->icptcode == 0) {
>> + sie64a(vm->sblk, &vm->save_area);
>> + if (vm->sblk->icptcode == 32)
>
> Can you maybe add #defines for the intercept codes you're checking for?
Sure ICTP_VALIDITY and ICPT_INSTRUCTION would make sense.
>
>> + handle_validity(vm);
>> + }
>> + vm->save_area.guest.grs[14] = vm->sblk->gg14;
>> + vm->save_area.guest.grs[15] = vm->sblk->gg15;
>> +}
>> +
>> +static void sblk_cleanup(struct vm *vm)
>> +{
>> + vm->sblk->icptcode = 0;
>> +}
>> +
>> +static void intercept_diag_10(void)
>> +{
>> + u32 instr = 0x83020010;
>> +
>> + vm.sblk->gpsw.addr = PAGE_SIZE * 2;
>> + vm.sblk->gpsw.mask = 0x0000000180000000ULL;
>> +
>> + memset(guest_instr, 0, PAGE_SIZE);
>> + memcpy(guest_instr, &instr, 4);
>> + sie(&vm);
>> + report(vm.sblk->icptcode == 4 && vm.sblk->ipa == 0x8302 && vm.sblk->ipb == 0x100000,
>
> Again, some #defines might help here, making clear that 0x8302 means
> diag. (The ipb value is clear enough :) Maybe you can also assemble
> instr out of pre-made pieces? Or factor out some code to a common
> function?
Yes, a diag test function that has the code as a parameter would make
this look nicer and I could also test ipa against the first 16bits of instr.
>
>> + "Diag 10 intercept");
>> + sblk_cleanup(&vm);
>> +}
>> +
>> +static void intercept_diag_44(void)
>> +{
>> + u32 instr = 0x83020044;
>> +
>> + vm.sblk->gpsw.addr = PAGE_SIZE * 2;
>> + vm.sblk->gpsw.mask = 0x0000000180000000ULL;
>> +
>> + memset(guest_instr, 0, PAGE_SIZE);
>> + memcpy(guest_instr, &instr, 4);
>> + sie(&vm);
>> + report(vm.sblk->icptcode == 4 && vm.sblk->ipa == 0x8302 && vm.sblk->ipb == 0x440000,
>> + "Diag 44 intercept");
>> + sblk_cleanup(&vm);
>> +}
>> +
>> +static void intercept_diag_9c(void)
>> +{
>> + u32 instr = 0x8302009c;
>> +
>> + vm.sblk->gpsw.addr = PAGE_SIZE * 2;
>> + vm.sblk->gpsw.mask = 0x0000000180000000ULL;
>> +
>> + memset(guest_instr, 0, PAGE_SIZE);
>> + memcpy(guest_instr, &instr, 4);
>> + sie(&vm);
>> + report(vm.sblk->icptcode == 4 && vm.sblk->ipa == 0x8302 && vm.sblk->ipb == 0x9c0000,
>> + "Diag 9c intercept");
>> + sblk_cleanup(&vm);
>> +}
>
> (...)
>
next prev parent reply other threads:[~2020-11-30 12:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 13:06 [kvm-unit-tests PATCH v2 0/7] s390x: Add SIE library and simple test Janosch Frank
2020-11-27 13:06 ` [kvm-unit-tests PATCH v2 1/7] s390x: Add test_bit to library Janosch Frank
2020-11-27 13:06 ` [kvm-unit-tests PATCH v2 2/7] s390x: Consolidate sclp read info Janosch Frank
2020-11-27 13:56 ` Thomas Huth
2020-11-27 13:59 ` Thomas Huth
2020-11-27 13:06 ` [kvm-unit-tests PATCH v2 3/7] s390x: SCLP feature checking Janosch Frank
2020-11-27 14:18 ` Thomas Huth
2020-11-30 10:38 ` Cornelia Huck
2020-11-27 13:06 ` [kvm-unit-tests PATCH v2 4/7] s390x: sie: Add SIE to lib Janosch Frank
2020-11-27 13:06 ` [kvm-unit-tests PATCH v2 5/7] s390x: sie: Add first SIE test Janosch Frank
2020-11-27 16:22 ` Thomas Huth
2020-11-30 10:45 ` Cornelia Huck
2020-11-30 12:42 ` Janosch Frank [this message]
2020-11-27 13:06 ` [kvm-unit-tests PATCH v2 6/7] s390x: Add diag318 intercept test Janosch Frank
2020-11-27 16:46 ` Thomas Huth
2020-11-30 12:38 ` Janosch Frank
2020-11-30 11:30 ` Cornelia Huck
2020-11-27 13:06 ` [kvm-unit-tests PATCH v2 7/7] s390x: Fix sclp.h style issues Janosch Frank
2020-11-27 14:25 ` Thomas Huth
2020-11-30 10:49 ` Cornelia Huck
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=e312e141-5cee-9e4d-9e2c-d4770e77473d@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.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