On 22.08.14 14:25, Peter Maydell wrote: > On 22 August 2014 13:12, Alexander Graf <ag...@suse.de> wrote: >> In Linux, the timer id is a "key" into a hash table that the kernel >> searches to find its timer. In QEMU it's an offset into an array. >> >> In both cases the syscall user receives it as a token from a create >> function and should treat it as opaque. >> >> So in the QEMU case it is unsigned, regardless of what the kernel allows >> it to be, because it's an array offset. > > It's a number between 0 and 32. That doesn't imply that it has > to be an unsigned variable, and we already have it in a > signed variable arg1...
Yes, so the end result will be the same. What's the point of this bike shedding? Alex
