On 16 April 2018 at 16:29, Alex Bennée wrote:
>
> Peter Maydell writes:
>> CNTVCT_EL0 isn't much use without CNTFRQ_EL0 which tells
>> you how fast it ticks...
>
> I've added it but of course:
>
> /* Note that CNTFRQ is purely reads-as-written for the benefit
> * of software; writing it
Peter Maydell writes:
> On 16 April 2018 at 15:03, Alex Bennée wrote:
>> Since kernel commit a86bd139f2 (arm64: arch_timer: Enable CNTVCT_EL0
>> trap..) user-space has been able to read this system register. This
>> patch enables access to that register although currently it always
>> returns 0
On 16 April 2018 at 15:03, Alex Bennée wrote:
> Since kernel commit a86bd139f2 (arm64: arch_timer: Enable CNTVCT_EL0
> trap..) user-space has been able to read this system register. This
> patch enables access to that register although currently it always
> returns 0 as we don't yet have a mechani
Since kernel commit a86bd139f2 (arm64: arch_timer: Enable CNTVCT_EL0
trap..) user-space has been able to read this system register. This
patch enables access to that register although currently it always
returns 0 as we don't yet have a mechanism for managing timers in
linux-user mode.
Signed-off-
