From: Kevin Wolf <kwolf@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-block@nongnu.org, qemu-stable@nongnu.org,
qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/2] block: allow flush on devices with open tray
Date: Fri, 16 Sep 2016 10:33:04 +0200 [thread overview]
Message-ID: <20160916083304.GD4633@noname.redhat.com> (raw)
In-Reply-To: <1473982972-8884-1-git-send-email-jsnow@redhat.com>
Am 16.09.2016 um 01:42 hat John Snow geschrieben:
> One more try.
>
> The move to blk_flush altered the behavior of migration and flushing
> nodes that are not reachable via the guest, but are still reachable
> via QEMU and may or may not need to be flushed.
>
> This is likely the simplest solution for now until we nail down our
> policy a bit more.
>
> This is intended for 2.6.2 and/or 2.7.1, to fix problems with libvirt
> et al being unable to migrate QEMU when the CDROM tray is open.
>
> v3:
> Trying to take a hint from Kevin, reinstating bdrv_flush_all.
> If it's not what we want, we can try moving back to v2,
> acknowledging that a nicer solution in the future:
> (A) Can skip flushing on devices that just don't need it, and
> (B) Optionally institutes some sort of flush-on-eject policy.
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
The only part that I'm not completely happy with are the commit messages
because there is a theme of "bypassing checks" in there. That's not
really what happens because the requests don't come from something
attached to the BlockBackends in the first place, and it also completely
ignores the case of BDSes that aren't currently attached to any BB and
are fixed by these changes as well.
Anyway, that's a minor problem as long as the code is right.
Kevin
next prev parent reply other threads:[~2016-09-16 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 23:42 [Qemu-devel] [PATCH v3 0/2] block: allow flush on devices with open tray John Snow
2016-09-15 23:42 ` [Qemu-devel] [PATCH v3 1/2] block: reintroduce bdrv_flush_all John Snow
2016-09-15 23:42 ` [Qemu-devel] [PATCH v3 2/2] qemu: use bdrv_flush_all for vm_stop et al John Snow
2016-09-16 16:17 ` John Snow
2016-09-19 8:01 ` Kevin Wolf
2016-09-16 0:06 ` [Qemu-devel] [PATCH v3 0/2] block: allow flush on devices with open tray Paolo Bonzini
2016-09-16 0:09 ` John Snow
2016-09-16 0:10 ` Paolo Bonzini
2016-09-16 8:33 ` Kevin Wolf [this message]
2016-09-16 15:59 ` John Snow
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=20160916083304.GD4633@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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.