Re: [qemu-arm-static] timer_delete issue from Qemu 5.0.0 onwards

[Jon Alduan]

Here you have the output with the debug logs:

next_free_host_timer: returning 0
timer_create: host timer_create: returned 0x00000000, set phtimer 0x559dc5d8aa00 to (nil)
timer_create: wrote 0xcaf0000 to guest address 0x408002e8

Create timer 0 536880
get_timer_id: guest timer id 0xcaf0000 -> index 0
next_free_host_timer: returning 0
timer_create: host timer_create: returned 0x00000000, set phtimer 0x559dc5d8aa00 to 0x1
timer_create: wrote 0xcaf0000 to guest address 0x408002e8
Create timer 1 537928
get_timer_id: guest timer id 0xcaf0000 -> index 0
next_free_host_timer: returning 1

So, it does create two different timers, but second one will be addressed as being first one?

...

El jue, 21 jul 2022 a las 16:52, Peter Maydell (<peter.maydell@linaro.org>) escribió:

On Thu, 21 Jul 2022 at 14:44, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Thu, 21 Jul 2022 at 14:10, Jon Alduan <jon.alduan@gmail.com> wrote:
> > Yes, exactly. When removing timer 0, time 1 will be removed instead.
> > Other timers are not affected. If you create a dummy timer 0, there
> > are no more problems (that I can address).
>
> Yeah, but it's complicated, because there are multiple "timer IDs" here:

I've attached a patch which adds some debug printing to QEMU's
timer_create/timer_delete code. Could you please apply this patch,
rebuild QEMU, run that with the test program, and send me the
output ?

thanks
-- PMM

--

j.A

testTimer_peter_patch_debug_output.log
Description: Binary data