There exists a simple patch that changes the wait loop timer to use
CLOCK_MONOTONIC. See
https://github.com/portante/qemu/commit/35c92daa9784882153c6d8b0e15e8c8f181d6e8a
.
-peter
On Tue, Mar 27, 2012 at 12:00 PM, Jan Kiszka wrote:
> On 2012-03-27 17:52, Paolo Bonzini wrote:
> > Il 27/03/2012 17
Il 24/03/2012 17:26, Lee Essen ha scritto:
> Dynticks was limited to linux. This patch adds Solaris support
> and ensures a CLOCK_HIGHRES clock is used which is the optimal
> setup for Solaris systems.
Looks good, but I would prefer if you tested for timer_create in
configure and use #ifdef CONFIG
On 2012-03-27 17:52, Paolo Bonzini wrote:
> Il 27/03/2012 17:08, Jan Kiszka ha scritto:
+#if defined(__sun__)
+if (timer_create(CLOCK_HIGHRES, &ev, &host_timer)) {
+#else
if (timer_create(CLOCK_REALTIME, &ev, &host_timer)) {
+#endif
>>>
>>> This should be #ifdef CL
Il 27/03/2012 17:08, Jan Kiszka ha scritto:
>>> +#if defined(__sun__)
>>> +if (timer_create(CLOCK_HIGHRES, &ev, &host_timer)) {
>>> +#else
>>> if (timer_create(CLOCK_REALTIME, &ev, &host_timer)) {
>>> +#endif
>>
>> This should be #ifdef CLOCK_HIGHRES.
>
> Are we sure about this is and wil
On 2012-03-27 17:01, Paolo Bonzini wrote:
> Il 24/03/2012 17:26, Lee Essen ha scritto:
>> Dynticks was limited to linux. This patch adds Solaris support
>> and ensures a CLOCK_HIGHRES clock is used which is the optimal
>> setup for Solaris systems.
>
> Looks good, but I would prefer if you tested
Dynticks was limited to linux. This patch adds Solaris support
and ensures a CLOCK_HIGHRES clock is used which is the optimal
setup for Solaris systems.
Signed-off-by: Lee Essen
---
qemu-timer.c | 14 +-
1 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/qemu-timer.c b/
