From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PULL 0/7] Block patches
Date: Wed, 28 Sep 2016 19:15:30 +0100 [thread overview]
Message-ID: <1475086537-31704-1-git-send-email-stefanha@redhat.com> (raw)
The following changes since commit 25930ed60aad49f1fdd7de05272317c86ce1275b:
Merge remote-tracking branch 'remotes/ehabkost/tags/x86-pull-request' into staging (2016-09-27 23:10:12 +0100)
are available in the git repository at:
git://github.com/stefanha/qemu.git tags/block-pull-request
for you to fetch changes up to fe121b9d3c4258e41f7efa4976bf79151b2d5dbb:
linux-aio: fix re-entrant completion processing (2016-09-28 17:11:23 +0100)
----------------------------------------------------------------
----------------------------------------------------------------
Laurent Vivier (1):
libqos: fix qvring_init()
Lin Ma (1):
iothread: check iothread->ctx before aio_context_unref to avoid
assertion
Stefan Hajnoczi (3):
coroutine: add qemu_coroutine_entered() function
test-coroutine: test qemu_coroutine_entered()
linux-aio: fix re-entrant completion processing
Yaowei Bai (2):
block: mirror: fix wrong comment of mirror_start
aio-posix: avoid unnecessary aio_epoll_enabled() calls
aio-posix.c | 12 +++++++-----
block/linux-aio.c | 9 ++++++---
include/block/block_int.h | 2 +-
include/qemu/coroutine.h | 13 +++++++++++++
iothread.c | 3 +++
tests/libqos/virtio.c | 2 +-
tests/test-coroutine.c | 42 ++++++++++++++++++++++++++++++++++++++++++
util/qemu-coroutine.c | 5 +++++
8 files changed, 78 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-28 18:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 18:15 Stefan Hajnoczi [this message]
2016-09-28 18:15 ` [Qemu-devel] [PULL 1/7] block: mirror: fix wrong comment of mirror_start Stefan Hajnoczi
2016-09-28 18:15 ` [Qemu-devel] [PULL 2/7] aio-posix: avoid unnecessary aio_epoll_enabled() calls Stefan Hajnoczi
2016-09-28 18:15 ` [Qemu-devel] [PULL 3/7] iothread: check iothread->ctx before aio_context_unref to avoid assertion Stefan Hajnoczi
2016-09-28 18:15 ` [Qemu-devel] [PULL 4/7] libqos: fix qvring_init() Stefan Hajnoczi
2016-09-28 18:15 ` [Qemu-devel] [PULL 5/7] coroutine: add qemu_coroutine_entered() function Stefan Hajnoczi
2016-09-28 18:15 ` [Qemu-devel] [PULL 6/7] test-coroutine: test qemu_coroutine_entered() Stefan Hajnoczi
2016-09-28 18:15 ` [Qemu-devel] [PULL 7/7] linux-aio: fix re-entrant completion processing Stefan Hajnoczi
2016-09-28 22:02 ` [Qemu-devel] [PULL 0/7] Block patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2019-03-08 16:53 Stefan Hajnoczi
2019-03-09 20:55 ` Peter Maydell
2018-03-09 13:19 Stefan Hajnoczi
2018-03-09 18:49 ` Peter Maydell
2017-06-30 11:46 Stefan Hajnoczi
2017-06-30 13:58 ` Peter Maydell
2015-11-06 17:52 Stefan Hajnoczi
2015-11-06 18:07 ` Peter Maydell
2015-11-09 2:00 ` Fam Zheng
2015-11-09 7:35 ` Markus Armbruster
2015-11-09 10:01 ` Stefan Hajnoczi
2015-09-25 15:50 Jeff Cody
2015-09-25 19:21 ` Peter Maydell
2015-04-30 19:10 Kevin Wolf
2015-05-01 8:59 ` Peter Maydell
2013-10-18 14:18 Stefan Hajnoczi
2013-06-17 16:31 Kevin Wolf
2013-06-17 21:17 ` Anthony Liguori
2010-07-26 14:01 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=1475086537-31704-1-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=peter.maydell@linaro.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).