From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
thuth@redhat.com, david@redhat.com, nsg@linux.ibm.com,
nrb@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v2 2/5] lib: s390x: uv: Dirty CC before uvc execution
Date: Wed, 31 Jan 2024 12:50:41 +0100 [thread overview]
Message-ID: <20240131125041.5abff114@p-imbrenda> (raw)
In-Reply-To: <20240131074427.70871-3-frankja@linux.ibm.com>
On Wed, 31 Jan 2024 07:44:24 +0000
Janosch Frank <frankja@linux.ibm.com> wrote:
> Dirtying the CC allows us to find missing CC changes.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> lib/s390x/asm/uv.h | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/lib/s390x/asm/uv.h b/lib/s390x/asm/uv.h
> index e9fb19af..611dcd3f 100644
> --- a/lib/s390x/asm/uv.h
> +++ b/lib/s390x/asm/uv.h
> @@ -216,14 +216,16 @@ struct uv_cb_ssc {
>
> static inline int uv_call_once(unsigned long r1, unsigned long r2)
> {
> + uint64_t bogus_cc = 1;
> int cc;
>
> asm volatile(
> + " tmll %[bogus_cc],3\n"
> "0: .insn rrf,0xB9A40000,%[r1],%[r2],0,0\n"
> " ipm %[cc]\n"
> " srl %[cc],28\n"
> : [cc] "=d" (cc)
> - : [r1] "a" (r1), [r2] "a" (r2)
> + : [r1] "a" (r1), [r2] "a" (r2), [bogus_cc] "d" (bogus_cc)
> : "memory", "cc");
>
> if (UVC_ERR_DEBUG && cc == 1)
next prev parent reply other threads:[~2024-01-31 11:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 7:44 [kvm-unit-tests PATCH v2 0/5] s390x: Dirty cc before executing tested instructions Janosch Frank
2024-01-31 7:44 ` [kvm-unit-tests PATCH v2 1/5] lib: s390x: sigp: Dirty CC before sigp execution Janosch Frank
2024-01-31 11:56 ` Claudio Imbrenda
2024-01-31 14:16 ` Janosch Frank
2024-01-31 7:44 ` [kvm-unit-tests PATCH v2 2/5] lib: s390x: uv: Dirty CC before uvc execution Janosch Frank
2024-01-31 11:50 ` Claudio Imbrenda [this message]
2024-01-31 7:44 ` [kvm-unit-tests PATCH v2 3/5] lib: s390x: css: Dirty CC before css instructions Janosch Frank
2024-01-31 7:44 ` [kvm-unit-tests PATCH v2 4/5] s390x: mvpg: Dirty CC before mvpg execution Janosch Frank
2024-01-31 7:44 ` [kvm-unit-tests PATCH v2 5/5] s390x: sclp: Dirty CC before sclp execution Janosch Frank
2024-02-01 17:49 ` [kvm-unit-tests PATCH v2 0/5] s390x: Dirty cc before executing tested instructions Claudio Imbrenda
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=20240131125041.5abff114@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--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