From: David Hildenbrand <david@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 3/4] s390x: Move stsi to library
Date: Wed, 21 Aug 2019 15:27:12 +0200 [thread overview]
Message-ID: <3a5cc77f-8b2b-269e-3939-3280287b470a@redhat.com> (raw)
In-Reply-To: <20190821104736.1470-4-frankja@linux.ibm.com>
On 21.08.19 12:47, Janosch Frank wrote:
> It's needed in multiple tests now.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> lib/s390x/asm/arch_def.h | 16 ++++++++++++++++
> s390x/skey.c | 18 ------------------
> 2 files changed, 16 insertions(+), 18 deletions(-)
>
> diff --git a/lib/s390x/asm/arch_def.h b/lib/s390x/asm/arch_def.h
> index 4bbb428..5f8f45e 100644
> --- a/lib/s390x/asm/arch_def.h
> +++ b/lib/s390x/asm/arch_def.h
> @@ -240,4 +240,20 @@ static inline void enter_pstate(void)
> load_psw_mask(mask);
> }
>
> +static inline int stsi(void *addr, int fc, int sel1, int sel2)
> +{
> + register int r0 asm("0") = (fc << 28) | sel1;
> + register int r1 asm("1") = sel2;
> + int cc;
> +
> + asm volatile(
> + "stsi 0(%3)\n"
> + "ipm %[cc]\n"
> + "srl %[cc],28\n"
> + : "+d" (r0), [cc] "=d" (cc)
> + : "d" (r1), "a" (addr)
> + : "cc", "memory");
> + return cc;
> +}
> +
> #endif
> diff --git a/s390x/skey.c b/s390x/skey.c
> index b1e11af..fd4fcc7 100644
> --- a/s390x/skey.c
> +++ b/s390x/skey.c
> @@ -70,24 +70,6 @@ static void test_set(void)
> skey.str.acc == ret.str.acc && skey.str.fp == ret.str.fp);
> }
>
> -static inline int stsi(void *addr, int fc, int sel1, int sel2)
> -{
> - register int r0 asm("0") = (fc << 28) | sel1;
> - register int r1 asm("1") = sel2;
> - int rc = 0;
> -
> - asm volatile(
> - " stsi 0(%3)\n"
> - " jz 0f\n"
> - " lhi %1,-1\n"
> - "0:\n"
> - : "+d" (r0), "+d" (rc)
> - : "d" (r1), "a" (addr)
> - : "cc", "memory");
> -
> - return rc;
> -}
> -
> /* Returns true if we are running under z/VM 6.x */
> static bool check_for_zvm6(void)
> {
>
You don't simply move, you also modify and change the return value from
o/-1 to cc. AFAIKs, this should be fine.
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-08-21 13:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 10:47 [kvm-unit-tests PATCH v2 0/4] s390x: More emulation tests Janosch Frank
2019-08-21 10:47 ` [kvm-unit-tests PATCH v2 1/4] s390x: Support PSW restart boot Janosch Frank
2019-08-21 13:23 ` David Hildenbrand
2019-08-23 10:31 ` David Hildenbrand
2019-08-21 10:47 ` [kvm-unit-tests PATCH v2 2/4] s390x: Diag288 test Janosch Frank
2019-08-23 10:30 ` Thomas Huth
2019-08-21 10:47 ` [kvm-unit-tests PATCH v2 3/4] s390x: Move stsi to library Janosch Frank
2019-08-21 13:27 ` David Hildenbrand [this message]
2019-08-23 10:34 ` Thomas Huth
2019-08-21 10:47 ` [kvm-unit-tests PATCH v2 4/4] s390x: STSI tests Janosch Frank
2019-08-23 10:57 ` Thomas Huth
2019-08-23 11:16 ` Janosch Frank
2019-08-22 11:11 ` [kvm-unit-tests PATCH] s390x: Add diag308 subcode 0 testing Janosch Frank
2019-08-23 11:00 ` David Hildenbrand
2019-08-23 11:33 ` Janosch Frank
2019-08-23 11:36 ` David Hildenbrand
2019-08-23 14:12 ` Thomas Huth
2019-08-23 14:41 ` 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=3a5cc77f-8b2b-269e-3939-3280287b470a@redhat.com \
--to=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).