From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, imbrenda@linux.ibm.com,
thuth@redhat.com, david@redhat.com, nsg@linux.ibm.com,
nrb@linux.ibm.com
Subject: [kvm-unit-tests PATCH v2 3/5] lib: s390x: css: Dirty CC before css instructions
Date: Wed, 31 Jan 2024 07:44:25 +0000 [thread overview]
Message-ID: <20240131074427.70871-4-frankja@linux.ibm.com> (raw)
In-Reply-To: <20240131074427.70871-1-frankja@linux.ibm.com>
Dirtying the CC allows us to find missing CC changes when css
instructions are emulated.
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
---
lib/s390x/css.h | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/lib/s390x/css.h b/lib/s390x/css.h
index 0a19324b..504b3f14 100644
--- a/lib/s390x/css.h
+++ b/lib/s390x/css.h
@@ -147,14 +147,16 @@ static inline int ssch(unsigned long schid, struct orb *addr)
static inline int stsch(unsigned long schid, struct schib *addr)
{
register unsigned long reg1 asm ("1") = schid;
+ uint64_t bogus_cc = 1;
int cc;
asm volatile(
+ " tmll %[bogus_cc],3\n"
" stsch 0(%3)\n"
" ipm %0\n"
" srl %0,28"
: "=d" (cc), "=m" (*addr)
- : "d" (reg1), "a" (addr)
+ : "d" (reg1), "a" (addr), [bogus_cc] "d" (bogus_cc)
: "cc");
return cc;
}
@@ -177,14 +179,16 @@ static inline int msch(unsigned long schid, struct schib *addr)
static inline int tsch(unsigned long schid, struct irb *addr)
{
register unsigned long reg1 asm ("1") = schid;
+ uint64_t bogus_cc = 2;
int cc;
asm volatile(
+ " tmll %[bogus_cc],3\n"
" tsch 0(%3)\n"
" ipm %0\n"
" srl %0,28"
: "=d" (cc), "=m" (*addr)
- : "d" (reg1), "a" (addr)
+ : "d" (reg1), "a" (addr), [bogus_cc] "d" (bogus_cc)
: "cc");
return cc;
}
@@ -252,28 +256,32 @@ static inline int rsch(unsigned long schid)
static inline int rchp(unsigned long chpid)
{
register unsigned long reg1 asm("1") = chpid;
+ uint64_t bogus_cc = 1;
int cc;
asm volatile(
+ " tmll %[bogus_cc],3\n"
" rchp\n"
" ipm %0\n"
" srl %0,28"
: "=d" (cc)
- : "d" (reg1)
+ : "d" (reg1), [bogus_cc] "d" (bogus_cc)
: "cc");
return cc;
}
static inline int stcrw(uint32_t *crw)
{
+ uint64_t bogus_cc = 1;
int cc;
asm volatile(
+ " tmll %[bogus_cc],3\n"
" stcrw %[crw]\n"
" ipm %[cc]\n"
" srl %[cc],28"
: [cc] "=d" (cc)
- : [crw] "Q" (*crw)
+ : [crw] "Q" (*crw), [bogus_cc] "d" (bogus_cc)
: "cc", "memory");
return cc;
}
--
2.40.1
next prev parent reply other threads:[~2024-01-31 7:44 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
2024-01-31 7:44 ` Janosch Frank [this message]
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=20240131074427.70871-4-frankja@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=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