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/4] Block patches
Date: Thu, 9 Apr 2015 10:55:14 +0100 [thread overview]
Message-ID: <1428573318-1572-1-git-send-email-stefanha@redhat.com> (raw)
The following changes since commit 5a24f20a7208a58fb80d78ca0521bba6f4d7b145:
Merge remote-tracking branch 'remotes/mjt/tags/pull-trivial-patches-2015-04-04' into staging (2015-04-07 14:33:46 +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 05b685fbabb7fdcab72cb42b27db916fd74b2265:
block/iscsi: handle zero events from iscsi_which_events (2015-04-09 10:31:45 +0100)
----------------------------------------------------------------
----------------------------------------------------------------
Kevin Wolf (1):
qcow2: Fix header update with overridden backing file
Paolo Bonzini (2):
virtio-blk: correctly dirty guest memory
aio: strengthen memory barriers for bottom half scheduling
Peter Lieven (1):
block/iscsi: handle zero events from iscsi_which_events
async.c | 28 ++++++------
block/iscsi.c | 33 +++++++++++---
block/qcow2.c | 29 ++++++++++---
block/qcow2.h | 6 +++
hw/block/dataplane/virtio-blk.c | 3 +-
hw/block/virtio-blk.c | 13 +++++-
include/hw/virtio/virtio-blk.h | 1 +
tests/qemu-iotests/130 | 95 +++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/130.out | 43 +++++++++++++++++++
tests/qemu-iotests/group | 1 +
10 files changed, 220 insertions(+), 32 deletions(-)
create mode 100755 tests/qemu-iotests/130
create mode 100644 tests/qemu-iotests/130.out
--
2.1.0
next reply other threads:[~2015-04-09 9:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 9:55 Stefan Hajnoczi [this message]
2015-04-09 9:55 ` [Qemu-devel] [PULL 1/4] qcow2: Fix header update with overridden backing file Stefan Hajnoczi
2015-04-09 9:55 ` [Qemu-devel] [PULL 2/4] virtio-blk: correctly dirty guest memory Stefan Hajnoczi
2015-04-09 9:55 ` [Qemu-devel] [PULL 3/4] aio: strengthen memory barriers for bottom half scheduling Stefan Hajnoczi
2015-04-09 9:55 ` [Qemu-devel] [PULL 4/4] block/iscsi: handle zero events from iscsi_which_events Stefan Hajnoczi
2015-04-09 12:03 ` [Qemu-devel] [PULL 0/4] Block patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2016-07-15 17:59 Stefan Hajnoczi
2016-07-18 10:23 ` Peter Maydell
2016-07-18 14:57 ` Paolo Bonzini
2016-07-18 14:58 ` Peter Maydell
2016-07-19 8:58 ` Stefan Hajnoczi
2016-07-19 22:47 Max Reitz
2016-07-20 16:05 ` Peter Maydell
2016-07-20 21:16 ` Eric Blake
2016-07-21 19:14 ` Peter Maydell
2016-07-22 12:41 ` Max Reitz
2017-02-27 16:34 Stefan Hajnoczi
2017-02-28 10:38 ` Peter Maydell
2017-09-05 13:29 Stefan Hajnoczi
2017-09-05 15:36 ` Peter Maydell
2018-03-27 14:41 Stefan Hajnoczi
2018-03-27 18:20 ` Peter Maydell
2018-03-31 7:12 ` no-reply
2018-05-08 15:19 Jeff Cody
2018-05-08 16:54 ` Peter Maydell
2018-05-16 17:42 Jeff Cody
2018-05-17 12:18 ` Peter Maydell
2018-09-12 13:18 Jeff Cody
2019-01-04 11:21 Stefan Hajnoczi
2019-01-04 14:54 ` Peter Maydell
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=1428573318-1572-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).