[Top][All Lists]

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

Re: [RFC PATCH v2 0/4] Allow changing bs->file on reopen

From: Vladimir Sementsov-Ogievskiy
Subject: Re: [RFC PATCH v2 0/4] Allow changing bs->file on reopen
Date: Tue, 9 Feb 2021 10:15:56 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0

08.02.2021 21:44, Alberto Garcia wrote:

this series allows changing bs->file using x-blockdev-reopen. Read
here for more details:


Version 2 of the series introduces a very significant change:
x-blockdev-reopen now receives a list of BlockdevOptions instead of
just one, so it is possible to reopen multiple block devices using a
single transaction.

This is still an RFC, I haven't updated the documentation and the
structure of the patches will probably change in the future, but I'd
like to know your opinion about the approach.

These patches apply on top of Vladimir's branch:

git: https://src.openvz.org/scm/~vsementsov/qemu.git
tag: up-block-topologic-perm-v2

Patchew understands "Based-on: MESSAGE_ID" tag, so, you can add:

Based-on: <20201127144522.29991-1-vsementsov@virtuozzo.com>



Alberto Garcia (4):
   block: Allow changing bs->file on reopen
   iotests: Update 245 to support replacing files with x-blockdev-reopen
   block: Support multiple reopening with x-blockdev-reopen
   iotests: Test reopening multiple devices at the same time

  qapi/block-core.json       |   2 +-
  include/block/block.h      |   2 +
  block.c                    |  81 +++++++++++++++++++++--
  blockdev.c                 |  85 +++++++++++++-----------
  tests/qemu-iotests/155     |   9 ++-
  tests/qemu-iotests/165     |   4 +-
  tests/qemu-iotests/245     | 128 ++++++++++++++++++++++++++++++++-----
  tests/qemu-iotests/245.out |   4 +-
  tests/qemu-iotests/248     |   2 +-
  tests/qemu-iotests/248.out |   2 +-
  tests/qemu-iotests/298     |   4 +-
  11 files changed, 254 insertions(+), 69 deletions(-)

Best regards,

reply via email to

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