From: "Andreas Färber" <andreas.faerber@web.de>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>, Stefan Weil <sw@weilnetz.de>,
Anthony Liguori <anthony@codemonkey.ws>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] qemu_rearm_alarm_timer: do not call rearm if the next deadline is INT64_MAX
Date: Tue, 12 Jun 2012 10:35:30 +0200 [thread overview]
Message-ID: <4FD6FF52.9030001@web.de> (raw)
In-Reply-To: <4FD6FCCE.8080807@web.de>
Am 12.06.2012 10:24, schrieb Andreas Färber:
> Am 29.05.2012 15:35, schrieb Stefano Stabellini:
> The check-qtest-i386 qemu-system-i386 process now hangs at ~98% CPU,
> just as with my INT64_MAX hack before. How would I best debug this qtest
> scenario, and what should I be looking for? Since my 1.1 patch this is
> no longer going through any Cocoa event handling, so the only causes I
> can think of are timers and signals...
Might this shed any light?
Analysis of sampling qemu-system-i386 (pid 19531) every 1 millisecond
Call graph:
2337 Thread_2503
2337 0xffc
2337 start
2337 main
2337 qemu_main
2337 main_loop_wait
2337 qemu_iohandler_poll
2337 tcp_chr_read
2337 qtest_read
2337 memory_region_iorange_write
2337 rtc_change_mon_event
2337 monitor_protocol_event
2337 monitor_json_emitter
2337 monitor_puts
2337 monitor_flush
2177 write
2177 write
92 send_all
81 cerror
57 malloc_zone_malloc
35 __error
35 __error
17 dyld_stub___error
17 dyld_stub___error
5 cthread_set_errno_self
5 cthread_set_errno_self
24 cerror
11 send_all
36 dyld_stub_write
36 dyld_stub_write
24 dyld_stub___error
24 dyld_stub___error
6 cerror
6 cerror
2 __error
2 __error
2337 Thread_2603
2337 _pthread_start
2337 sigwait_compat
2337 sigwait
2337 __sigwait
2337 __sigwait
2337 Thread_2703
2337 _pthread_start
2337 qemu_dummy_cpu_thread_fn
2337 sigwait
2337 __sigwait
2337 __sigwait
rtc-test is still blocked by the system() call apparently, and gtester
is polling in its main loop.
Andreas
next prev parent reply other threads:[~2012-06-12 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1205291426350.26786@kaball-desktop>
[not found] ` <4FC502CE.20509@weilnetz.de>
[not found] ` <4FC53AAD.3010201@redhat.com>
[not found] ` <4FC5888D.5080902@codemonkey.ws>
2012-06-11 9:55 ` [Qemu-devel] [PATCH 1.1?] qemu_rearm_alarm_timer: do not call rearm if the next deadline is INT64_MAX Stefano Stabellini
2012-06-11 10:12 ` Andreas Färber
2012-06-12 8:24 ` [Qemu-devel] " Andreas Färber
2012-06-12 8:35 ` Andreas Färber [this message]
2012-06-12 12:37 ` Stefano Stabellini
2012-06-12 12:58 ` Andreas Färber
2012-06-12 13:32 ` Stefano Stabellini
2012-07-27 17:00 ` Andreas Färber
2012-08-09 15:35 ` [Qemu-devel] [Qemu-devel for-1.2] " Andreas Färber
2012-08-09 19:58 ` Blue Swirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FD6FF52.9030001@web.de \
--to=andreas.faerber@web.de \
--cc=anthony@codemonkey.ws \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=sw@weilnetz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.