From: Thomas Huth <thuth@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, imbrenda@linux.ibm.com,
david@redhat.com, seiden@linux.ibm.com, scgl@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v3 7/9] s390x: Add sthyi cc==0 r2+1 verification
Date: Thu, 7 Oct 2021 11:11:50 +0200 [thread overview]
Message-ID: <18a10bec-aee5-700f-9004-b4a200dcebed@redhat.com> (raw)
In-Reply-To: <20211007085027.13050-8-frankja@linux.ibm.com>
On 07/10/2021 10.50, Janosch Frank wrote:
> On success r2 + 1 should be 0, let's also check for that.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> s390x/sthyi.c | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/s390x/sthyi.c b/s390x/sthyi.c
> index db90b56f..4b153bf4 100644
> --- a/s390x/sthyi.c
> +++ b/s390x/sthyi.c
> @@ -24,16 +24,16 @@ static inline int sthyi(uint64_t vaddr, uint64_t fcode, uint64_t *rc,
> {
> register uint64_t code asm("0") = fcode;
> register uint64_t addr asm("2") = vaddr;
> - register uint64_t rc3 asm("3") = 0;
> + register uint64_t rc3 asm("3") = 42;
> int cc = 0;
>
> - asm volatile(".insn rre,0xB2560000,%[r1],%[r2]\n"
> - "ipm %[cc]\n"
> - "srl %[cc],28\n"
> - : [cc] "=d" (cc)
> - : [code] "d" (code), [addr] "a" (addr), [r1] "i" (r1),
> - [r2] "i" (r2)
> - : "memory", "cc", "r3");
> + asm volatile(
> + ".insn rre,0xB2560000,%[r1],%[r2]\n"
> + "ipm %[cc]\n"
> + "srl %[cc],28\n"
> + : [cc] "=d" (cc), "+d" (rc3)
> + : [code] "d" (code), [addr] "a" (addr), [r1] "i" (r1), [r2] "i" (r2)
> + : "memory", "cc");
> if (rc)
> *rc = rc3;
> return cc;
> @@ -139,16 +139,18 @@ static void test_fcode0(void)
> struct sthyi_hdr_sctn *hdr;
> struct sthyi_mach_sctn *mach;
> struct sthyi_par_sctn *par;
> + uint64_t rc = 42;
>
> /* Zero destination memory. */
> memset(pagebuf, 0, PAGE_SIZE);
>
> report_prefix_push("fcode 0");
> - sthyi((uint64_t)pagebuf, 0, NULL, 0, 2);
> + sthyi((uint64_t)pagebuf, 0, &rc, 0, 2);
> hdr = (void *)pagebuf;
> mach = (void *)pagebuf + hdr->INFMOFF;
> par = (void *)pagebuf + hdr->INFPOFF;
>
> + report(!rc, "r2 + 1 == 0");
Could you please check for "rc == CODE_SUCCES" (since we've got that for
this purpose)?
With that change:
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2021-10-07 9:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 8:50 [kvm-unit-tests PATCH v3 0/9] s390x: Cleanup and maintenance 2 Janosch Frank
2021-10-07 8:50 ` [kvm-unit-tests PATCH v3 1/9] s390x: uv: Tolerate 0x100 query return code Janosch Frank
2021-10-07 8:58 ` Thomas Huth
2021-10-07 8:50 ` [kvm-unit-tests PATCH v3 2/9] s390x: uv-host: Fence a destroy cpu test on z15 Janosch Frank
2021-10-07 8:50 ` [kvm-unit-tests PATCH v3 3/9] lib: s390x: uv: Fix share return value and print Janosch Frank
2021-10-07 8:50 ` [kvm-unit-tests PATCH v3 4/9] lib: s390x: uv: Add UVC_ERR_DEBUG switch Janosch Frank
2021-10-07 9:01 ` Thomas Huth
2021-10-13 14:14 ` Janosch Frank
2021-10-07 8:50 ` [kvm-unit-tests PATCH v3 5/9] lib: s390x: Add access key argument to tprot Janosch Frank
2021-10-07 9:05 ` Thomas Huth
2021-10-07 8:50 ` [kvm-unit-tests PATCH v3 6/9] lib: s390x: Print PGM code as hex Janosch Frank
2021-10-07 8:50 ` [kvm-unit-tests PATCH v3 7/9] s390x: Add sthyi cc==0 r2+1 verification Janosch Frank
2021-10-07 9:11 ` Thomas Huth [this message]
2021-10-07 10:51 ` Janosch Frank
2021-10-07 8:50 ` [kvm-unit-tests PATCH v3 8/9] s390x: snippets: Set stackptr and stacktop in cstart.S Janosch Frank
2021-10-07 9:13 ` Thomas Huth
2021-10-07 9:22 ` Janosch Frank
2021-10-07 8:50 ` [kvm-unit-tests PATCH v3 9/9] s390x: snippets: Define all things that are needed to link the lib Janosch Frank
2021-10-07 9:44 ` Thomas Huth
2021-10-07 10:44 ` Janosch Frank
2021-10-08 7:20 ` Thomas Huth
2021-10-08 8:13 ` 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=18a10bec-aee5-700f-9004-b4a200dcebed@redhat.com \
--to=thuth@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 \
--cc=seiden@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