diff options
| author | Catalin Marinas <catalin.marinas@arm.com> | 2014-12-10 14:02:09 +0300 |
|---|---|---|
| committer | Arnd Bergmann <arnd@arndb.de> | 2014-12-17 00:26:44 +0300 |
| commit | d6ad36913083d683aad4e02e53580c995f1a6ede (patch) | |
| tree | 5747e14cc4bdd26de3ef46b875f8c7f78c1b2cfe /drivers/clocksource/time-armada-370-xp.c | |
| parent | 5f1b2953da58e51e97eea9b7235545d72e9e1dab (diff) | |
| download | linux-d6ad36913083d683aad4e02e53580c995f1a6ede.tar.xz | |
clocksource: arch_timer: Only use the virtual counter (CNTVCT) on arm64
Commit 0b46b8a718c6 (clocksource: arch_timer: Fix code to use physical
timers when requested) introduces the use of physical counters in the
ARM architected timer driver. However, he arm64 kernel uses CNTVCT in
VDSO. When booting in EL2, the kernel switches to the physical timers to
make things easier for KVM but it continues to use the virtual counter
both in user and kernel. While in such scenario CNTVCT == CNTPCT (since
CNTVOFF is initialised by the kernel to 0), we want to spot firmware
bugs corrupting CNTVOFF early (which would affect CNTVCT).
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Tested-by: Yingjoe Chen <yingjoe.chen@mediatek.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'drivers/clocksource/time-armada-370-xp.c')
0 files changed, 0 insertions, 0 deletions