From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Alberto Garcia <berto@igalia.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH v4 0/4] block: move I/O request processing to block/io.c
Date: Tue, 28 Apr 2015 14:27:48 +0100 [thread overview]
Message-ID: <1430227672-7670-1-git-send-email-stefanha@redhat.com> (raw)
Note: This series is based on my block-next branch:
https://github.com/stefanha/qemu.git block-next
v4:
* Extracted two patches that change block.c code, now making the final
block/io.c patch purely code movement [Eric]
* Added missing block/io.c file (oops!) [Eric]
This series splits block.c because the file has grown too large. This helps
separate the core block layer into BlockDriverState graph operations and I/O
processing.
Stefan Hajnoczi (4):
block: replace bdrv_states iteration with bdrv_next()
block: add bdrv_set_dirty()/bdrv_reset_dirty() to block_int.h
block: extract bdrv_setup_io_funcs()
block: move I/O request processing to block/io.c
block.c | 2519 +-------------------------------------------
block/Makefile.objs | 2 +-
block/io.c | 2540 +++++++++++++++++++++++++++++++++++++++++++++
include/block/block_int.h | 12 +
4 files changed, 2558 insertions(+), 2515 deletions(-)
create mode 100644 block/io.c
--
2.1.0
next reply other threads:[~2015-04-28 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 13:27 Stefan Hajnoczi [this message]
2015-04-28 13:27 ` [Qemu-devel] [PATCH v4 1/4] block: replace bdrv_states iteration with bdrv_next() Stefan Hajnoczi
2015-04-28 13:27 ` [Qemu-devel] [PATCH v4 2/4] block: add bdrv_set_dirty()/bdrv_reset_dirty() to block_int.h Stefan Hajnoczi
2015-04-28 13:27 ` [Qemu-devel] [PATCH v4 3/4] block: extract bdrv_setup_io_funcs() Stefan Hajnoczi
2015-04-28 13:27 ` [Qemu-devel] [PATCH v4 4/4] block: move I/O request processing to block/io.c Stefan Hajnoczi
2015-04-28 13:49 ` [Qemu-devel] [PATCH v4 0/4] " 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=1430227672-7670-1-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--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).