From: Janosch Frank <frankja@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>, imbrenda@linux.ibm.com, thuth@redhat.com
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v3 1/6] lib: s390x: introduce bitfield for PSW mask
Date: Thu, 1 Jun 2023 09:42:48 +0200 [thread overview]
Message-ID: <3667d7af-f9ba-fbb6-537d-e6143f63ac43@linux.ibm.com> (raw)
In-Reply-To: <20230601070202.152094-2-nrb@linux.ibm.com>
On 6/1/23 09:01, Nico Boehr wrote:
> Changing the PSW mask is currently little clumsy, since there is only the
> PSW_MASK_* defines. This makes it hard to change e.g. only the address
> space in the current PSW without a lot of bit fiddling.
>
> Introduce a bitfield for the PSW mask. This makes this kind of
> modifications much simpler and easier to read.
>
> Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
> ---
> lib/s390x/asm/arch_def.h | 25 ++++++++++++++++++++++++-
> s390x/selftest.c | 40 ++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 64 insertions(+), 1 deletion(-)
>
> diff --git a/lib/s390x/asm/arch_def.h b/lib/s390x/asm/arch_def.h
> index bb26e008cc68..84f6996c4d8c 100644
> --- a/lib/s390x/asm/arch_def.h
> +++ b/lib/s390x/asm/arch_def.h
> @@ -37,12 +37,35 @@ struct stack_frame_int {
> };
>
> struct psw {
> - uint64_t mask;
> + union {
> + uint64_t mask;
> + struct {
> + uint8_t reserved00:1;
> + uint8_t per:1;
> + uint8_t reserved02:3;
> + uint8_t dat:1;
> + uint8_t io:1;
> + uint8_t ext:1;
> + uint8_t key:4;
> + uint8_t reserved12:1;
> + uint8_t mchk:1;
> + uint8_t wait:1;
> + uint8_t pstate:1;
> + uint8_t as:2;
> + uint8_t cc:2;
> + uint8_t prg_mask:4;
> + uint8_t reserved24:7;
> + uint8_t ea:1;
> + uint8_t ba:1;
> + uint32_t reserved33:31;
Hrm, since I already made the mistake of introducing bitfields with and
without spaces between the ":" I'm in no position to complain here.
I'm also not sure what the consensus is.
> + };
> + };
> uint64_t addr;
> };
I've come to like static asserts for huge structs and bitfields since
they can safe you from a *lot* of headaches.
>
> #define PSW(m, a) ((struct psw){ .mask = (m), .addr = (uint64_t)(a) })
>
> +
Whitespace damage
> struct short_psw {
> uint32_t mask;
> uint32_t addr;
> diff --git a/s390x/selftest.c b/s390x/selftest.c
> index 13fd36bc06f8..8d81ba312279 100644
> --- a/s390x/selftest.c
> +++ b/s390x/selftest.c
> @@ -74,6 +74,45 @@ static void test_malloc(void)
> report_prefix_pop();
> }
>
> +static void test_psw_mask(void)
> +{
> + uint64_t expected_key = 0xF;
We're using lowercase chars for hex constants
> + struct psw test_psw = PSW(0, 0);
> +
> + report_prefix_push("PSW mask");
> + test_psw.dat = 1;
> + report(test_psw.mask == PSW_MASK_DAT, "DAT matches expected=0x%016lx actual=0x%016lx", PSW_MASK_DAT, test_psw.mask);
> +
> + test_psw.mask = 0;
> + test_psw.io = 1;
> + report(test_psw.mask == PSW_MASK_IO, "IO matches expected=0x%016lx actual=0x%016lx", PSW_MASK_IO, test_psw.mask);
> +
> + test_psw.mask = 0;
> + test_psw.ext = 1;
> + report(test_psw.mask == PSW_MASK_EXT, "EXT matches expected=0x%016lx actual=0x%016lx", PSW_MASK_EXT, test_psw.mask);
> +
> + test_psw.mask = expected_key << (63 - 11);
> + report(test_psw.key == expected_key, "PSW Key matches expected=0x%lx actual=0x%x", expected_key, test_psw.key);
> +
> + test_psw.mask = 1UL << (63 - 13);
> + report(test_psw.mchk, "MCHK matches");
> +
> + test_psw.mask = 0;
> + test_psw.wait = 1;
> + report(test_psw.mask == PSW_MASK_WAIT, "Wait matches expected=0x%016lx actual=0x%016lx", PSW_MASK_WAIT, test_psw.mask);
> +
> + test_psw.mask = 0;
> + test_psw.pstate = 1;
> + report(test_psw.mask == PSW_MASK_PSTATE, "Pstate matches expected=0x%016lx actual=0x%016lx", PSW_MASK_PSTATE, test_psw.mask);
> +
> + test_psw.mask = 0;
> + test_psw.ea = 1;
> + test_psw.ba = 1;
> + report(test_psw.mask == PSW_MASK_64, "BA/EA matches expected=0x%016lx actual=0x%016lx", PSW_MASK_64, test_psw.mask);
> +
> + report_prefix_pop();
> +}
> +
> int main(int argc, char**argv)
> {
> report_prefix_push("selftest");
> @@ -89,6 +128,7 @@ int main(int argc, char**argv)
> test_fp();
> test_pgm_int();
> test_malloc();
> + test_psw_mask();
>
> return report_summary();
> }
next prev parent reply other threads:[~2023-06-01 7:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 7:01 [kvm-unit-tests PATCH v3 0/6] s390x: Add support for running guests without MSO/MSL Nico Boehr
2023-06-01 7:01 ` [kvm-unit-tests PATCH v3 1/6] lib: s390x: introduce bitfield for PSW mask Nico Boehr
2023-06-01 7:42 ` Janosch Frank [this message]
2023-06-05 10:35 ` Claudio Imbrenda
2023-06-05 14:23 ` Janosch Frank
2023-06-07 15:56 ` Nico Boehr
2023-06-07 16:19 ` Claudio Imbrenda
2023-06-01 7:01 ` [kvm-unit-tests PATCH v3 2/6] s390x: add function to set DAT mode for all interrupts Nico Boehr
2023-06-05 8:42 ` Janosch Frank
2023-06-15 12:44 ` Nico Boehr
2023-06-01 7:01 ` [kvm-unit-tests PATCH v3 3/6] s390x: sie: switch to home space mode before entering SIE Nico Boehr
2023-06-05 9:03 ` Janosch Frank
2023-06-15 13:09 ` Nico Boehr
2023-06-01 7:02 ` [kvm-unit-tests PATCH v3 4/6] s390x: lib: don't forward PSW when handling exception in SIE Nico Boehr
2023-06-05 9:11 ` Janosch Frank
2023-06-05 10:42 ` Claudio Imbrenda
2023-06-01 7:02 ` [kvm-unit-tests PATCH v3 5/6] s390x: lib: sie: don't reenter SIE on pgm int Nico Boehr
2023-06-05 9:30 ` Janosch Frank
2023-06-05 10:44 ` Claudio Imbrenda
2023-06-30 14:59 ` Nico Boehr
2023-06-30 15:04 ` Janosch Frank
2023-06-30 15:53 ` Claudio Imbrenda
2023-06-01 7:02 ` [kvm-unit-tests PATCH v3 6/6] s390x: add a test for SIE without MSO/MSL Nico Boehr
2023-06-05 9:57 ` Janosch Frank
2023-07-10 14:29 ` Nico Boehr
2023-07-10 15:05 ` 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=3667d7af-f9ba-fbb6-537d-e6143f63ac43@linux.ibm.com \
--to=frankja@linux.ibm.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