From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qtest: Fix deadloop by running main loop AIO context's timers
Date: Mon, 19 Jan 2015 17:48:08 +0800 [thread overview]
Message-ID: <20150119094808.GA3763@ad.nay.redhat.com> (raw)
In-Reply-To: <54BCCE7A.1050506@redhat.com>
On Mon, 01/19 10:29, Paolo Bonzini wrote:
>
>
> On 16/01/2015 09:01, Fam Zheng wrote:
> > qemu_clock_run_timers() only takes care of main_loop_tlg, we shouldn't
> > forget aio timer list groups.
> >
> > Currently, the qemu_clock_deadline_ns_all (a few lines above) counts all
> > the timergroups of this clock type, including aio tlg, but we don't fire
> > them, so they are never cleared, which makes a dead loop.
> >
> > For example, this function hangs when trying to drive throttled block
> > request queue with qtest clock_step.
> >
> > Signed-off-by: Fam Zheng <famz@redhat.com>
> > ---
> > cpus.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/cpus.c b/cpus.c
> > index 3a5323b..dd7e595 100644
> > --- a/cpus.c
> > +++ b/cpus.c
> > @@ -387,6 +387,7 @@ void qtest_clock_warp(int64_t dest)
> > seqlock_write_unlock(&timers_state.vm_clock_seqlock);
> >
> > qemu_clock_run_timers(QEMU_CLOCK_VIRTUAL);
> > + timerlistgroup_run_timers(&qemu_get_aio_context()->tlg);
>
> Good catch. However, I think it's enough to run the QEMU_CLOCK_VIRTUAL
> events, using timerlist_run_timers.
OK, will fix!
Fam
prev parent reply other threads:[~2015-01-19 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 8:01 [Qemu-devel] [PATCH] qtest: Fix deadloop by running main loop AIO context's timers Fam Zheng
2015-01-16 13:26 ` Stefan Hajnoczi
2015-01-19 9:29 ` Paolo Bonzini
2015-01-19 9:48 ` Fam Zheng [this message]
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=20150119094808.GA3763@ad.nay.redhat.com \
--to=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@redhat.com \
/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).