From: David Hildenbrand <david@redhat.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, thuth@redhat.com,
borntraeger@de.ibm.com, frankja@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v8 0/6] s390x: SCLP Unit test
Date: Wed, 22 Jan 2020 11:02:48 +0100 [thread overview]
Message-ID: <3919c77f-1b89-07b2-8bb9-67ba5289defc@redhat.com> (raw)
In-Reply-To: <b47c3b26-398a-1791-802d-8f6f6abf3498@redhat.com>
On 22.01.20 10:55, David Hildenbrand wrote:
> On 20.01.20 19:42, Claudio Imbrenda wrote:
>> This patchset contains some minor cleanup, some preparatory work and
>> then the SCLP unit test itself.
>>
>> The unit test checks the following:
>>
>> * Correctly ignoring instruction bits that should be ignored
>> * Privileged instruction check
>> * Check for addressing exceptions
>> * Specification exceptions:
>> - SCCB size less than 8
>> - SCCB unaligned
>> - SCCB overlaps prefix or lowcore
>> - SCCB address higher than 2GB
>> * Return codes for
>> - Invalid command
>> - SCCB too short (but at least 8)
>> - SCCB page boundary violation
>>
>> v7 -> v8
>> * fixed existing stfl asm wrapper
>> * now using stfl asm wrapper in intercept.c
>> * patched the program interrupt handler to clear the sclp_busy bit
>> * removed now unnecessary expect_pgm_int from the unit test
>> v6 -> v7
>> * renamed spx() and stpx() wrappers to set_prefix and get_prefix
>> * set_prefix now takes a value and get_prefix now returns a value
>> * put back some inline assembly for spx and stpx as a consequence
>> * used LC_SIZE instead of 2 * PAGE_SIZE everywhere in the unit test
>> v5 -> v6
>> * fixed a bug in test_addressing
>> * improved comments in test_sccb_prefix
>> * replaced all inline assembly usages of spx and stpx with the wrappers
>> * added one more wrapper for test_one_sccb for read-only tests
>> v4 -> v5
>> * updated usage of report()
>> * added SPX and STPX wrappers to the library
>> * improved readability
>> * addressed some more comments
>> v3 -> v4
>> * export sclp_setup_int instead of copying it
>> * add more comments
>> * rename some more variables to improve readability
>> * improve the prefix test
>> * improved the invalid address test
>> * addressed further comments received during review
>> v2 -> v3
>> * generally improved the naming of variables
>> * added and fixed comments
>> * renamed test_one_run to test_one_simple
>> * added some const where needed
>> * addresed many more small comments received during review
>> v1 -> v2
>> * fix many small issues that came up during the first round of reviews
>> * add comments to each function
>> * use a static buffer for the SCCP template when used
>>
>> Claudio Imbrenda (6):
>> s390x: export sclp_setup_int
>> s390x: sclp: add service call instruction wrapper
>> s390x: lib: fix stfl wrapper asm
>> s390x: lib: add SPX and STPX instruction wrapper
>> s390x: lib: fix program interrupt handler if sclp_busy was set
>> s390x: SCLP unit test
>>
>> s390x/Makefile | 1 +
>> lib/s390x/asm/arch_def.h | 26 +++
>> lib/s390x/asm/facility.h | 2 +-
>> lib/s390x/sclp.h | 1 +
>> lib/s390x/interrupt.c | 5 +-
>> lib/s390x/sclp.c | 9 +-
>> s390x/intercept.c | 24 +-
>> s390x/sclp.c | 474 +++++++++++++++++++++++++++++++++++++++
>> s390x/unittests.cfg | 8 +
>> 9 files changed, 526 insertions(+), 24 deletions(-)
>> create mode 100644 s390x/sclp.c
>>
>
> Queued to
>
> https://github.com/davidhildenbrand/qemu.git s390-tcg-next
Lol, wrong shortcut (thanks Thomas :) )
Queued to
https://github.com/davidhildenbrand/kvm-unit-tests.git s390x-next
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2020-01-22 10:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 18:42 [kvm-unit-tests PATCH v8 0/6] s390x: SCLP Unit test Claudio Imbrenda
2020-01-20 18:42 ` [kvm-unit-tests PATCH v8 1/6] s390x: export sclp_setup_int Claudio Imbrenda
2020-01-20 18:42 ` [kvm-unit-tests PATCH v8 2/6] s390x: sclp: add service call instruction wrapper Claudio Imbrenda
2020-01-20 18:42 ` [kvm-unit-tests PATCH v8 3/6] s390x: lib: fix stfl wrapper asm Claudio Imbrenda
2020-01-21 6:15 ` Thomas Huth
2020-01-21 9:17 ` David Hildenbrand
2020-01-21 12:42 ` Janosch Frank
2020-01-20 18:42 ` [kvm-unit-tests PATCH v8 4/6] s390x: lib: add SPX and STPX instruction wrapper Claudio Imbrenda
2020-01-20 18:42 ` [kvm-unit-tests PATCH v8 5/6] s390x: lib: fix program interrupt handler if sclp_busy was set Claudio Imbrenda
2020-01-21 6:19 ` Thomas Huth
2020-01-21 9:18 ` David Hildenbrand
2020-01-20 18:42 ` [kvm-unit-tests PATCH v8 6/6] s390x: SCLP unit test Claudio Imbrenda
2020-01-22 9:55 ` David Hildenbrand
2020-01-22 10:10 ` David Hildenbrand
2020-01-22 10:22 ` David Hildenbrand
2020-01-22 10:31 ` Thomas Huth
2020-01-22 10:32 ` David Hildenbrand
2020-01-22 10:39 ` Thomas Huth
2020-01-22 10:40 ` David Hildenbrand
2020-01-22 11:20 ` David Hildenbrand
2020-01-22 12:13 ` Thomas Huth
2020-01-22 12:16 ` Thomas Huth
2020-01-22 14:15 ` strict aliasing in kvm-unit-tests (was: Re: [kvm-unit-tests PATCH v8 6/6] s390x: SCLP unit test) Thomas Huth
2020-01-22 14:42 ` Paolo Bonzini
2020-01-22 15:01 ` Laurent Vivier
2020-01-22 9:55 ` [kvm-unit-tests PATCH v8 0/6] s390x: SCLP Unit test David Hildenbrand
2020-01-22 10:02 ` David Hildenbrand [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=3919c77f-1b89-07b2-8bb9-67ba5289defc@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=frankja@linux.ibm.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