Re: [PULL 26/38] linux-user: Don't assume 0 is not a valid host timer_t value

2022-09-28 Thread Peter Maydell
On Wed, 28 Sept 2022 at 09:23, Jon Alduan wrote: > > Hello Laurent, hello Peter, > > I see the Maximum number of active timers ist still 32. I hope it is not too > late, but for my application this is not enough. Could this define be bigger > i.e. 32*4? This is a separate issue from the "0 ID v

Re: [PULL 26/38] linux-user: Don't assume 0 is not a valid host timer_t value

2022-09-28 Thread Jon Alduan
Hello Laurent, hello Peter, I see the Maximum number of active timers ist still 32. I hope it is not too late, but for my application this is not enough. Could this define be bigger i.e. 32*4? Thanks for your support! I really appreciate it! Jon Laurent Vivier igorleak hau idatzi zuen (2022 ir

[PULL 26/38] linux-user: Don't assume 0 is not a valid host timer_t value

2022-09-28 Thread Laurent Vivier
From: Peter Maydell For handling guest POSIX timers, we currently use an array g_posix_timers[], whose entries are a host timer_t value, or 0 for "this slot is unused". When the guest calls the timer_create syscall we look through the array for a slot containing 0, and use that for the new timer