From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PULL 00/22] Docker and block patches
Date: Fri, 26 May 2017 15:52:24 +0800 [thread overview]
Message-ID: <20170526075246.20265-1-famz@redhat.com> (raw)
The following changes since commit 9964e96dc9999cf7f7c936ee854a795415d19b60:
Merge remote-tracking branch 'jasowang/tags/net-pull-request' into staging (2017-05-23 15:01:31 +0100)
are available in the git repository at:
git://github.com/famz/qemu.git tags/docker-and-block-pull-request
for you to fetch changes up to 77269bba94ef97de99ae61fdc98629a8704ae2ed:
block: make accounting thread-safe (2017-05-26 09:25:30 +0800)
----------------------------------------------------------------
For Paolo's block layer thread safety part I and my docker testing
enhancements.
----------------------------------------------------------------
Fam Zheng (4):
docker: Run tests with current user
docker: Add bzip2 and hostname to fedora image
docker: Add libaio to fedora image
docker: Add flex and bison to centos6 image
Paolo Bonzini (18):
block: access copy_on_read with atomic ops
block: access quiesce_counter with atomic ops
block: access io_limits_disabled with atomic ops
block: access serialising_in_flight with atomic ops
block: access wakeup with atomic ops
block: access io_plugged with atomic ops
throttle-groups: only start one coroutine from drained_begin
throttle-groups: do not use qemu_co_enter_next
throttle-groups: protect throttled requests with a CoMutex
util: add stats64 module
block: use Stat64 for wr_highest_offset
block: access write_gen with atomics
block: protect tracked_requests and flush_queue with reqs_lock
block: introduce dirty_bitmap_mutex
migration/block: reset dirty bitmap before reading
block: protect modification of dirty bitmaps with a mutex
block: introduce block_account_one_io
block: make accounting thread-safe
block.c | 9 +-
block/accounting.c | 65 ++++++-----
block/block-backend.c | 5 +-
block/dirty-bitmap.c | 114 +++++++++++++++++--
block/io.c | 51 +++++----
block/mirror.c | 14 ++-
block/nfs.c | 4 +-
block/qapi.c | 2 +-
block/sheepdog.c | 3 +-
block/throttle-groups.c | 91 +++++++++++----
blockdev.c | 46 ++------
include/block/accounting.h | 8 +-
include/block/block.h | 5 +-
include/block/block_int.h | 65 +++++++----
include/block/dirty-bitmap.h | 25 +++--
include/qemu/stats64.h | 193 ++++++++++++++++++++++++++++++++
include/sysemu/block-backend.h | 10 +-
migration/block.c | 17 ++-
tests/docker/Makefile.include | 2 +-
tests/docker/dockerfiles/centos6.docker | 2 +-
tests/docker/dockerfiles/fedora.docker | 4 +-
util/Makefile.objs | 1 +
util/stats64.c | 136 ++++++++++++++++++++++
23 files changed, 687 insertions(+), 185 deletions(-)
create mode 100644 include/qemu/stats64.h
create mode 100644 util/stats64.c
--
2.9.4
next reply other threads:[~2017-05-26 7:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 7:52 Fam Zheng [this message]
2017-05-26 7:52 ` [Qemu-devel] [PULL 01/22] docker: Run tests with current user Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 02/22] docker: Add bzip2 and hostname to fedora image Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 03/22] docker: Add libaio " Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 04/22] docker: Add flex and bison to centos6 image Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 05/22] block: access copy_on_read with atomic ops Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 06/22] block: access quiesce_counter " Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 07/22] block: access io_limits_disabled " Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 08/22] block: access serialising_in_flight " Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 09/22] block: access wakeup " Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 10/22] block: access io_plugged " Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 11/22] throttle-groups: only start one coroutine from drained_begin Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 12/22] throttle-groups: do not use qemu_co_enter_next Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 13/22] throttle-groups: protect throttled requests with a CoMutex Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 14/22] util: add stats64 module Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 15/22] block: use Stat64 for wr_highest_offset Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 16/22] block: access write_gen with atomics Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 17/22] block: protect tracked_requests and flush_queue with reqs_lock Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 18/22] block: introduce dirty_bitmap_mutex Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 19/22] migration/block: reset dirty bitmap before reading Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 20/22] block: protect modification of dirty bitmaps with a mutex Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 21/22] block: introduce block_account_one_io Fam Zheng
2017-05-26 7:52 ` [Qemu-devel] [PULL 22/22] block: make accounting thread-safe Fam Zheng
2017-05-26 8:52 ` [Qemu-devel] [PULL 00/22] Docker and block patches no-reply
2017-05-30 9:19 ` Stefan Hajnoczi
2017-05-30 9:33 ` Fam Zheng
2017-05-30 9:36 ` Paolo Bonzini
2017-05-30 10:47 ` Fam Zheng
2017-06-01 14:15 ` Fam Zheng
2017-06-01 17:18 ` Peter Maydell
2017-06-02 7:58 ` Fam Zheng
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=20170526075246.20265-1-famz@redhat.com \
--to=famz@redhat.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).