All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, sw@weilnetz.de, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH 0/4] Allow VPC and VDI to be created over protocols
Date: Fri, 18 Jul 2014 16:53:57 -0400	[thread overview]
Message-ID: <cover.1405715876.git.jcody@redhat.com> (raw)

This allows VPC and VDI to be created over protocols; currently, they use
posix calls directly to open, seek, and write into new image files.  This
obviously precludes them from being able to be created over a protocol, like
glusterfs.

Jeff Cody (4):
  block: allow bdrv_unref() to be passed NULL pointers
  block: vdi - use block layer ops in vdi_create, instead of posix calls
  block: use the standard 'ret' instead of 'result'
  block: vpc - use block layer ops in vpc_create, instead of posix calls

 block.c     |  3 ++
 block/vdi.c | 82 ++++++++++++++++++++++----------------------------
 block/vpc.c | 99 +++++++++++++++++++++++++++----------------------------------
 3 files changed, 82 insertions(+), 102 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2014-07-18 20:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 20:53 Jeff Cody [this message]
2014-07-18 20:53 ` [Qemu-devel] [PATCH 1/4] block: allow bdrv_unref() to be passed NULL pointers Jeff Cody
2014-07-19 12:59   ` Max Reitz
2014-07-18 20:53 ` [Qemu-devel] [PATCH 2/4] block: vdi - use block layer ops in vdi_create, instead of posix calls Jeff Cody
2014-07-19 13:13   ` Max Reitz
2014-07-21 12:58     ` Jeff Cody
2014-07-21 13:02       ` Kevin Wolf
2014-07-18 20:54 ` [Qemu-devel] [PATCH 3/4] block: use the standard 'ret' instead of 'result' Jeff Cody
2014-07-19 13:23   ` Max Reitz
2014-07-18 20:54 ` [Qemu-devel] [PATCH 4/4] block: vpc - use block layer ops in vpc_create, instead of posix calls Jeff Cody
2014-07-19 13:33   ` Max Reitz

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=cover.1405715876.git.jcody@redhat.com \
    --to=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.