From: Thomas Huth <thuth@redhat.com>
To: Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH] s390x: Add specification exception test
Date: Wed, 21 Jul 2021 15:26:53 +0200 [thread overview]
Message-ID: <18803632-6a9c-5999-2a8a-d4501a0a77d8@redhat.com> (raw)
In-Reply-To: <20210706115459.372749-1-scgl@linux.ibm.com>
On 06/07/2021 13.54, Janis Schoetterl-Glausch wrote:
> Generate specification exceptions and check that they occur.
> Also generate specification exceptions during a transaction,
> which results in another interruption code.
> With the iterations argument one can check if specification
> exception interpretation occurs, e.g. by using a high value and
> checking that the debugfs counters are substantially lower.
> The argument is also useful for estimating the performance benefit
> of interpretation.
>
> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
> ---
> s390x/Makefile | 1 +
> lib/s390x/asm/arch_def.h | 1 +
> s390x/spec_ex.c | 344 +++++++++++++++++++++++++++++++++++++++
> s390x/unittests.cfg | 3 +
> 4 files changed, 349 insertions(+)
> create mode 100644 s390x/spec_ex.c
>
> diff --git a/s390x/Makefile b/s390x/Makefile
> index 8820e99..be100d3 100644
> --- a/s390x/Makefile
> +++ b/s390x/Makefile
> @@ -23,6 +23,7 @@ tests += $(TEST_DIR)/sie.elf
> tests += $(TEST_DIR)/mvpg.elf
> tests += $(TEST_DIR)/uv-host.elf
> tests += $(TEST_DIR)/edat.elf
> +tests += $(TEST_DIR)/spec_ex.elf
>
> tests_binary = $(patsubst %.elf,%.bin,$(tests))
> ifneq ($(HOST_KEY_DOCUMENT),)
> diff --git a/lib/s390x/asm/arch_def.h b/lib/s390x/asm/arch_def.h
> index 15cf7d4..7cb0b92 100644
> --- a/lib/s390x/asm/arch_def.h
> +++ b/lib/s390x/asm/arch_def.h
> @@ -229,6 +229,7 @@ static inline uint64_t stctg(int cr)
> return value;
> }
>
> +#define CTL0_TRANSACT_EX_CTL (63 - 8)
> #define CTL0_LOW_ADDR_PROT (63 - 35)
> #define CTL0_EDAT (63 - 40)
> #define CTL0_IEP (63 - 43)
> diff --git a/s390x/spec_ex.c b/s390x/spec_ex.c
> new file mode 100644
> index 0000000..2e05bfb
> --- /dev/null
> +++ b/s390x/spec_ex.c
> @@ -0,0 +1,344 @@
Please add a short comment header at the top of the file with some
information on what it is all about, and license information (e.g. a
SPDX-License-Identifier)
> +#include <stdlib.h>
> +#include <htmintrin.h>
> +#include <libcflat.h>
> +#include <asm/barrier.h>
> +#include <asm/interrupt.h>
> +#include <asm/facility.h>
> +
> +struct lowcore *lc = (struct lowcore *) 0;
> +
> +static bool expect_early;
> +static struct psw expected_early_pgm_psw;
> +static struct psw fixup_early_pgm_psw;
> +
> +static void fixup_early_pgm_ex(void)
Could you please add a comment in front of this function with a description
why this is required / good for?
> +{
> + if (expect_early) {
> + report(expected_early_pgm_psw.mask == lc->pgm_old_psw.mask
> + && expected_early_pgm_psw.addr == lc->pgm_old_psw.addr,
> + "Early program new PSW as expected");
> + expect_early = false;
> + }
> + lc->pgm_old_psw = fixup_early_pgm_psw;
> +}
> +
> +static void lpsw(uint64_t psw)
> +{
> + uint32_t *high, *low;
> + uint64_t r0 = 0, r1 = 0;
> +
> + high = (uint32_t *) &fixup_early_pgm_psw.mask;
> + low = high + 1;
> +
> + asm volatile (
> + " epsw %0,%1\n"
> + " st %0,%[high]\n"
> + " st %1,%[low]\n"
What's all this magic with high and low good for? Looks like high and low
are not used afterwards anymore?
> + " larl %0,nop%=\n"
> + " stg %0,%[addr]\n"
> + " lpsw %[psw]\n"
> + "nop%=: nop\n"
> + : "+&r"(r0), "+&a"(r1), [high] "=&R"(*high), [low] "=&R"(*low)
... also not sure why you need the "&" modifiers here?
> + , [addr] "=&R"(fixup_early_pgm_psw.addr)
> + : [psw] "Q"(psw)
> + : "cc", "memory"
> + );
> +}
> +
> +static void psw_bit_31_32_are_1_0(void)
> +{
> + uint64_t bad_psw = 0x000800015eadbeef;
> +
> + //bit 12 gets inverted when extending to 128-bit PSW
I'd prefer a space after the "//"
> + expected_early_pgm_psw.mask = 0x0000000100000000;
> + expected_early_pgm_psw.addr = 0x000000005eadbeef;
> + expect_early = true;
> + lpsw(bad_psw);
> +}
> +
> +static void bad_alignment(void)
> +{
> + uint32_t words[5] = {0, 0, 0};
> + uint32_t (*bad_aligned)[4];
> +
> + register uint64_t r1 asm("6");
> + register uint64_t r2 asm("7");
> + if (((uintptr_t)&words[0]) & 0xf) {
> + bad_aligned = (uint32_t (*)[4])&words[0];
> + } else {
> + bad_aligned = (uint32_t (*)[4])&words[1];
> + }
> + asm volatile ("lpq %0,%2"
> + : "=r"(r1), "=r"(r2)
> + : "T"(*bad_aligned)
> + );
> +}
> +
> +static void not_even(void)
> +{
> + uint64_t quad[2];
> +
> + register uint64_t r1 asm("7");
> + register uint64_t r2 asm("8");
> + asm volatile (".insn rxy,0xe3000000008f,%0,%2" //lpq %0,%2
> + : "=r"(r1), "=r"(r2)
> + : "T"(quad)
> + );
> +}
> +
> +struct spec_ex_trigger {
> + const char *name;
> + void (*func)(void);
> + bool transactable;
> + void (*fixup)(void);
> +};
> +
> +static const struct spec_ex_trigger spec_ex_triggers[] = {
> + { "psw_bit_31_32_are_1_0", &psw_bit_31_32_are_1_0, false, &fixup_early_pgm_ex},
> + { "bad_alignment", &bad_alignment, true, NULL},
> + { "not_even", ¬_even, true, NULL},
> + { NULL, NULL, true, NULL},
> +};
> +
> +struct args {
> + uint64_t iterations;
> + uint64_t max_retries;
> + uint64_t suppress_info;
> + uint64_t max_failures;
> + bool diagnose;
> +};
> +
> +static void test_spec_ex(struct args *args,
> + const struct spec_ex_trigger *trigger)
> +{
> + uint16_t expected_pgm = PGM_INT_CODE_SPECIFICATION;
> + uint16_t pgm;
> + unsigned int i;
> +
> + register_pgm_cleanup_func(trigger->fixup);
> + for (i = 0; i < args->iterations; i++) {
> + expect_pgm_int();
> + trigger->func();
> + pgm = clear_pgm_int();
> + if (pgm != expected_pgm) {
> + report(0,
> + "Program interrupt: expected(%d) == received(%d)",
> + expected_pgm,
> + pgm);
> + return;
> + }
> + }
Maybe it would be nice to "unregister" the cleanup function at the end with
register_pgm_cleanup_func(NULL) ?
> + report(1,
> + "Program interrupt: always expected(%d) == received(%d)",
> + expected_pgm,
> + expected_pgm);
> +}
> +
> +#define TRANSACTION_COMPLETED 4
> +#define TRANSACTION_MAX_RETRIES 5
> +
> +static int __attribute__((nonnull))
Not sure whether that attribute makes much sense with a static function? ...
the compiler has information about the implementation details here, so it
should be able to see that e.g. trigger must be non-NULL anyway?
> +with_transaction(void (*trigger)(void), struct __htm_tdb *diagnose)
> +{
> + int cc;
> +
> + cc = __builtin_tbegin(diagnose);
> + if (cc == _HTM_TBEGIN_STARTED) {
> + trigger();
> + __builtin_tend();
> + return -TRANSACTION_COMPLETED;
> + } else {
> + return -cc;
> + }
> +}
[...]
Thomas
next prev parent reply other threads:[~2021-07-21 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 11:54 [kvm-unit-tests PATCH] s390x: Add specification exception test Janis Schoetterl-Glausch
2021-07-09 9:22 ` Cornelia Huck
2021-07-09 14:22 ` Janis Schoetterl-Glausch
2021-07-27 12:26 ` Janosch Frank
2021-07-21 13:26 ` Thomas Huth [this message]
2021-07-21 15:44 ` Janis Schoetterl-Glausch
2021-07-22 7:33 ` Thomas Huth
2021-07-27 12:28 ` 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=18803632-6a9c-5999-2a8a-d4501a0a77d8@redhat.com \
--to=thuth@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=scgl@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).