From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, imbrenda@linux.ibm.com,
thuth@redhat.com, nrb@linux.ibm.com, david@redhat.com
Subject: [kvm-unit-tests PATCH v3 0/9] s390x: uv-host: Fixups and extensions part 1
Date: Tue, 2 May 2023 13:07:23 +0000 [thread overview]
Message-ID: <20230502130732.147210-1-frankja@linux.ibm.com> (raw)
The uv-host test has a lot of historical growth problems which have
largely been overlooked since running it is harder than running a KVM
(guest 2) based test.
This series fixes up smaller problems but still leaves the test with
fails when running create config base and variable storage
tests. Those problems will either be fixed up with the second series
or with a firmware fix since I'm unsure on which side of the os/fw
fence the problem exists.
The series is based on my other series that introduces pv-ipl and
pv-icpt. The memory allocation fix will be added to the new version of
that series so all G1 tests are fixed.
v3:
- Re-based on the ipl/icpt series
- Added review-bys
v2:
- Added patch that exchanges sigp_retry with the smp variant
- Re-worked the create config test handling
- Minor fixups
Janosch Frank (9):
s390x: uv-host: Fix UV init test memory allocation
s390x: uv-host: Check for sufficient amount of memory
s390x: uv-host: Beautify code
s390x: uv-host: Add cpu number check
s390x: uv-host: Fix create guest variable storage prefix check
s390x: uv-host: Switch to smp_sigp
s390x: uv-host: Properly handle config creation errors
s390x: uv-host: Fence access checks when UV debug is enabled
s390x: uv-host: Add the test to unittests.conf
lib/s390x/asm/uv.h | 1 +
s390x/unittests.cfg | 5 ++
s390x/uv-host.c | 137 ++++++++++++++++++++++++++++++++++----------
3 files changed, 114 insertions(+), 29 deletions(-)
--
2.34.1
next reply other threads:[~2023-05-02 13:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 13:07 Janosch Frank [this message]
2023-05-02 13:07 ` [kvm-unit-tests PATCH v3 1/9] s390x: uv-host: Fix UV init test memory allocation Janosch Frank
2023-05-10 8:51 ` Nico Boehr
2023-05-10 9:03 ` Janosch Frank
2023-05-10 11:14 ` Nico Boehr
2023-05-02 13:07 ` [kvm-unit-tests PATCH v3 2/9] s390x: uv-host: Check for sufficient amount of memory Janosch Frank
2023-05-02 13:07 ` [kvm-unit-tests PATCH v3 3/9] s390x: uv-host: Beautify code Janosch Frank
2023-05-02 13:07 ` [kvm-unit-tests PATCH v3 4/9] s390x: uv-host: Add cpu number check Janosch Frank
2023-05-02 13:07 ` [kvm-unit-tests PATCH v3 5/9] s390x: uv-host: Fix create guest variable storage prefix check Janosch Frank
2023-05-02 13:07 ` [kvm-unit-tests PATCH v3 6/9] s390x: uv-host: Switch to smp_sigp Janosch Frank
2023-05-10 8:53 ` Nico Boehr
2023-05-02 13:07 ` [kvm-unit-tests PATCH v3 7/9] s390x: uv-host: Properly handle config creation errors Janosch Frank
2023-05-10 11:17 ` Nico Boehr
2023-05-02 13:07 ` [kvm-unit-tests PATCH v3 8/9] s390x: uv-host: Fence access checks when UV debug is enabled Janosch Frank
2023-05-02 13:07 ` [kvm-unit-tests PATCH v3 9/9] s390x: uv-host: Add the test to unittests.conf Janosch Frank
2023-05-10 11:25 ` Nico Boehr
2023-05-31 14:47 ` [kvm-unit-tests PATCH v3 0/9] s390x: uv-host: Fixups and extensions part 1 Nico Boehr
2023-06-02 8:10 ` 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=20230502130732.147210-1-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--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