From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, imbrenda@linux.ibm.com,
david@redhat.com, thuth@redhat.com, cohuck@redhat.com,
nrb@linux.ibm.com
Subject: [kvm-unit-tests PATCH 0/5] s390x: Allocation and hosting environment detection fixes
Date: Fri, 14 Jan 2022 10:02:40 +0000 [thread overview]
Message-ID: <20220114100245.8643-1-frankja@linux.ibm.com> (raw)
I took some time before Christmas to write a test runner for lpar
which automatically runs all tests and sends me the logs. It's based
on the zhmc library to control starting and stopping of the lpar and
works by having a menu entry for each kvm unit test.
This revealed a number of test fails when the tests are run under lpar
as there are a few differences:
* lpars most often have a very high memory amount (upwards of 8GB)
compared to our qemu env (256MB)
* lpar supports diag308 subcode 2
* lpar does not provide virtio devices
The higher memory amount leads to allocations crossing the 2GB or 4GB
border which made sclp and sigp calls fail that expect 31/32 bit
addresses.
Janosch Frank (5):
lib: s390x: vm: Add kvm and lpar vm queries
s390x: css: Skip if we're not run by qemu
s390x: diag308: Only test subcode 2 under QEMU
s390x: smp: Allocate memory in DMA31 space
s390x: firq: Fix sclp buffer allocation
lib/s390x/vm.c | 39 +++++++++++++++++++++++++++++++++++++++
lib/s390x/vm.h | 23 +++++++++++++++++++++++
s390x/css.c | 10 +++++++++-
s390x/diag308.c | 15 ++++++++++++++-
s390x/firq.c | 2 +-
s390x/smp.c | 4 ++--
s390x/stsi.c | 21 +--------------------
7 files changed, 89 insertions(+), 25 deletions(-)
--
2.32.0
next reply other threads:[~2022-01-14 10:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 10:02 Janosch Frank [this message]
2022-01-14 10:02 ` [kvm-unit-tests PATCH 1/5] lib: s390x: vm: Add kvm and lpar vm queries Janosch Frank
2022-01-14 11:18 ` Claudio Imbrenda
2022-01-14 12:28 ` Janosch Frank
2022-01-14 12:55 ` Claudio Imbrenda
2022-01-14 13:27 ` Nico Boehr
2022-01-14 13:35 ` Janosch Frank
2022-01-14 13:43 ` Nico Boehr
2022-01-14 10:02 ` [kvm-unit-tests PATCH 2/5] s390x: css: Skip if we're not run by qemu Janosch Frank
2022-01-14 10:41 ` Claudio Imbrenda
2022-01-17 7:01 ` Thomas Huth
2022-01-14 10:02 ` [kvm-unit-tests PATCH 3/5] s390x: diag308: Only test subcode 2 under QEMU Janosch Frank
2022-01-14 10:39 ` Claudio Imbrenda
2022-01-17 7:04 ` Thomas Huth
2022-01-17 9:39 ` Janosch Frank
2022-01-14 10:02 ` [kvm-unit-tests PATCH 4/5] s390x: smp: Allocate memory in DMA31 space Janosch Frank
2022-01-14 11:18 ` Claudio Imbrenda
2022-01-14 12:50 ` Nico Boehr
2022-01-14 12:57 ` Claudio Imbrenda
2022-01-14 13:07 ` Janosch Frank
2022-01-14 13:01 ` Claudio Imbrenda
2022-01-14 13:13 ` Janosch Frank
2022-01-14 13:16 ` Claudio Imbrenda
2022-01-14 13:18 ` Janosch Frank
2022-01-14 13:19 ` Claudio Imbrenda
2022-01-14 10:02 ` [kvm-unit-tests PATCH 5/5] s390x: firq: Fix sclp buffer allocation Janosch Frank
2022-01-14 11:19 ` Claudio Imbrenda
2022-01-14 11:19 ` [kvm-unit-tests PATCH 0/5] s390x: Allocation and hosting environment detection fixes Claudio Imbrenda
2022-01-14 12:23 ` 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=20220114100245.8643-1-frankja@linux.ibm.com \
--to=frankja@linux.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.