From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
thuth@redhat.com, nrb@linux.ibm.com, david@redhat.com
Subject: Re: [kvm-unit-tests PATCH v3 4/7] lib: s390x: uv: Add pv guest requirement check function
Date: Fri, 21 Apr 2023 16:13:53 +0200 [thread overview]
Message-ID: <20230421161353.2dfaea97@p-imbrenda> (raw)
In-Reply-To: <20230421113647.134536-5-frankja@linux.ibm.com>
On Fri, 21 Apr 2023 11:36:44 +0000
Janosch Frank <frankja@linux.ibm.com> wrote:
> When running PV guests some of the UV memory needs to be allocated
> with > 31 bit addresses which means tests with PV guests will always
> need a lot more memory than other tests.
> Additionally facilities nr 158 and sclp.sief2 need to be available.
>
> Let's add a function that checks for these requirements and prints a
> helpful skip message.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> lib/s390x/snippet.h | 7 +++++++
> lib/s390x/uv.c | 20 ++++++++++++++++++++
> lib/s390x/uv.h | 1 +
> s390x/pv-diags.c | 8 +-------
> 4 files changed, 29 insertions(+), 7 deletions(-)
>
> diff --git a/lib/s390x/snippet.h b/lib/s390x/snippet.h
> index 57045994..11ec54c3 100644
> --- a/lib/s390x/snippet.h
> +++ b/lib/s390x/snippet.h
> @@ -30,6 +30,13 @@
> #define SNIPPET_HDR_LEN(type, file) \
> ((uintptr_t)SNIPPET_HDR_END(type, file) - (uintptr_t)SNIPPET_HDR_START(type, file))
>
> +/*
> + * Some of the UV memory needs to be allocated with >31 bit
> + * addresses which means we need a lot more memory than other
> + * tests.
> + */
> +#define SNIPPET_PV_MIN_MEM_SIZE (SZ_1M * 2200UL)
> +
> #define SNIPPET_PV_TWEAK0 0x42UL
> #define SNIPPET_PV_TWEAK1 0UL
> #define SNIPPET_UNPACK_OFF 0
> diff --git a/lib/s390x/uv.c b/lib/s390x/uv.c
> index 383271a5..db47536c 100644
> --- a/lib/s390x/uv.c
> +++ b/lib/s390x/uv.c
> @@ -18,6 +18,7 @@
> #include <asm/uv.h>
> #include <uv.h>
> #include <sie.h>
> +#include <snippet.h>
>
> static struct uv_cb_qui uvcb_qui = {
> .header.cmd = UVC_CMD_QUI,
> @@ -38,6 +39,25 @@ bool uv_os_is_host(void)
> return test_facility(158) && uv_query_test_call(BIT_UVC_CMD_INIT_UV);
> }
>
> +bool uv_guest_requirement_checks(void)
I would call it uv_host_requirement_checks since it will run on the
host to check if the host meets certain requirements
> +{
> + if (!test_facility(158)) {
> + report_skip("UV Call facility unavailable");
> + return false;
> + }
> + if (!sclp_facilities.has_sief2) {
> + report_skip("SIEF2 facility unavailable");
> + return false;
> + }
> + if (get_ram_size() < SNIPPET_PV_MIN_MEM_SIZE) {
> + report_skip("Not enough memory. This test needs about %ld MB of memory",
> + SNIPPET_PV_MIN_MEM_SIZE / 1024 / 1024);
a better way to do this would be to check the amount of memory needed
by the Ultravisor and check if that size + 2GB is available
of course in that case unittest.cfg would also need to be adjusted
> + return false;
> + }
> +
> + return true;
> +}
> +
> bool uv_query_test_call(unsigned int nr)
> {
> /* Query needs to be called first */
> diff --git a/lib/s390x/uv.h b/lib/s390x/uv.h
> index 78b979b7..d9af691a 100644
> --- a/lib/s390x/uv.h
> +++ b/lib/s390x/uv.h
> @@ -7,6 +7,7 @@
>
> bool uv_os_is_guest(void);
> bool uv_os_is_host(void);
> +bool uv_guest_requirement_checks(void);
> bool uv_query_test_call(unsigned int nr);
> const struct uv_cb_qui *uv_get_query_data(void);
> void uv_init(void);
> diff --git a/s390x/pv-diags.c b/s390x/pv-diags.c
> index fa4e5532..1289a571 100644
> --- a/s390x/pv-diags.c
> +++ b/s390x/pv-diags.c
> @@ -149,14 +149,8 @@ static void test_diag_yield(void)
> int main(void)
> {
> report_prefix_push("pv-diags");
> - if (!test_facility(158)) {
> - report_skip("UV Call facility unavailable");
> + if (!uv_guest_requirement_checks())
> goto done;
> - }
> - if (!sclp_facilities.has_sief2) {
> - report_skip("SIEF2 facility unavailable");
> - goto done;
> - }
>
> uv_setup_asces();
> snippet_setup_guest(&vm, true);
next prev parent reply other threads:[~2023-04-21 15:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 11:36 [kvm-unit-tests PATCH v3 0/7] s390x: Add PV SIE intercepts and ipl tests Janosch Frank
2023-04-21 11:36 ` [kvm-unit-tests PATCH v3 1/7] lib: s390x: uv: Introduce UV validity function Janosch Frank
2023-05-31 13:36 ` Nico Boehr
2023-04-21 11:36 ` [kvm-unit-tests PATCH v3 2/7] lib: s390x: uv: Add intercept data check library function Janosch Frank
2023-04-21 14:10 ` Claudio Imbrenda
2023-04-26 11:22 ` Nico Boehr
2023-04-21 11:36 ` [kvm-unit-tests PATCH v3 3/7] s390x: pv-diags: Drop snippet from snippet names Janosch Frank
2023-04-21 14:10 ` Claudio Imbrenda
2023-04-26 11:24 ` Nico Boehr
2023-04-21 11:36 ` [kvm-unit-tests PATCH v3 4/7] lib: s390x: uv: Add pv guest requirement check function Janosch Frank
2023-04-21 14:13 ` Claudio Imbrenda [this message]
2023-04-24 8:26 ` Janosch Frank
2023-04-26 11:27 ` Nico Boehr
2023-04-21 11:36 ` [kvm-unit-tests PATCH v3 5/7] s390x: pv: Add sie entry intercept and validity test Janosch Frank
2023-04-21 15:23 ` Claudio Imbrenda
2023-04-21 11:36 ` [kvm-unit-tests PATCH v3 6/7] s390x: pv: Add IPL reset tests Janosch Frank
2023-04-21 15:32 ` Claudio Imbrenda
2023-04-21 11:36 ` [kvm-unit-tests PATCH v3 7/7] s390x: pv-diags: Add the test to unittests.conf Janosch Frank
2023-04-21 14:10 ` Claudio Imbrenda
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=20230421161353.2dfaea97@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@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