qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com,
	Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
	stefanha@redhat.com
Subject: [Qemu-devel] [RFC PATCH 0/3] move global bdrv_states out of block.c
Date: Tue, 27 Aug 2013 15:49:22 +0800	[thread overview]
Message-ID: <1377589765-30215-1-git-send-email-xiawenc@linux.vnet.ibm.com> (raw)

In order to support multiple caller from different thread, global
inside block layer should be carefully treated. bdrv_states represent
a group of bds* which is now used by qemu, so it is a user concept which
should be managed by user. This series tries to move it out, so later
different thread can feed the API with its own bds* group.

This is a RFC series which does not completely convert the API, the missing
part is adding parameter *l in all API which uses bdrv_states, then move
bdrv_states to caller. About 10 functions need to be converted, so hope to
get comments before that, to see if this is the right direction.

Wenchao Xia (3):
  1 block: add typedef for BlockDriverState queue
  2 block: add function qemu_get_bds_queue
  3 block: add parameter bds queue in bdrv_invalidate_cache_all()

 block.c               |   11 ++++++++---
 include/block/block.h |    7 ++++++-
 migration.c           |    2 +-
 3 files changed, 15 insertions(+), 5 deletions(-)

             reply	other threads:[~2013-08-27  7:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-27  7:49 Wenchao Xia [this message]
2013-08-27  7:49 ` [Qemu-devel] [RFC PATCH 1/3] block: add typedef for BlockDriverState queue Wenchao Xia
2013-08-27  7:49 ` [Qemu-devel] [RFC PATCH 2/3] block: add function qemu_get_bds_queue Wenchao Xia
2013-08-27  7:49 ` [Qemu-devel] [RFC PATCH 3/3] block: add parameter bds queue in bdrv_invalidate_cache_all() Wenchao Xia
2013-09-18 14:03 ` [Qemu-devel] [RFC PATCH 0/3] move global bdrv_states out of block.c Stefan Hajnoczi
2013-09-20  6:24   ` Wenchao Xia

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=1377589765-30215-1-git-send-email-xiawenc@linux.vnet.ibm.com \
    --to=xiawenc@linux.vnet.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).