From: Eric Auger <eric.auger@redhat.com>
To: eric.auger.pro@gmail.com, eric.auger@redhat.com, maz@kernel.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: drjones@redhat.com, andrew.murray@arm.com,
andre.przywara@arm.com, peter.maydell@linaro.org,
alexandru.elisei@arm.com
Subject: [kvm-unit-tests PATCH 01/10] arm64: Provide read/write_sysreg_s
Date: Mon, 16 Dec 2019 21:47:48 +0100 [thread overview]
Message-ID: <20191216204757.4020-2-eric.auger@redhat.com> (raw)
In-Reply-To: <20191216204757.4020-1-eric.auger@redhat.com>
From: Andrew Jones <drjones@redhat.com>
Sometimes we need to test access to system registers which are
missing assembler mnemonics.
Signed-off-by: Andrew Jones <drjones@redhat.com>
Reviewed-by: Alexandru Elisei <alexandru.elisei@arm.com>
---
lib/arm64/asm/sysreg.h | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/lib/arm64/asm/sysreg.h b/lib/arm64/asm/sysreg.h
index a03830b..a45eebd 100644
--- a/lib/arm64/asm/sysreg.h
+++ b/lib/arm64/asm/sysreg.h
@@ -38,6 +38,17 @@
asm volatile("msr " xstr(r) ", %x0" : : "rZ" (__val)); \
} while (0)
+#define read_sysreg_s(r) ({ \
+ u64 __val; \
+ asm volatile("mrs_s %0, " xstr(r) : "=r" (__val)); \
+ __val; \
+})
+
+#define write_sysreg_s(v, r) do { \
+ u64 __val = (u64)v; \
+ asm volatile("msr_s " xstr(r) ", %x0" : : "rZ" (__val));\
+} while (0)
+
asm(
" .irp num,0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30\n"
" .equ .L__reg_num_x\\num, \\num\n"
--
2.20.1
next prev parent reply other threads:[~2019-12-16 20:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 20:47 [kvm-unit-tests PATCH 00/10] KVM: arm64: PMUv3 Event Counter Tests Eric Auger
2019-12-16 20:47 ` Eric Auger [this message]
2019-12-16 20:47 ` [kvm-unit-tests PATCH 02/10] arm: pmu: Let pmu tests take a sub-test parameter Eric Auger
2020-01-03 18:09 ` Andre Przywara
2019-12-16 20:47 ` [kvm-unit-tests PATCH 03/10] arm: pmu: Add a pmu struct Eric Auger
2020-01-03 18:12 ` Andre Przywara
2019-12-16 20:47 ` [kvm-unit-tests PATCH 04/10] arm: pmu: Check Required Event Support Eric Auger
2020-01-03 18:12 ` Andre Przywara
2020-01-09 16:54 ` Auger Eric
2020-01-09 17:30 ` André Przywara
2020-01-09 17:37 ` Auger Eric
2019-12-16 20:47 ` [kvm-unit-tests PATCH 05/10] arm: pmu: Basic event counter Tests Eric Auger
2020-01-07 12:19 ` Andre Przywara
2020-01-09 21:38 ` Auger Eric
2019-12-16 20:47 ` [kvm-unit-tests PATCH 06/10] arm: pmu: Test chained counter Eric Auger
2019-12-16 20:47 ` [kvm-unit-tests PATCH 07/10] arm: pmu: test 32-bit <-> 64-bit transitions Eric Auger
2019-12-16 20:47 ` [kvm-unit-tests PATCH 08/10] arm: gic: Provide per-IRQ helper functions Eric Auger
2019-12-16 20:47 ` [kvm-unit-tests PATCH 09/10] arm/arm64: gic: Introduce setup_irq() helper Eric Auger
2019-12-16 20:47 ` [kvm-unit-tests PATCH 10/10] arm: pmu: Test overflow interrupts Eric Auger
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=20191216204757.4020-2-eric.auger@redhat.com \
--to=eric.auger@redhat.com \
--cc=alexandru.elisei@arm.com \
--cc=andre.przywara@arm.com \
--cc=andrew.murray@arm.com \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maz@kernel.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).