From: Kevin Wolf <kwolf@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
qemu block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] bug introduced by "block: Move throttling fields from BDS to BB"
Date: Mon, 17 Oct 2016 13:18:26 +0200 [thread overview]
Message-ID: <20161017111826.GD4821@noname.redhat.com> (raw)
In-Reply-To: <w51r37fs6ll.fsf@maestria.local.igalia.com>
Am 17.10.2016 um 10:49 hat Alberto Garcia geschrieben:
> On Fri 14 Oct 2016 04:11:46 PM CEST, Paolo Bonzini wrote:
> > Here is next_throttle_token:
> >
> > - ThrottleGroup *tg = container_of(blk_bs(blk)->throttle_state,
> > - ThrottleGroup, ts);
> > + BlockBackendPublic *blkp = blk_get_public(blk);
> > + ThrottleGroup *tg = container_of(blkp->throttle_state, ThrottleGroup, ts);
> > BlockBackend *token, *start;
> >
> > start = token = tg->tokens[is_write];
> >
> > /* get next bs round in round robin style */
> > token = throttle_group_next_blk(token);
> > - while (token != start && !blk_bs(token)->pending_reqs[is_write]) {
> > + while (token != start && !blkp->pending_reqs[is_write]) {
> > token = throttle_group_next_blk(token);
> > }
> >
> >
> > blkp isn't updated every time token is updated.
>
> You're right, I'll write a patch. I'd also try to check why this was not
> detected by any iotest.
>
> Thanks!
Thanks a lot, Berto! (Both for fixing my bug and thinking of test cases)
Kevin
prev parent reply other threads:[~2016-10-17 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 14:11 [Qemu-devel] bug introduced by "block: Move throttling fields from BDS to BB" Paolo Bonzini
2016-10-14 19:29 ` Paolo Bonzini
2016-10-17 8:49 ` Alberto Garcia
2016-10-17 11:18 ` Kevin Wolf [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=20161017111826.GD4821@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).