xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Jiang Yunhong <yunhong.jiang@intel.com>,
	Dong Eddie <eddie.dong@intel.com>,
	xen devel <xen-devel@lists.xen.org>,
	Yang Hongyang <yanghy@cn.fujitsu.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [PATCH 00/17] blktap2 related bugfix patches
Date: Mon, 27 Oct 2014 14:32:17 -0400	[thread overview]
Message-ID: <20141027183217.GA13854@laptop.dumpdata.com> (raw)
In-Reply-To: <1413252845-23433-1-git-send-email-wency@cn.fujitsu.com>

On Tue, Oct 14, 2014 at 10:13:48AM +0800, Wen Congyang wrote:
> These bugs are found when we implement COLO, or rebase
> COLO to upstream xen. They are independent patches, so
> post them in separate series.

There is no maintainer for blktap in the Xen code-base.
As such there is nobody to actually review the patches.

Now there is an version of blktap(v3?v4?) 'userspace' 
that I have been hearing from but I do not know much
about.

As such - I was wondering what should be done
about your changes to blktap?

Are you considering being the maintainer of this
version of blktap code?

> 
> The codes are also hosted on github:
> https://github.com/wencongyang/xen/commits/bugfix-v4
> 
> Lai Jiangshan (1):
>   tools: blktap2: dynamic allocate aio_requests to avoid -EBUSY error
> 
> Wen Congyang (16):
>   tools: block-remus: pass uuid to the callback td_open
>   tools: block-remus: use correct way to get remus_image
>   tools: block-remus: fix bug in tdremus_close()
>   tools: block-remus: fix memory leak
>   tools: blktap2: return the correct dev path
>   tools: blktap2: use correct way to get free event id
>   tools: blktap2: don't return negative event id
>   tools: blktap2: use correct way to define array.
>   tools: block-remus: fix bug in ctl_request()
>   tools: block-remus: clean unused functions
>   tools: blktap2: implement an API to create a connection asynchronously
>   tools: block-remus: connect to backup asynchronously
>   block-remus: switch to unprotected mode before closing
>   tools: blktap2: move ramdisk related codes to block-replication.c
>   support blktap remus in xl
>   HACK: libxl/remus: setup and control disk replication for blktap2
>     backends
> 
>  tools/blktap2/drivers/Makefile            |    1 +
>  tools/blktap2/drivers/block-aio.c         |   41 +-
>  tools/blktap2/drivers/block-cache.c       |    4 +-
>  tools/blktap2/drivers/block-log.c         |    4 +-
>  tools/blktap2/drivers/block-qcow.c        |    5 +-
>  tools/blktap2/drivers/block-ram.c         |    5 +-
>  tools/blktap2/drivers/block-remus.c       | 1201 +++++++----------------------
>  tools/blktap2/drivers/block-replication.c |  928 ++++++++++++++++++++++
>  tools/blktap2/drivers/block-replication.h |  178 +++++
>  tools/blktap2/drivers/block-vhd.c         |    5 +-
>  tools/blktap2/drivers/scheduler.c         |   33 +-
>  tools/blktap2/drivers/tapdisk-control.c   |   17 +-
>  tools/blktap2/drivers/tapdisk-disktype.c  |   12 +-
>  tools/blktap2/drivers/tapdisk-disktype.h  |    2 +-
>  tools/blktap2/drivers/tapdisk-interface.c |   21 +-
>  tools/blktap2/drivers/tapdisk-interface.h |    1 +
>  tools/blktap2/drivers/tapdisk-vbd.c       |    9 +
>  tools/blktap2/drivers/tapdisk-vbd.h       |    1 +
>  tools/blktap2/drivers/tapdisk.h           |    3 +-
>  tools/libxl/Makefile                      |    2 +-
>  tools/libxl/libxl.c                       |   25 +-
>  tools/libxl/libxl_blktap2.c               |   38 +-
>  tools/libxl/libxl_create.c                |    8 +
>  tools/libxl/libxl_device.c                |   35 +-
>  tools/libxl/libxl_dm.c                    |    4 +-
>  tools/libxl/libxl_internal.h              |   10 +-
>  tools/libxl/libxl_noblktap2.c             |    8 +-
>  tools/libxl/libxl_remus_device.c          |    6 +
>  tools/libxl/libxl_remus_disk_blktap.c     |  209 +++++
>  tools/libxl/libxl_types.idl               |    2 +
>  tools/libxl/libxlu_disk_l.l               |    2 +
>  31 files changed, 1857 insertions(+), 963 deletions(-)
>  create mode 100644 tools/blktap2/drivers/block-replication.c
>  create mode 100644 tools/blktap2/drivers/block-replication.h
>  create mode 100644 tools/libxl/libxl_remus_disk_blktap.c
> 
> -- 
> 1.9.3
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      parent reply	other threads:[~2014-10-27 18:32 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14  2:13 [PATCH 00/17] blktap2 related bugfix patches Wen Congyang
2014-10-14  2:13 ` [PATCH 01/17] tools: blktap2: dynamic allocate aio_requests to avoid -EBUSY error Wen Congyang
2014-10-14  2:13 ` [PATCH 02/17] tools: block-remus: pass uuid to the callback td_open Wen Congyang
2014-10-20  2:58   ` Shriram Rajagopalan
2014-10-14  2:13 ` [PATCH 03/17] tools: block-remus: use correct way to get remus_image Wen Congyang
2014-10-20  3:02   ` Shriram Rajagopalan
2014-10-14  2:13 ` [PATCH 04/17] tools: block-remus: fix bug in tdremus_close() Wen Congyang
2014-10-20  3:01   ` Shriram Rajagopalan
2014-10-20  3:05     ` Wen Congyang
2014-10-14  2:13 ` [PATCH 05/17] tools: block-remus: fix memory leak Wen Congyang
2014-10-20  2:33   ` Shriram Rajagopalan
2014-10-14  2:13 ` [PATCH 06/17] tools: blktap2: return the correct dev path Wen Congyang
2014-10-14  2:13 ` [PATCH 07/17] tools: blktap2: use correct way to get free event id Wen Congyang
2014-10-14  2:13 ` [PATCH 08/17] tools: blktap2: don't return negative " Wen Congyang
2014-10-14  2:13 ` [PATCH 09/17] tools: blktap2: use correct way to define array Wen Congyang
2014-10-20  2:37   ` Shriram Rajagopalan
2014-10-20  2:52     ` Wen Congyang
2014-10-14  2:13 ` [PATCH 10/17] tools: block-remus: fix bug in ctl_request() Wen Congyang
2014-10-20  2:38   ` Shriram Rajagopalan
2014-10-14  2:13 ` [PATCH 11/17] tools: block-remus: clean unused functions Wen Congyang
2014-10-20  3:01   ` Shriram Rajagopalan
2014-10-14  2:14 ` [PATCH 12/17] tools: blktap2: implement an API to create a connection asynchronously Wen Congyang
2014-10-14  2:14 ` [PATCH 13/17] tools: block-remus: connect to backup asynchronously Wen Congyang
2014-10-20  2:50   ` Shriram Rajagopalan
2014-10-20  3:00     ` Wen Congyang
2014-10-20  3:11       ` Shriram Rajagopalan
2014-10-14  2:14 ` [PATCH 14/17] block-remus: switch to unprotected mode before closing Wen Congyang
2014-10-20  2:51   ` Shriram Rajagopalan
2014-10-14  2:14 ` [PATCH 15/17] tools: blktap2: move ramdisk related codes to block-replication.c Wen Congyang
2014-10-20  2:52   ` Shriram Rajagopalan
2014-10-14  2:14 ` [PATCH 16/17] support blktap remus in xl Wen Congyang
2014-10-14  2:14 ` [PATCH 17/17] HACK: libxl/remus: setup and control disk replication for blktap2 backends Wen Congyang
2014-10-20  3:00   ` Shriram Rajagopalan
2014-10-20  3:09     ` Wen Congyang
2014-10-14 15:48 ` [PATCH 00/17] blktap2 related bugfix patches Ian Jackson
2014-10-15  1:05   ` Wen Congyang
2014-10-19 20:34     ` Shriram Rajagopalan
2014-10-20 14:25     ` George Dunlap
2014-10-21  2:28       ` Wen Congyang
2014-10-21  2:56       ` Wen Congyang
2014-10-21  9:55         ` George Dunlap
2014-10-21 10:07           ` M A Young
2014-10-21 10:45           ` Bob Ball
2014-10-29  5:49       ` Wen Congyang
2014-11-03  9:58         ` George Dunlap
2014-11-03 10:07           ` Wen Congyang
2014-11-05 19:25             ` Konrad Rzeszutek Wilk
2015-02-13  6:56           ` Hongyang Yang
2015-02-14 18:40             ` George Dunlap
2014-10-27 18:32 ` Konrad Rzeszutek Wilk [this message]

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=20141027183217.GA13854@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=wency@cn.fujitsu.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yanghy@cn.fujitsu.com \
    --cc=yunhong.jiang@intel.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).