From: Paolo Bonzini <pbonzini@redhat.com>
To: Alberto Garcia <berto@igalia.com>, Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block/throttle: Use host clock type
Date: Fri, 13 Mar 2015 13:28:38 +0100 [thread overview]
Message-ID: <5502D7F6.8020902@redhat.com> (raw)
In-Reply-To: <20150313122329.GA9419@igalia.com>
On 13/03/2015 13:23, Alberto Garcia wrote:
> On Fri, Mar 13, 2015 at 02:35:29PM +0800, Fam Zheng wrote:
>
>> Throttle timers won't make any progress when VCPU is not running,
>> which is prone to stall the request queue in cases like utils,
>> qtest, suspending, and live migration, unless carefully handled.
>
> Yes, this can be easily reproduced by stopping the VM and starting a
> block-commit job. If the I/O in that device is throttled then the job
> will be stalled.
That may be a different bug. Should jobs be subject to throttling at all?
Paolo
> Then there's also the situation that we discussed in IRC: if the
> block-commit job is ongoing and then we stop the VM, then the rest of
> the data will be committed bypassing the throttling settings. But
> that's not related to these changes.
>
>> Signed-off-by: Fam Zheng <famz@redhat.com>
>> ---
>> block.c | 2 +-
>> tests/test-throttle.c | 14 +++++++-------
>> 2 files changed, 8 insertions(+), 8 deletions(-)
>
> Reviewed-By: Alberto Garcia <berto@igalia.com>
>
> Berto
>
>
next prev parent reply other threads:[~2015-03-13 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 6:35 [Qemu-devel] [PATCH] block/throttle: Use host clock type Fam Zheng
2015-03-13 8:08 ` Paolo Bonzini
2015-03-13 8:27 ` Fam Zheng
2015-03-13 11:09 ` Paolo Bonzini
2015-03-13 11:43 ` Fam Zheng
2015-03-13 12:23 ` Alberto Garcia
2015-03-13 12:28 ` Paolo Bonzini [this message]
2015-03-16 2:15 ` Fam Zheng
2015-03-16 15:18 ` Kevin Wolf
2015-03-16 16:08 ` Kevin Wolf
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=5502D7F6.8020902@redhat.com \
--to=pbonzini@redhat.com \
--cc=berto@igalia.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@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).