Am 28.05.2012 22:15, schrieb Paolo Bonzini:
> Il 28/05/2012 21:40, Andreas Färber ha scritto:
>> I'm seeing qemu-timer.c:unix_rearm_timer()'s setitimer() abort with
>> EINVAL during `make check` on both platforms. The value of
>> nearest_delta_ns appears to be INT64_MAX. Is this expected? Is it
>>
Il 29/05/2012 14:01, Stefano Stabellini ha scritto:
> On Mon, 28 May 2012, Paolo Bonzini wrote:
>> Il 28/05/2012 21:40, Andreas Färber ha scritto:
>>> I'm seeing qemu-timer.c:unix_rearm_timer()'s setitimer() abort with
>>> EINVAL during `make check` on both platforms. The value of
>>> nearest_delta
On Mon, 28 May 2012, Paolo Bonzini wrote:
> Il 28/05/2012 21:40, Andreas Färber ha scritto:
> > I'm seeing qemu-timer.c:unix_rearm_timer()'s setitimer() abort with
> > EINVAL during `make check` on both platforms. The value of
> > nearest_delta_ns appears to be INT64_MAX. Is this expected? Is it
>
Il 28/05/2012 21:40, Andreas Färber ha scritto:
> I'm seeing qemu-timer.c:unix_rearm_timer()'s setitimer() abort with
> EINVAL during `make check` on both platforms. The value of
> nearest_delta_ns appears to be INT64_MAX. Is this expected? Is it
> possible that this value is too large for it_value
Hello,
I'm seeing qemu-timer.c:unix_rearm_timer()'s setitimer() abort with
EINVAL during `make check` on both platforms. The value of
nearest_delta_ns appears to be INT64_MAX. Is this expected? Is it
possible that this value is too large for it_value on some platforms?
Apple's man page mentions th
