qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com, armbru@redhat.com,
	eblake@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v4 0/5] vmdk: Implement blockdev-create
Date: Fri,  7 Dec 2018 12:53:38 +0100	[thread overview]
Message-ID: <20181207115343.6747-1-kwolf@redhat.com> (raw)

I picked up the patch series from Fam and rebased it to current master
(which involved a major rework on the test case) and tried to address
Markus' review comments for v2. I did not do any further review of the
actual code, but it passes the tests, so I guess having it in tree is
better than continuing to let it bitrot.

v4:
- Use "legacyESX" in QAPI instead of "legacyesx" (requires an additional
  exception from the QAPI rules, but the string is directly written into
  the VMDK file, and "legacyESX" is the spelling in the spec). The
  QemuOpts based parser stays case sensitive in v4. [Markus]
- Documentation fixes [Markus]
- Added tests for adapter types
- Added patch 5 to forbid excess extents in blockdev-create [Markus]

Fam Zheng (3):
  vmdk: Refactor vmdk_create_extent
  vmdk: Implement .bdrv_co_create callback
  iotests: Filter cid numbers in VMDK extent info

Kevin Wolf (2):
  iotests: Add VMDK tests for blockdev-create
  vmdk: Reject excess extents in blockdev-create

 qapi/block-core.json             |  71 +++++
 qapi/qapi-schema.json            |  16 +-
 block/vmdk.c                     | 532 ++++++++++++++++++++++---------
 tests/qemu-iotests/237           | 237 ++++++++++++++
 tests/qemu-iotests/237.out       | 348 ++++++++++++++++++++
 tests/qemu-iotests/common.filter |   1 +
 tests/qemu-iotests/group         |   1 +
 tests/qemu-iotests/iotests.py    |   1 +
 8 files changed, 1049 insertions(+), 158 deletions(-)
 create mode 100755 tests/qemu-iotests/237
 create mode 100644 tests/qemu-iotests/237.out

-- 
2.19.2

             reply	other threads:[~2018-12-07 11:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 11:53 Kevin Wolf [this message]
2018-12-07 11:53 ` [Qemu-devel] [PATCH v4 1/5] vmdk: Refactor vmdk_create_extent Kevin Wolf
2018-12-07 11:53 ` [Qemu-devel] [PATCH v4 2/5] vmdk: Implement .bdrv_co_create callback Kevin Wolf
2018-12-07 13:01   ` Markus Armbruster
2018-12-07 13:04     ` Markus Armbruster
2018-12-07 11:53 ` [Qemu-devel] [PATCH v4 3/5] iotests: Filter cid numbers in VMDK extent info Kevin Wolf
2018-12-07 11:53 ` [Qemu-devel] [PATCH v4 4/5] iotests: Add VMDK tests for blockdev-create Kevin Wolf
2018-12-07 13:02   ` Markus Armbruster
2018-12-07 13:12   ` Markus Armbruster
2018-12-07 14:45     ` Kevin Wolf
2018-12-07 15:40       ` Eric Blake
2018-12-07 16:42         ` Kevin Wolf
2018-12-07 16:52           ` Eric Blake
2018-12-07 17:09             ` Kevin Wolf
2018-12-07 11:53 ` [Qemu-devel] [PATCH v4 5/5] vmdk: Reject excess extents in blockdev-create Kevin Wolf
2018-12-07 13:11   ` Markus Armbruster
2018-12-07 14:54     ` Kevin Wolf
2018-12-07 15:34       ` Markus Armbruster
2018-12-07 12:56 ` [Qemu-devel] [PATCH v4 0/5] vmdk: Implement blockdev-create no-reply

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=20181207115343.6747-1-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).