From: Janosch Frank <frankja@linux.ibm.com>
To: Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v6 1/2] s390x: Add specification exception test
Date: Mon, 26 Sep 2022 09:59:27 +0200 [thread overview]
Message-ID: <08831aac-ecaa-9cc4-3900-2b0049eec910@linux.ibm.com> (raw)
In-Reply-To: <20220826161112.3786131-2-scgl@linux.ibm.com>
On 8/26/22 18:11, Janis Schoetterl-Glausch wrote:
> Generate specification exceptions and check that they occur.
>
> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
Minor issues below, apart from that:
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> s390x/Makefile | 1 +
> lib/s390x/asm/arch_def.h | 5 +
> s390x/spec_ex.c | 194 +++++++++++++++++++++++++++++++++++++++
> s390x/unittests.cfg | 3 +
> 4 files changed, 203 insertions(+)
> create mode 100644 s390x/spec_ex.c
>
> diff --git a/s390x/Makefile b/s390x/Makefile
> index efd5e0c1..58b1bf54 100644
> --- a/s390x/Makefile
> +++ b/s390x/Makefile
> @@ -27,6 +27,7 @@ tests += $(TEST_DIR)/uv-host.elf
> tests += $(TEST_DIR)/edat.elf
> tests += $(TEST_DIR)/mvpg-sie.elf
> tests += $(TEST_DIR)/spec_ex-sie.elf
> +tests += $(TEST_DIR)/spec_ex.elf
> tests += $(TEST_DIR)/firq.elf
> tests += $(TEST_DIR)/epsw.elf
> tests += $(TEST_DIR)/adtl-status.elf
> diff --git a/lib/s390x/asm/arch_def.h b/lib/s390x/asm/arch_def.h
> index e7ae454b..b6e60fb0 100644
> --- a/lib/s390x/asm/arch_def.h
> +++ b/lib/s390x/asm/arch_def.h
> @@ -41,6 +41,11 @@ struct psw {
> uint64_t addr;
> };
>
> +struct short_psw {
> + uint32_t mask;
> + uint32_t addr;
> +};
> +
> struct cpu {
> struct lowcore *lowcore;
> uint64_t *stack;
> diff --git a/s390x/spec_ex.c b/s390x/spec_ex.c
> new file mode 100644
> index 00000000..68469e4b
> --- /dev/null
> +++ b/s390x/spec_ex.c
> @@ -0,0 +1,194 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright IBM Corp. 2021, 2022
> + *
> + * Specification exception test.
> + * Tests that specification exceptions occur when expected.
> + *
> + * Can be extended by adding triggers to spec_ex_triggers, see comments below.
> + */
> +#include <stdlib.h>
> +#include <libcflat.h>
> +#include <bitops.h>
> +#include <asm/interrupt.h>
> +
> +/* toggled to signal occurrence of invalid psw fixup */
> +static bool invalid_psw_expected;
> +static struct psw expected_psw;
> +static struct psw invalid_psw;
> +static struct psw fixup_psw;
> +
> +/*
> + * The standard program exception handler cannot deal with invalid old PSWs,
> + * especially not invalid instruction addresses, as in that case one cannot
> + * find the instruction following the faulting one from the old PSW.
> + * The PSW to return to is set by load_psw.
> + */
> +static void fixup_invalid_psw(struct stack_frame_int *stack)
> +{
> + /* signal occurrence of invalid psw fixup */
> + invalid_psw_expected = false;
Hmmmm (TM), assert(invalid_psw_expected) ?
> + invalid_psw = lowcore.pgm_old_psw;
> + lowcore.pgm_old_psw = fixup_psw;
> +}
> +
> +/*
> + * Load possibly invalid psw, but setup fixup_psw before,
> + * so that fixup_invalid_psw() can bring us back onto the right track.
> + * Also acts as compiler barrier, -> none required in expect/check_invalid_psw
> + */
> +static void load_psw(struct psw psw)
> +{
> + uint64_t scratch;
> +
> + /*
> + * The fixup psw is current psw with the instruction address replaced by
is the current psw
> + * the address of the nop following the instruction loading the new psw. > + */
> + fixup_psw.mask = extract_psw_mask();
> + asm volatile ( "larl %[scratch],0f\n"
> + " stg %[scratch],%[fixup_addr]\n"
> + " lpswe %[psw]\n"
> + "0: nop\n"
> + : [scratch] "=&d" (scratch),
> + [fixup_addr] "=&T" (fixup_psw.addr)
> + : [psw] "Q" (psw)
> + : "cc", "memory"
> + );
> +}
> +
> +static void load_short_psw(struct short_psw psw)
> +{
> + uint64_t scratch;
> +
> + fixup_psw.mask = extract_psw_mask();
> + asm volatile ( "larl %[scratch],0f\n"
> + " stg %[scratch],%[fixup_addr]\n"
> + " lpsw %[psw]\n"
> + "0: nop\n"
> + : [scratch] "=&d" (scratch),
> + [fixup_addr] "=&T" (fixup_psw.addr)
> + : [psw] "Q" (psw)
> + : "cc", "memory"
> + );
> +}
> +
> +static void expect_invalid_psw(struct psw psw)
> +{
> + expected_psw = psw;
> + invalid_psw_expected = true;
> +}
> +
> +static int check_invalid_psw(void)
> +{
/* Since the fixup sets this to false we check for false here. */
> + if (!invalid_psw_expected) {
> + if (expected_psw.mask == invalid_psw.mask &&
> + expected_psw.addr == invalid_psw.addr)
> + return 0;
> + report_fail("Wrong invalid PSW");
> + } else {
> + report_fail("Expected exception due to invalid PSW");
> + }
> + return 1;
> +}
> +
next prev parent reply other threads:[~2022-09-26 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 16:11 [kvm-unit-tests PATCH v6 0/2] Add specification exception tests Janis Schoetterl-Glausch
2022-08-26 16:11 ` [kvm-unit-tests PATCH v6 1/2] s390x: Add specification exception test Janis Schoetterl-Glausch
2022-08-30 14:34 ` Nico Boehr
2022-08-30 15:16 ` Janis Schoetterl-Glausch
2022-09-26 7:59 ` Janosch Frank [this message]
2022-08-26 16:11 ` [kvm-unit-tests PATCH v6 2/2] s390x: Test specification exceptions during transaction Janis Schoetterl-Glausch
2022-09-01 14:59 ` Nico Boehr
2022-09-01 16:08 ` Janis Schoetterl-Glausch
2022-09-05 7:10 ` Nico Boehr
2022-09-26 13:18 ` 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=08831aac-ecaa-9cc4-3900-2b0049eec910@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=scgl@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