All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, Alexandru Elisei <alexandru.elisei@arm.com>
Subject: [PULL kvm-unit-tests 04/10] arm64: timer: Add ISB before reading the counter value
Date: Thu,  6 Feb 2020 17:24:28 +0100	[thread overview]
Message-ID: <20200206162434.14624-5-drjones@redhat.com> (raw)
In-Reply-To: <20200206162434.14624-1-drjones@redhat.com>

From: Alexandru Elisei <alexandru.elisei@arm.com>

Reads of the physical counter and the virtual counter registers "can occur
speculatively and out of order relative to other instructions executed on
the same PE" [1, 2].

There is no theoretical limit to the number of instructions that the CPU
can reorder and we use the counter value to program the timer to fire in
the future. Add an ISB before reading the counter to make sure the read
instruction is not reordered too long in the past with regard to the
instruction that programs the timer alarm, thus causing the timer to fire
unexpectedly. This matches what Linux does (see
arch/arm64/include/asm/arch_timer.h).

Because we use the counter value to program the timer, we create a register
dependency [3] between the value that we read and the value that we write to
CVAL and thus we don't need a barrier after the read. Linux does things
differently because the read needs to be ordered with regard to a memory
load (more information in commit 75a19a0202db ("arm64: arch_timer: Ensure
counter register reads occur with seqlock held")).

This also matches what we already do in get_cntvct from
lib/arm{,64}/asm/processor.h.

[1] ARM DDI 0487E.a, section D11.2.1
[2] ARM DDI 0487E.a, section D11.2.2
[3] ARM DDI 0486E.a, section B2.3.2

Signed-off-by: Alexandru Elisei <alexandru.elisei@arm.com>
Signed-off-by: Andrew Jones <drjones@redhat.com>
---
 arm/timer.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arm/timer.c b/arm/timer.c
index c6ea108cfa4b..e758e84855c3 100644
--- a/arm/timer.c
+++ b/arm/timer.c
@@ -30,6 +30,7 @@ static void ptimer_unsupported_handler(struct pt_regs *regs, unsigned int esr)
 
 static u64 read_vtimer_counter(void)
 {
+	isb();
 	return read_sysreg(cntvct_el0);
 }
 
@@ -68,6 +69,7 @@ static void write_vtimer_ctl(u64 val)
 
 static u64 read_ptimer_counter(void)
 {
+	isb();
 	return read_sysreg(cntpct_el0);
 }
 
-- 
2.21.1


  parent reply	other threads:[~2020-02-06 16:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 16:24 [PULL kvm-unit-tests 00/10] arm/arm64: Various fixes Andrew Jones
2020-02-06 16:24 ` [PULL kvm-unit-tests 01/10] Makefile: Use no-stack-protector compiler options Andrew Jones
2020-02-06 16:24 ` [PULL kvm-unit-tests 02/10] arm/arm64: psci: Don't run C code without stack or vectors Andrew Jones
2020-02-06 16:24 ` [PULL kvm-unit-tests 03/10] arm64: timer: Add ISB after register writes Andrew Jones
2020-02-06 16:24 ` Andrew Jones [this message]
2020-02-06 16:24 ` [PULL kvm-unit-tests 05/10] arm64: timer: Make irq_received volatile Andrew Jones
2020-02-06 16:24 ` [PULL kvm-unit-tests 06/10] arm64: timer: EOIR the interrupt after masking the timer Andrew Jones
2020-02-06 16:24 ` [PULL kvm-unit-tests 07/10] arm64: timer: Wait for the GIC to sample timer interrupt state Andrew Jones
2020-02-06 16:24 ` [PULL kvm-unit-tests 08/10] arm64: timer: Check the " Andrew Jones
2020-02-06 16:24 ` [PULL kvm-unit-tests 09/10] arm64: timer: Test behavior when timer disabled or masked Andrew Jones
2020-02-06 16:24 ` [PULL kvm-unit-tests 10/10] arm/arm64: Perform dcache clean + invalidate after turning MMU off Andrew Jones
2020-03-17 12:10 ` [PULL kvm-unit-tests 00/10] arm/arm64: Various fixes Alexandru Elisei

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=20200206162434.14624-5-drjones@redhat.com \
    --to=drjones@redhat.com \
    --cc=alexandru.elisei@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.