target/riscv: Stop timer with infinite timecmp
PATCH 1/1 target/riscv: Stop timer with infinite timecmp
While the spec doesn't state it, setting timecmp to UINT64_MAX is another way to stop a timer, as it's considered setting the next timer event to occur at infinity. And, even if the time CSR does eventually reach UINT64_MAX, the very next tick will bring it back to zero, once again less than timecmp. For this reason riscv_timer_write_timecmp() special cases UINT64_MAX. However, if a previously set timecmp has not yet expired, then setting timecmp to UINT64_MAX to disable / stop it would not work, as the special case left the previous QEMU timer active, which would then still deliver an interrupt at that previous timecmp time. Ensure the stopped timer will not still deliver an interrupt by also deleting the QEMU timer in the UINT64_MAX special case.
--- target/riscv/time_helper.c | 1 + 1 file changed, 1 insertion(+)
target/riscv/time_helper.c +1 -0
@@ -92,6 +92,7 @@ void riscv_timer_write_timecmp(CPURISCVState *env, QEMUTimer *timer,* equals UINT64_MAX. */ if (timecmp ==UINT64_MAX ) { +timer_del (timer);return ; }
Signature · 1 line
2.45.2
Quoted 14 lines · Andrew Jones
While the spec doesn't state it, setting timecmp to
UINT64_MAXis another way to stop a timer, as it's considered setting the next timer event to occur at infinity. And, even if the time CSR does eventually reachUINT64_MAX, the very next tick will bring it back to zero, once again less than timecmp. For this reasonriscv_timer_write_timecmp()special casesUINT64_MAX. However, if a previously set timecmp has not yet expired, then setting timecmp toUINT64_MAXto disable / stop it would not work, as the special case left the previous QEMU timer active, which would then still deliver an interrupt at that previous timecmp time. Ensure the stopped timer will not still deliver an interrupt by also deleting the QEMU timer in theUINT64_MAXspecial case.
Quoted 2 lines
Fixes ae0edf2188b3 ("target/riscv: No need to re-start QEMU timer when timecmp == UINT64_MAX")Signed-off-by Andrew Jones <[email protected]>
Alistair
Quoted 20 lines
--- target/riscv/time_helper.c | 1 + 1 file changed, 1 insertion(+)target/riscv/time_helper.c +1
-1@@ -92,6 +92,7 @@ void riscv_timer_write_timecmp(CPURISCVState *env, QEMUTimer *timer,* equals UINT64_MAX. */ if (timecmp ==UINT64_MAX ) { +timer_del (timer);return ; } --2.45.2
Hi Andrew,
Quoted 3 lines · Andrew Jones
While the spec doesn't state it, setting timecmp to
UINT64_MAXis another way to stop a timer, as it's considered setting the next timer event to occur at infinity.
I think this should be explicitly stated in the spec, since some software may initially set time and timecmp to big values just to check how overflow is handled. And without it no chance that all HW implementations will interpret UINT64_MAX as 'stop timer'.
Do we need github issue on SSTC/privileged?
Thank you,
Vladimir Isaev
Quoted 29 lines
And, even if the time CSR does
eventually reachUINT64_MAX, the very next tick will bring it back to zero, once again less than timecmp. For this reasonriscv_timer_write_timecmp()special casesUINT64_MAX. However, if a previously set timecmp has not yet expired, then setting timecmp toUINT64_MAXto disable / stop it would not work, as the special case left the previous QEMU timer active, which would then still deliver an interrupt at that previous timecmp time. Ensure the stopped timer will not still deliver an interrupt by also deleting the QEMU timer in theUINT64_MAXspecial case.Fixes ae0edf2188b3 ("target/riscv: No need to re-start QEMU timer when timecmp == UINT64_MAX")Signed-off-by Andrew Jones <[email protected]>--- target/riscv/time_helper.c | 1 + 1 file changed, 1 insertion(+)target/riscv/time_helper.c +1
-0@@ -92,6 +92,7 @@ void riscv_timer_write_timecmp(CPURISCVState *env, QEMUTimer *timer,* equals UINT64_MAX. */ if (timecmp ==UINT64_MAX ) { +timer_del (timer);return ; }
Quoted 7 lines · Vladimir Isaev
Hi Andrew,
Quoted 3 lines · Andrew Jones
While the spec doesn't state it, setting timecmp to
UINT64_MAXis another way to stop a timer, as it's considered setting the next timer event to occur at infinity.
Quoted 6 lines
I think this should be explicitly stated in the spec, since some software may initially set time and timecmp to big values just to check how overflow is handled. And without it no chance that all HW implementations will interpret
UINT64_MAXas 'stop timer'.Do we need github issue on SSTC/privileged?
Hi Vladimir,
I don't think we need to update the spec, so hardware is free to make the interrupt pending if time ever reaches UINT64_MAX. However, the hardware will then need to clear the pending interrupt on the very next increment of time. This means even if the interrupt is raised it will most likely look spurious to the handler. I think we can leave this to software. If the software wants to use UINT64_MAX to stop timers, then it may also want to add a check in its timer handlers for timecmp == UINT64_MAX, and, under that condition, just ignore the interrupt.
Thanks,
drew
Quoted 36 lines
Thank you,
Vladimir IsaevQuoted 29 lines
And, even if the time CSR does
eventually reachUINT64_MAX, the very next tick will bring it back to zero, once again less than timecmp. For this reasonriscv_timer_write_timecmp()special casesUINT64_MAX. However, if a previously set timecmp has not yet expired, then setting timecmp toUINT64_MAXto disable / stop it would not work, as the special case left the previous QEMU timer active, which would then still deliver an interrupt at that previous timecmp time. Ensure the stopped timer will not still deliver an interrupt by also deleting the QEMU timer in theUINT64_MAXspecial case.Fixes ae0edf2188b3 ("target/riscv: No need to re-start QEMU timer when timecmp == UINT64_MAX")Signed-off-by Andrew Jones <[email protected]>--- target/riscv/time_helper.c | 1 + 1 file changed, 1 insertion(+)target/riscv/time_helper.c +1
-0@@ -92,6 +92,7 @@ void riscv_timer_write_timecmp(CPURISCVState *env, QEMUTimer *timer,* equals UINT64_MAX. */ if (timecmp ==UINT64_MAX ) { +timer_del (timer);return ; }
30.08.2024 17:50, Andrew Jones пишет:
Quoted 17 lines · Vladimir Isaev
Quoted 7 lines
Hi Andrew,
Quoted 3 lines · Andrew Jones
While the spec doesn't state it, setting timecmp to
UINT64_MAXis another way to stop a timer, as it's considered setting the next timer event to occur at infinity.Quoted 6 lines
I think this should be explicitly stated in the spec, since some software may initially set time and timecmp to big values just to check how overflow is handled. And without it no chance that all HW implementations will interpret
UINT64_MAXas 'stop timer'.Do we need github issue on SSTC/privileged?
Hi Vladimir,
Quoted 9 lines
I don't think we need to update the spec, so hardware is free to make the interrupt pending if time ever reaches
UINT64_MAX. However, the hardware will then need to clear the pending interrupt on the very next increment of time. This means even if the interrupt is raised it will most likely look spurious to the handler. I think we can leave this to software. If the software wants to useUINT64_MAXto stop timers, then it may also want to add a check in its timer handlers for timecmp ==UINT64_MAX, and, under that condition, just ignore the interrupt.
oh, I got it, thank you for explanation!
Quoted 39 lines
Thanks,
drewQuoted 36 lines
Thank you,
Vladimir IsaevQuoted 29 lines
And, even if the time CSR does
eventually reachUINT64_MAX, the very next tick will bring it back to zero, once again less than timecmp. For this reasonriscv_timer_write_timecmp()special casesUINT64_MAX. However, if a previously set timecmp has not yet expired, then setting timecmp toUINT64_MAXto disable / stop it would not work, as the special case left the previous QEMU timer active, which would then still deliver an interrupt at that previous timecmp time. Ensure the stopped timer will not still deliver an interrupt by also deleting the QEMU timer in theUINT64_MAXspecial case.Fixes ae0edf2188b3 ("target/riscv: No need to re-start QEMU timer when timecmp == UINT64_MAX")Signed-off-by Andrew Jones <[email protected]>--- target/riscv/time_helper.c | 1 + 1 file changed, 1 insertion(+)target/riscv/time_helper.c +1
-0@@ -92,6 +92,7 @@ void riscv_timer_write_timecmp(CPURISCVState *env, QEMUTimer *timer,* equals UINT64_MAX. */ if (timecmp ==UINT64_MAX ) { +timer_del (timer);return ; }
Alistair Francis
AppliedQuoted 14 lines · Andrew Jones
While the spec doesn't state it, setting timecmp to
UINT64_MAXis another way to stop a timer, as it's considered setting the next timer event to occur at infinity. And, even if the time CSR does eventually reachUINT64_MAX, the very next tick will bring it back to zero, once again less than timecmp. For this reasonriscv_timer_write_timecmp()special casesUINT64_MAX. However, if a previously set timecmp has not yet expired, then setting timecmp toUINT64_MAXto disable / stop it would not work, as the special case left the previous QEMU timer active, which would then still deliver an interrupt at that previous timecmp time. Ensure the stopped timer will not still deliver an interrupt by also deleting the QEMU timer in theUINT64_MAXspecial case.
Quoted 2 lines
Fixes ae0edf2188b3 ("target/riscv: No need to re-start QEMU timer when timecmp == UINT64_MAX")Signed-off-by Andrew Jones <[email protected]>
Thanks!
Applied to riscv-to-apply.next
Alistair
Quoted 20 lines
--- target/riscv/time_helper.c | 1 + 1 file changed, 1 insertion(+)target/riscv/time_helper.c +1
-1@@ -92,6 +92,7 @@ void riscv_timer_write_timecmp(CPURISCVState *env, QEMUTimer *timer,* equals UINT64_MAX. */ if (timecmp ==UINT64_MAX ) { +timer_del (timer);return ; } --2.45.2