From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, thuth@redhat.com, david@redhat.com,
borntraeger@de.ibm.com, frankja@linux.ibm.com
Subject: [kvm-unit-tests PATCH v5 3/4] s390x: lib: add SPX and STPX instruction wrapper
Date: Wed, 8 Jan 2020 17:13:16 +0100 [thread overview]
Message-ID: <20200108161317.268928-4-imbrenda@linux.ibm.com> (raw)
In-Reply-To: <20200108161317.268928-1-imbrenda@linux.ibm.com>
Add a wrapper for the SET PREFIX and STORE PREFIX instructions, and
use it instead of using inline assembly everywhere.
Signed-off-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
---
lib/s390x/asm/arch_def.h | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/lib/s390x/asm/arch_def.h b/lib/s390x/asm/arch_def.h
index 1a5e3c6..38c9dfa 100644
--- a/lib/s390x/asm/arch_def.h
+++ b/lib/s390x/asm/arch_def.h
@@ -284,4 +284,17 @@ static inline int servc(uint32_t command, unsigned long sccb)
return cc;
}
+static inline void spx(uint32_t new_prefix)
+{
+ asm volatile("spx %0" : : "Q" (new_prefix) : "memory");
+}
+
+static inline uint32_t stpx(void)
+{
+ uint32_t prefix;
+
+ asm volatile("stpx %0" : "=Q" (prefix));
+ return prefix;
+}
+
#endif
--
2.24.1
next prev parent reply other threads:[~2020-01-08 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 16:13 [kvm-unit-tests PATCH v5 0/4] s390x: SCLP Unit test Claudio Imbrenda
2020-01-08 16:13 ` [kvm-unit-tests PATCH v5 1/4] s390x: export sclp_setup_int Claudio Imbrenda
2020-01-08 16:13 ` [kvm-unit-tests PATCH v5 2/4] s390x: sclp: add service call instruction wrapper Claudio Imbrenda
2020-01-08 16:13 ` Claudio Imbrenda [this message]
2020-01-08 18:58 ` [kvm-unit-tests PATCH v5 3/4] s390x: lib: add SPX and STPX " Thomas Huth
2020-01-09 11:36 ` Claudio Imbrenda
2020-01-09 12:55 ` Thomas Huth
2020-01-08 16:13 ` [kvm-unit-tests PATCH v5 4/4] s390x: SCLP unit test Claudio Imbrenda
2020-01-09 12:42 ` Thomas Huth
2020-01-09 13:29 ` 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=20200108161317.268928-4-imbrenda@linux.ibm.com \
--to=imbrenda@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=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).