From: Janosch Frank <frankja@linux.ibm.com>
To: Nina Schoetterl-Glausch <nsg@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: David Hildenbrand <david@redhat.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v2 1/3] s390x/spec_ex: Use PSW macro
Date: Thu, 23 Feb 2023 11:09:01 +0100 [thread overview]
Message-ID: <78be2778-9cc8-e635-4eee-0b833e515110@linux.ibm.com> (raw)
In-Reply-To: <20230221174822.1378667-2-nsg@linux.ibm.com>
On 2/21/23 18:48, Nina Schoetterl-Glausch wrote:
> Replace explicit psw definition by PSW macro.
> No functional change intended.
>
> Signed-off-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> ---
> s390x/spec_ex.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/s390x/spec_ex.c b/s390x/spec_ex.c
> index 42ecaed3..2adc5996 100644
> --- a/s390x/spec_ex.c
> +++ b/s390x/spec_ex.c
> @@ -105,10 +105,7 @@ static int check_invalid_psw(void)
> /* For normal PSWs bit 12 has to be 0 to be a valid PSW*/
> static int psw_bit_12_is_1(void)
> {
> - struct psw invalid = {
> - .mask = BIT(63 - 12),
> - .addr = 0x00000000deadbeee
> - };
> + struct psw invalid = PSW(BIT(63 - 12), 0x00000000deadbeee);
I think we've passed the point where we can use a constant for the short
psw. But we can convert that at a later time, I'll add it to the TODO
list, so:
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
next prev parent reply other threads:[~2023-02-23 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230221174822.1378667-1-nsg@linux.ibm.com>
2023-02-21 17:48 ` [kvm-unit-tests PATCH v2 1/3] s390x/spec_ex: Use PSW macro Nina Schoetterl-Glausch
2023-02-21 17:50 ` Nina Schoetterl-Glausch
2023-02-23 10:09 ` Janosch Frank [this message]
2023-02-21 17:48 ` [kvm-unit-tests PATCH v2 2/3] s390x/spec_ex: Add test introducing odd address into PSW Nina Schoetterl-Glausch
2023-03-14 15:21 ` Claudio Imbrenda
2023-03-15 13:48 ` Nina Schoetterl-Glausch
2023-02-21 17:48 ` [kvm-unit-tests PATCH v2 3/3] s390x/spec_ex: Add test of EXECUTE with odd target address Nina Schoetterl-Glausch
2023-03-14 15:25 ` Claudio Imbrenda
2023-03-14 16:41 ` Nina Schoetterl-Glausch
2023-03-14 17:12 ` Claudio Imbrenda
2023-03-14 17:59 ` Nina Schoetterl-Glausch
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=78be2778-9cc8-e635-4eee-0b833e515110@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=nsg@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