From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 00/24] Block patches
Date: Tue, 21 Feb 2017 11:16:00 +0000 [thread overview]
Message-ID: <20170221111600.GC22731@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAFEAcA_5dyLsiGwns9LgBf92Ffv57VEPo3SYmfz6wGeFU7YeLg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
On Mon, Feb 20, 2017 at 01:37:58PM +0000, Peter Maydell wrote:
> On 20 February 2017 at 09:32, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > The following changes since commit 5dae13cd71f0755a1395b5a4cde635b8a6ee3f58:
> >
> > Merge remote-tracking branch 'remotes/rth/tags/pull-or-20170214' into staging (2017-02-14 09:55:48 +0000)
> >
> > are available in the git repository at:
> >
> > git://github.com/stefanha/qemu.git tags/block-pull-request
> >
> > for you to fetch changes up to decc18f33adecb1316437a47fff0cf0a7665906a:
> >
> > coroutine-lock: make CoRwlock thread-safe and fair (2017-02-16 17:17:34 +0000)
> >
> > ----------------------------------------------------------------
> >
> > ----------------------------------------------------------------
>
> Hi; this has merge conflicts in hw/scsi/virtio-scsi.c and
> hw/block/virtio-blk.c which I could maybe resolve by hand
> but at least one of them makes me suspicious that perhaps
> the automatic merging will have semantically mismerged:
>
> @@@ -758,13 -756,13 +768,18 @@@ out
> virtio_scsi_release(s);
> }
>
> -void virtio_scsi_handle_event_vq(VirtIOSCSI *s, VirtQueue *vq)
> +bool virtio_scsi_handle_event_vq(VirtIOSCSI *s, VirtQueue *vq)
> {
> + virtio_scsi_acquire(s);
> if (s->events_dropped) {
> virtio_scsi_push_event(s, NULL, VIRTIO_SCSI_T_NO_EVENT, 0);
> + return true;
> }
> ++<<<<<<< HEAD
> + return false;
> ++=======
> + virtio_scsi_release(s);
> ++>>>>>>> remotes/stefanha/tags/block-pull-request
> }
>
> static void virtio_scsi_handle_event(VirtIODevice *vdev, VirtQueue *vq)
>
> since one half of this merge is adding extra return paths
> which won't have release() calls in them in the other half.
>
> Can you rebase and fix, please?
Sending v2.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-02-21 11:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 9:32 [Qemu-devel] [PULL 00/24] Block patches Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 01/24] block: move AioContext, QEMUTimer, main-loop to libqemuutil Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 02/24] aio: introduce aio_co_schedule and aio_co_wake Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 03/24] block-backend: allow blk_prw from coroutine context Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 04/24] test-thread-pool: use generic AioContext infrastructure Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 05/24] io: add methods to set I/O handlers on AioContext Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 06/24] io: make qio_channel_yield aware of AioContexts Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 07/24] nbd: convert to use qio_channel_yield Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 08/24] coroutine-lock: reschedule coroutine on the AioContext it was running on Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 09/24] blkdebug: reschedule coroutine on the AioContext it is " Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 10/24] qed: introduce qed_aio_start_io and qed_aio_next_io_cb Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 11/24] aio: push aio_context_acquire/release down to dispatching Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 12/24] block: explicitly acquire aiocontext in timers that need it Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 13/24] block: explicitly acquire aiocontext in callbacks " Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 14/24] block: explicitly acquire aiocontext in bottom halves " Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 15/24] block: explicitly acquire aiocontext in aio callbacks " Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 16/24] aio-posix: partially inline aio_dispatch into aio_poll Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 17/24] async: remove unnecessary inc/dec pairs Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 18/24] block: document fields protected by AioContext lock Stefan Hajnoczi
2017-02-20 9:32 ` [Qemu-devel] [PULL 19/24] coroutine-lock: make CoMutex thread-safe Stefan Hajnoczi
2017-02-20 9:33 ` [Qemu-devel] [PULL 20/24] coroutine-lock: add limited spinning to CoMutex Stefan Hajnoczi
2017-02-20 9:33 ` [Qemu-devel] [PULL 21/24] test-aio-multithread: add performance comparison with thread-based mutexes Stefan Hajnoczi
2017-02-20 9:33 ` [Qemu-devel] [PULL 22/24] coroutine-lock: place CoMutex before CoQueue in header Stefan Hajnoczi
2017-02-20 9:33 ` [Qemu-devel] [PULL 23/24] coroutine-lock: add mutex argument to CoQueue APIs Stefan Hajnoczi
2017-02-20 9:33 ` [Qemu-devel] [PULL 24/24] coroutine-lock: make CoRwlock thread-safe and fair Stefan Hajnoczi
2017-02-20 13:37 ` [Qemu-devel] [PULL 00/24] Block patches Peter Maydell
2017-02-20 13:53 ` Paolo Bonzini
2017-02-21 11:16 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-14 16:48 Kevin Wolf
2011-10-14 17:48 ` Anthony Liguori
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=20170221111600.GC22731@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=peter.maydell@linaro.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).