From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel mailing list <qemu-devel@nongnu.org>
Subject: [Qemu-devel] dyntick timer stall
Date: Sat, 19 Jul 2008 11:13:08 +0200 [thread overview]
Message-ID: <fb249edb0807190213t4ae30c60yf5c2b23377f43c11@mail.gmail.com> (raw)
With dyntick enabled I see qemu-system-arm lock up after a while (stay
in code_gen_buffer) due to no more signals reaching qemu. This happens
after a couple of seconds of constantly rearming the host timer with
250usec period (MIN_TIMER_REARM_US).
The offender is audio which, if the QEMU_AUDIO_TIMER_PERIOD env
variable is unset, requests audio_timer() be called every 1 vm_clock
tick, resulting in a negative period in qemu_next_deadline_dyntick
which is then trimmed to MIN_TIMER_REARM_US. It seems to be a problem
in host's timer_settime() though.
timer_settime is constantly called with 250usec as parameter without
the timeout having passed, and then after it's called for the last
time, no signal arrives in the main thread for at least a couple of
minutes. The host is x86_64 Linux 2.6, what may be causing this and
what may be a fix?
Regards
next reply other threads:[~2008-07-19 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 9:13 andrzej zaborowski [this message]
2008-07-19 10:20 ` [Qemu-devel] Re: dyntick timer stall Jan Kiszka
2008-07-19 12:55 ` andrzej zaborowski
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=fb249edb0807190213t4ae30c60yf5c2b23377f43c11@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).