qemu-block
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-block] ping Re: [PATCH v2 0/6] nbd export qmp interface


From: Vladimir Sementsov-Ogievskiy
Subject: [Qemu-block] ping Re: [PATCH v2 0/6] nbd export qmp interface
Date: Thu, 21 Dec 2017 14:52:42 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0

Hi, what about this?

07.12.2017 18:50, Vladimir Sementsov-Ogievskiy wrote:
Here:
     1. separate export name from device name
     1.1 several exports per device possible
     2. add nbd-server-remove

v2:
01: add r-bs by Max and Eric, add comment to code (hope you don't mind)
03: address export by its name, not by device name
     make it possible to force-remove export, which is already
     non-force-removed (thourh new "hidden" field)
other patches are new

v1:
Add command to remove nbd export, pair to nbd-server-add.
The whole thing and description are in patch 02.


Vladimir Sementsov-Ogievskiy (6):
   nbd/server: add additional assert to nbd_export_put
   qapi: add name parameter to nbd-server-add
   qapi: add nbd-server-remove
   iotest 147: add cases to test new @name parameter of nbd-server-add
   iotests: implement QemuIoInteractive class
   iotest 201: new test for qmp nbd-server-remove

  qapi/block.json               |  27 ++++++++-
  include/block/nbd.h           |   3 +-
  blockdev-nbd.c                |  41 +++++++++++--
  hmp.c                         |   5 +-
  nbd/server.c                  |  31 +++++++++-
  tests/qemu-iotests/147        |  68 +++++++++++++++++-----
  tests/qemu-iotests/147.out    |   4 +-
  tests/qemu-iotests/201        | 130 ++++++++++++++++++++++++++++++++++++++++++
  tests/qemu-iotests/201.out    |   5 ++
  tests/qemu-iotests/group      |   1 +
  tests/qemu-iotests/iotests.py |  38 ++++++++++++
  11 files changed, 325 insertions(+), 28 deletions(-)
  create mode 100644 tests/qemu-iotests/201
  create mode 100644 tests/qemu-iotests/201.out



--
Best regards,
Vladimir




reply via email to

[Prev in Thread] Current Thread [Next in Thread]