qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: pbonzini@redhat.com, stefanha@redhat.com, qemu-devel@nongnu.org,
	qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 00/12] block: Protect nested event loop with bdrv_drained_begin and bdrv_drained_end
Date: Wed, 21 Oct 2015 09:18:05 +0800	[thread overview]
Message-ID: <20151021011805.GA639@ad.usersys.redhat.com> (raw)
In-Reply-To: <20151020141727.GB30615@noname>

On Tue, 10/20 16:17, Kevin Wolf wrote:
> Am 20.10.2015 um 07:16 hat Fam Zheng geschrieben:
> > v4: Rebase on to master so fix the "bdrv_move_feature_fields" issue.
> > 
> > v3: Call bdrv_drain unconditionally in bdrv_drained_begin.
> >     Document the internal I/O implications between bdrv_drain_begin and end.
> > 
> > The nested aio_poll()'s in block layer has a bug that new r/w requests from
> > ioeventfds and nbd exports are processed, which might break the caller's
> > semantics (qmp_transaction) or even pointers (bdrv_reopen).
> 
> This series conflicts with the first part of Max' "BlockBackend and
> media" series which I already merged to my tree. I tried to resolve the
> conflict while applying, but while it doesn't seem really hard to do,
> it's a bit more involved than what I'm willing to do while applying.
> 
> So I'm afraid I have to request another rebase.

Sure, thanks for taking a look!

Fam

      reply	other threads:[~2015-10-21  1:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  5:16 [Qemu-devel] [PATCH v4 00/12] block: Protect nested event loop with bdrv_drained_begin and bdrv_drained_end Fam Zheng
2015-10-20  5:16 ` [Qemu-devel] [PATCH v4 01/12] aio: Add "is_external" flag for event handlers Fam Zheng
2015-10-20  5:16 ` [Qemu-devel] [PATCH v4 02/12] nbd: Mark fd handlers client type as "external" Fam Zheng
2015-10-20  5:16 ` [Qemu-devel] [PATCH v4 03/12] dataplane: Mark host notifiers' " Fam Zheng
2015-10-20  5:16 ` [Qemu-devel] [PATCH v4 04/12] aio: introduce aio_{disable, enable}_external Fam Zheng
2015-10-20  5:16 ` [Qemu-devel] [PATCH v4 05/12] block: Introduce "drained begin/end" API Fam Zheng
2015-10-20  5:16 ` [Qemu-devel] [PATCH v4 06/12] block: Add "drained begin/end" for transactional external snapshot Fam Zheng
2015-10-20  5:16 ` [Qemu-devel] [PATCH v4 07/12] block: Add "drained begin/end" for transactional backup Fam Zheng
2015-10-20  5:16 ` [Qemu-devel] [PATCH v4 08/12] block: Add "drained begin/end" for transactional blockdev-backup Fam Zheng
2015-10-20  5:17 ` [Qemu-devel] [PATCH v4 09/12] block: Add "drained begin/end" for internal snapshot Fam Zheng
2015-10-20  5:17 ` [Qemu-devel] [PATCH v4 10/12] block: Introduce BlockDriver.bdrv_drain callback Fam Zheng
2015-10-20  5:17 ` [Qemu-devel] [PATCH v4 11/12] qed: Implement .bdrv_drain Fam Zheng
2015-10-20  5:17 ` [Qemu-devel] [PATCH v4 12/12] tests: Add test case for aio_disable_external Fam Zheng
2015-10-20 14:17 ` [Qemu-devel] [PATCH v4 00/12] block: Protect nested event loop with bdrv_drained_begin and bdrv_drained_end Kevin Wolf
2015-10-21  1:18   ` 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=20151021011805.GA639@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).