qemu-commits
[Top][All Lists]
Advanced

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

[Qemu-commits] [qemu/qemu] 339984: block: drop unused bdrv_co_drain() AP


From: Richard Henderson
Subject: [Qemu-commits] [qemu/qemu] 339984: block: drop unused bdrv_co_drain() API
Date: Fri, 24 Jun 2022 13:38:12 -0700

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: 3399848b7fffcf388f53c5308a9b97bcd346ea7c
      
https://github.com/qemu/qemu/commit/3399848b7fffcf388f53c5308a9b97bcd346ea7c
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/io.c
    M include/block/block-io.h

  Log Message:
  -----------
  block: drop unused bdrv_co_drain() API

bdrv_co_drain() has not been used since commit 9a0cec664eef ("mirror:
use bdrv_drained_begin/bdrv_drained_end") in 2016. Remove it so there
are fewer drain scenarios to worry about.

Use bdrv_drained_begin()/bdrv_drained_end() instead. They are "mixed"
functions that can be called from coroutine context. Unlike
bdrv_co_drain(), these functions provide control of the length of the
drained section, which is usually the right thing.

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20220521122714.3837731-1-stefanha@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Alberto Faria <afaria@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 1ab5096b3a9790f28be0399f8642b8cebd3529e0
      
https://github.com/qemu/qemu/commit/1ab5096b3a9790f28be0399f8642b8cebd3529e0
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/block-backend.c
    M block/export/vhost-user-blk-server.c
    M hw/block/virtio-blk.c
    M hw/block/xen-block.c
    M hw/ide/core.c
    M hw/scsi/scsi-disk.c
    M hw/scsi/scsi-generic.c
    M include/sysemu/block-backend-io.h

  Log Message:
  -----------
  block: get rid of blk->guest_block_size

Commit 1b7fd729559c ("block: rename buffer_alignment to
guest_block_size") noted:

  At this point, the field is set by the device emulation, but completely
  ignored by the block layer.

The last time the value of buffer_alignment/guest_block_size was
actually used was before commit 339064d50639 ("block: Don't use guest
sector size for qemu_blockalign()").

This value has not been used since 2013. Get rid of it.

Cc: Xie Yongji <xieyongji@bytedance.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20220518130945.2657905-1-stefanha@redhat.com>
Reviewed-by: Paul Durrant <paul@xen.org>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Alberto Faria <afaria@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 775b30b3050a8718130701008a4afcca57e774c4
      
https://github.com/qemu/qemu/commit/775b30b3050a8718130701008a4afcca57e774c4
  Author: Vladimir Sementsov-Ogievskiy <vsementsov@openvz.org>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/monitor/bitmap-qmp-cmds.c

  Log Message:
  -----------
  block: block_dirty_bitmap_merge(): fix error path

At the end we ignore failure of bdrv_merge_dirty_bitmap() and report
success. And still set errp. That's wrong.

Signed-off-by: Vladimir Sementsov-Ogievskiy <v.sementsov-og@mail.ru>
Reviewed-by: Nikita Lapshin <nikita.lapshin@virtuozzo.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <20220517111206.23585-2-v.sementsov-og@mail.ru>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 58cbfbdf73d1d20ba9506b1260a4cb321adad47d
      
https://github.com/qemu/qemu/commit/58cbfbdf73d1d20ba9506b1260a4cb321adad47d
  Author: Vladimir Sementsov-Ogievskiy <vsementsov@openvz.org>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/monitor/bitmap-qmp-cmds.c

  Log Message:
  -----------
  block: improve block_dirty_bitmap_merge(): don't allocate extra bitmap

We don't need extra bitmap. All we need is to backup the original
bitmap when we do first merge. So, drop extra temporary bitmap and work
directly with target and backup.

Still to keep old semantics, that on failure target is unchanged and
user don't need to restore, we need a local_backup variable and do
restore ourselves on failure path.

Signed-off-by: Vladimir Sementsov-Ogievskiy <v.sementsov-og@mail.ru>
Message-Id: <20220517111206.23585-3-v.sementsov-og@mail.ru>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 618af89e559daf897cc5013d3476a9c41ee76e00
      
https://github.com/qemu/qemu/commit/618af89e559daf897cc5013d3476a9c41ee76e00
  Author: Vladimir Sementsov-Ogievskiy <vsementsov@openvz.org>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/backup.c
    M block/dirty-bitmap.c
    M include/block/block_int-io.h
    M include/qemu/hbitmap.h
    M util/hbitmap.c

  Log Message:
  -----------
  block: simplify handling of try to merge different sized bitmaps

We have too much logic to simply check that bitmaps are of the same
size. Let's just define that hbitmap_merge() and
bdrv_dirty_bitmap_merge_internal() require their argument bitmaps be of
same size, this simplifies things.

Let's look through the callers:

For backup_init_bcs_bitmap() we already assert that merge can't fail.

In bdrv_reclaim_dirty_bitmap_locked() we gracefully handle the error
that can't happen: successor always has same size as its parent, drop
this logic.

In bdrv_merge_dirty_bitmap() we already has assertion and separate
check. Make the check explicit and improve error message.

Signed-off-by: Vladimir Sementsov-Ogievskiy <v.sementsov-og@mail.ru>
Reviewed-by: Nikita Lapshin <nikita.lapshin@virtuozzo.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <20220517111206.23585-4-v.sementsov-og@mail.ru>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: ac1fc3a3a93ca57271e4ca6072aa340b30261d1e
      
https://github.com/qemu/qemu/commit/ac1fc3a3a93ca57271e4ca6072aa340b30261d1e
  Author: Xie Yongji <xieyongji@bytedance.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/block-backend.c

  Log Message:
  -----------
  block: Support passing NULL ops to blk_set_dev_ops()

This supports passing NULL ops to blk_set_dev_ops()
so that we can remove stale ops in some cases.

Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20220523084611.91-2-xieyongji@bytedance.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 8e7fd6f623fb8f6c6eb9b456d9221d4c8226f3d5
      
https://github.com/qemu/qemu/commit/8e7fd6f623fb8f6c6eb9b456d9221d4c8226f3d5
  Author: Xie Yongji <xieyongji@bytedance.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/export/vhost-user-blk-server.c

  Log Message:
  -----------
  block/export: Fix incorrect length passed to vu_queue_push()

Now the req->size is set to the correct value only
when handling VIRTIO_BLK_T_GET_ID request. This patch
fixes it.

Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Message-Id: <20220523084611.91-3-xieyongji@bytedance.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 5c368029703da5f16dd2bbc4308c4486e74c1aa3
      
https://github.com/qemu/qemu/commit/5c368029703da5f16dd2bbc4308c4486e74c1aa3
  Author: Xie Yongji <xieyongji@bytedance.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M MAINTAINERS
    M block/export/meson.build
    M block/export/vhost-user-blk-server.c
    A block/export/virtio-blk-handler.c
    A block/export/virtio-blk-handler.h

  Log Message:
  -----------
  block/export: Abstract out the logic of virtio-blk I/O process

Abstract the common logic of virtio-blk I/O process to a function
named virtio_blk_process_req(). It's needed for the following commit.

Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Message-Id: <20220523084611.91-4-xieyongji@bytedance.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 92e879505feb70d141acdb78c0331c796fda8f96
      
https://github.com/qemu/qemu/commit/92e879505feb70d141acdb78c0331c796fda8f96
  Author: Xie Yongji <xieyongji@bytedance.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    A linux-headers/linux/vduse.h
    M scripts/update-linux-headers.sh

  Log Message:
  -----------
  linux-headers: Add vduse.h

This adds vduse header to linux headers so that the
relevant VDUSE API can be used in subsequent patches.

Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20220523084611.91-5-xieyongji@bytedance.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: a6caeee8111386b2d16ee07fe817193cde7f0d2a
      
https://github.com/qemu/qemu/commit/a6caeee8111386b2d16ee07fe817193cde7f0d2a
  Author: Xie Yongji <xieyongji@bytedance.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M MAINTAINERS
    M meson.build
    M meson_options.txt
    M scripts/meson-buildoptions.sh
    A subprojects/libvduse/include/atomic.h
    A subprojects/libvduse/include/compiler.h
    A subprojects/libvduse/libvduse.c
    A subprojects/libvduse/libvduse.h
    A subprojects/libvduse/linux-headers/linux
    A subprojects/libvduse/meson.build
    A subprojects/libvduse/standard-headers/linux

  Log Message:
  -----------
  libvduse: Add VDUSE (vDPA Device in Userspace) library

VDUSE [1] is a linux framework that makes it possible to implement
software-emulated vDPA devices in userspace. This adds a library
as a subproject to help implementing VDUSE backends in QEMU.

[1] https://www.kernel.org/doc/html/latest/userspace-api/vduse.html

Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Message-Id: <20220523084611.91-6-xieyongji@bytedance.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 2a2359b84407b35fe978e98b7396f2ab8c5dd8b7
      
https://github.com/qemu/qemu/commit/2a2359b84407b35fe978e98b7396f2ab8c5dd8b7
  Author: Xie Yongji <xieyongji@bytedance.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M MAINTAINERS
    M block/export/export.c
    M block/export/meson.build
    A block/export/vduse-blk.c
    A block/export/vduse-blk.h
    M meson.build
    M meson_options.txt
    M qapi/block-export.json
    M scripts/meson-buildoptions.sh

  Log Message:
  -----------
  vduse-blk: Implement vduse-blk export

This implements a VDUSE block backends based on
the libvduse library. We can use it to export the BDSs
for both VM and container (host) usage.

The new command-line syntax is:

$ qemu-storage-daemon \
    --blockdev file,node-name=drive0,filename=test.img \
    --export vduse-blk,node-name=drive0,id=vduse-export0,writable=on

After the qemu-storage-daemon started, we need to use
the "vdpa" command to attach the device to vDPA bus:

$ vdpa dev add name vduse-export0 mgmtdev vduse

Also the device must be removed via the "vdpa" command
before we stop the qemu-storage-daemon.

Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20220523084611.91-7-xieyongji@bytedance.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 9e4dea67277fff54ccc9d83444c8fa392ad94c11
      
https://github.com/qemu/qemu/commit/9e4dea67277fff54ccc9d83444c8fa392ad94c11
  Author: Xie Yongji <xieyongji@bytedance.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/export/vduse-blk.c

  Log Message:
  -----------
  vduse-blk: Add vduse-blk resize support

To support block resize, this uses vduse_dev_update_config()
to update the capacity field in configuration space and inject
config interrupt on the block resize callback.

Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20220523084611.91-8-xieyongji@bytedance.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: d043e2db87a3d9725a8cbc86cfee61039df65f77
      
https://github.com/qemu/qemu/commit/d043e2db87a3d9725a8cbc86cfee61039df65f77
  Author: Xie Yongji <xieyongji@bytedance.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/export/vduse-blk.c
    M subprojects/libvduse/libvduse.c
    M subprojects/libvduse/libvduse.h

  Log Message:
  -----------
  libvduse: Add support for reconnecting

To support reconnecting after restart or crash, VDUSE backend
might need to resubmit inflight I/Os. This stores the metadata
such as the index of inflight I/O's descriptors to a shm file so
that VDUSE backend can restore them during reconnecting.

Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Message-Id: <20220523084611.91-9-xieyongji@bytedance.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: ca941c406cc3fb152abdfa490e66aaedd03b869c
      
https://github.com/qemu/qemu/commit/ca941c406cc3fb152abdfa490e66aaedd03b869c
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M docs/tools/qemu-storage-daemon.rst
    M storage-daemon/qemu-storage-daemon.c

  Log Message:
  -----------
  qsd: document vduse-blk exports

Document vduse-blk exports in qemu-storage-daemon --help and the
qemu-storage-daemon(1) man page.

Based-on: <20220523084611.91-1-xieyongji@bytedance.com>
Cc: Xie Yongji <xieyongji@bytedance.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20220525121947.859820-1-stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 66dc5f9606bec7ce029e98a90f209153dfade82e
      
https://github.com/qemu/qemu/commit/66dc5f9606bec7ce029e98a90f209153dfade82e
  Author: Stefano Garzarella <sgarzare@redhat.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/rbd.c
    M meson.build

  Log Message:
  -----------
  block/rbd: report a better error when namespace does not exist

If the namespace does not exist, rbd_create() fails with -ENOENT and
QEMU reports a generic "error rbd create: No such file or directory":

    $ qemu-img create rbd:rbd/namespace/image 1M
    Formatting 'rbd:rbd/namespace/image', fmt=raw size=1048576
    qemu-img: rbd:rbd/namespace/image: error rbd create: No such file or 
directory

Unfortunately rados_ioctx_set_namespace() does not fail if the namespace
does not exist, so let's use rbd_namespace_exists() in qemu_rbd_connect()
to check if the namespace exists, reporting a more understandable error:

    $ qemu-img create rbd:rbd/namespace/image 1M
    Formatting 'rbd:rbd/namespace/image', fmt=raw size=1048576
    qemu-img: rbd:rbd/namespace/image: namespace 'namespace' does not exist

Reported-by: Tingting Mao <timao@redhat.com>
Reviewed-by: Ilya Dryomov <idryomov@gmail.com>
Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
Message-Id: <20220517071012.6120-1-sgarzare@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 9b38fc56c054c7de65fa3bf7cdd82b32654f6b7d
      
https://github.com/qemu/qemu/commit/9b38fc56c054c7de65fa3bf7cdd82b32654f6b7d
  Author: Fabian Ebner <f.ebner@proxmox.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/gluster.c

  Log Message:
  -----------
  block/gluster: correctly set max_pdiscard

On 64-bit platforms, assigning SIZE_MAX to the int64_t max_pdiscard
results in a negative value, and the following assertion would trigger
down the line (it's not the same max_pdiscard, but computed from the
other one):
qemu-system-x86_64: ../block/io.c:3166: bdrv_co_pdiscard: Assertion
`max_pdiscard >= bs->bl.request_alignment' failed.

On 32-bit platforms, it's fine to keep using SIZE_MAX.

The assertion in qemu_gluster_co_pdiscard() is checking that the value
of 'bytes' can safely be passed to glfs_discard_async(), which takes a
size_t for the argument in question, so it is kept as is. And since
max_pdiscard is still <= SIZE_MAX, relying on max_pdiscard is still
fine.

Fixes: 0c8022876f ("block: use int64_t instead of int in driver discard 
handlers")
Cc: qemu-stable@nongnu.org
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
Message-Id: <20220520075922.43972-1-f.ebner@proxmox.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 7455ff1aa01564cc175db5b2373e610503ad4411
      
https://github.com/qemu/qemu/commit/7455ff1aa01564cc175db5b2373e610503ad4411
  Author: Emanuele Giuseppe Esposito <eesposit@redhat.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M include/block/aio-wait.h
    M util/aio-wait.c

  Log Message:
  -----------
  aio_wait_kick: add missing memory barrier

It seems that aio_wait_kick always required a memory barrier
or atomic operation in the caller, but nobody actually
took care of doing it.

Let's put the barrier in the function instead, and pair it
with another one in AIO_WAIT_WHILE. Read aio_wait_kick()
comment for further explanation.

Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Message-Id: <20220524173054.12651-1-eesposit@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 2866ddd121f5ccaabf1752a8d25eab9be1309d3f
      
https://github.com/qemu/qemu/commit/2866ddd121f5ccaabf1752a8d25eab9be1309d3f
  Author: Eric Blake <eblake@redhat.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/nbd.c

  Log Message:
  -----------
  nbd: Drop dead code spotted by Coverity

CID 1488362 points out that the second 'rc >= 0' check is now dead
code.

Reported-by: Peter Maydell <peter.maydell@linaro.org>
Fixes: 172f5f1a40(nbd: remove peppering of nbd_client_connected)
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <20220516210519.76135-1-eblake@redhat.com>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Vladimir Sementsov-Ogievskiy <v.sementsov-og@mail.ru>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 0862a087fd710a6c7ad4ea01d35309686e54e202
      
https://github.com/qemu/qemu/commit/0862a087fd710a6c7ad4ea01d35309686e54e202
  Author: Xie Yongji <xieyongji@bytedance.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/export/vduse-blk.c
    M block/export/vhost-user-blk-server.c
    M block/export/virtio-blk-handler.h
    M docs/tools/qemu-storage-daemon.rst
    M qapi/block-export.json
    M storage-daemon/qemu-storage-daemon.c

  Log Message:
  -----------
  vduse-blk: Add serial option

Add a 'serial' option to allow user to specify this value
explicitly. And the default value is changed to an empty
string as what we did in "hw/block/virtio-blk.c".

Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Message-Id: <20220614051532.92-6-xieyongji@bytedance.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 779d82e1d305f2a9cbd7f48cf6555ad58145e04a
      
https://github.com/qemu/qemu/commit/779d82e1d305f2a9cbd7f48cf6555ad58145e04a
  Author: Xie Yongji <xieyongji@bytedance.com>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M block/export/vduse-blk.c
    M docs/tools/qemu-storage-daemon.rst
    M qapi/block-export.json
    M storage-daemon/qemu-storage-daemon.c

  Log Message:
  -----------
  vduse-blk: Add name option

Currently we use 'id' option as the name of VDUSE device.
It's a bit confusing since we use one value for two different
purposes: the ID to identfy the export within QEMU (must be
distinct from any other exports in the same QEMU process, but
can overlap with names used by other processes), and the VDUSE
name to uniquely identify it on the host (must be distinct from
other VDUSE devices on the same host, but can overlap with other
export types like NBD in the same process). To make it clear,
this patch adds a separate 'name' option to specify the VDUSE
name for the vduse-blk export instead.

Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
Message-Id: <20220614051532.92-7-xieyongji@bytedance.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 40d522490714b65e0856444277db6c14c5cc3796
      
https://github.com/qemu/qemu/commit/40d522490714b65e0856444277db6c14c5cc3796
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2022-06-24 (Fri, 24 Jun 2022)

  Changed paths:
    M MAINTAINERS
    M block/backup.c
    M block/block-backend.c
    M block/dirty-bitmap.c
    M block/export/export.c
    M block/export/meson.build
    A block/export/vduse-blk.c
    A block/export/vduse-blk.h
    M block/export/vhost-user-blk-server.c
    A block/export/virtio-blk-handler.c
    A block/export/virtio-blk-handler.h
    M block/gluster.c
    M block/io.c
    M block/monitor/bitmap-qmp-cmds.c
    M block/nbd.c
    M block/rbd.c
    M docs/tools/qemu-storage-daemon.rst
    M hw/block/virtio-blk.c
    M hw/block/xen-block.c
    M hw/ide/core.c
    M hw/scsi/scsi-disk.c
    M hw/scsi/scsi-generic.c
    M include/block/aio-wait.h
    M include/block/block-io.h
    M include/block/block_int-io.h
    M include/qemu/hbitmap.h
    M include/sysemu/block-backend-io.h
    A linux-headers/linux/vduse.h
    M meson.build
    M meson_options.txt
    M qapi/block-export.json
    M scripts/meson-buildoptions.sh
    M scripts/update-linux-headers.sh
    M storage-daemon/qemu-storage-daemon.c
    A subprojects/libvduse/include/atomic.h
    A subprojects/libvduse/include/compiler.h
    A subprojects/libvduse/libvduse.c
    A subprojects/libvduse/libvduse.h
    A subprojects/libvduse/linux-headers/linux
    A subprojects/libvduse/meson.build
    A subprojects/libvduse/standard-headers/linux
    M util/aio-wait.c
    M util/hbitmap.c

  Log Message:
  -----------
  Merge tag 'for-upstream' of git://repo.or.cz/qemu/kevin into staging

Block layer patches

- Add vduse-blk export
- Dirty bitmaps: Fix and improve bitmap merge
- gluster: correctly set max_pdiscard
- rbd: report a better error when namespace does not exist
- aio_wait_kick: add missing memory barrier
- Code cleanups

# -----BEGIN PGP SIGNATURE-----
#
# iQJFBAABCAAvFiEE3D3rFZqa+V09dFb+fwmycsiPL9YFAmK10yURHGt3b2xmQHJl
# ZGhhdC5jb20ACgkQfwmycsiPL9YnXg/+J9PKsGl7hbJUFVIb4RZ3pMQ0o4xC1TbS
# OjA63RRwdJWt1gGsgLNH6kdsgz04FXiXk7XNDTe8MYn21bvznCYGFsI2EFJiit+x
# HkOYXJwAGsrfKBViq8QznosBQbwf9fOrDUlOdbnixFH/dx6DXUZM2F9ud5shiuiC
# vrP76zjUgSlHhPwL+0xsJSNxxNISv845uN9SYNpiGbZDaYLBtNbEc8NA2GMOYW45
# sCbxJDxNSFNrTT5gaZyo4KGFH9393qJSmYHJ+q53elbhje5dpmcn2c/AkIG7/UM4
# HsEWd7Gj1YbLQV6kvkefJzF4BOuZmN/b8sG+LRDjrEMHLeOw5rh2ETmkQfIdy2H3
# 2U52mHqw9bMGWtds0ocOJFKw3vPZuOCJaA+ql/A0aWGO9Fjivx1cQcOVXn3jKgj5
# 7riSxigK9TCTd92Qhi3j4do86mJi9NpjgawbQ5oOvKqUiq29moOwcv1hit0WVzwB
# hJp2qsrM6w00wFseyp+10vHigW7ZMNEIh4TKYLfZ15Gvy6YIG/m/oyCYF4oVM5y5
# knbsnJBRpTjLnggag86Pk8Ji+Lxi0cbv7zrbn++/S9OLQ5VMV5OpxKXHmyX2HyXa
# RCV0rMaTC3s4hy8gElDSwSeor6NBaJ9TECcit67uJ/kw1eK+omoa4hKMCgKf6qYC
# GY+NRPELJGA=
# =OuiN
# -----END PGP SIGNATURE-----
# gpg: Signature made Fri 24 Jun 2022 08:07:17 AM PDT
# gpg:                using RSA key DC3DEB159A9AF95D3D7456FE7F09B272C88F2FD6
# gpg:                issuer "kwolf@redhat.com"
# gpg: Good signature from "Kevin Wolf <kwolf@redhat.com>" [full]

* tag 'for-upstream' of git://repo.or.cz/qemu/kevin:
  vduse-blk: Add name option
  vduse-blk: Add serial option
  nbd: Drop dead code spotted by Coverity
  aio_wait_kick: add missing memory barrier
  block/gluster: correctly set max_pdiscard
  block/rbd: report a better error when namespace does not exist
  qsd: document vduse-blk exports
  libvduse: Add support for reconnecting
  vduse-blk: Add vduse-blk resize support
  vduse-blk: Implement vduse-blk export
  libvduse: Add VDUSE (vDPA Device in Userspace) library
  linux-headers: Add vduse.h
  block/export: Abstract out the logic of virtio-blk I/O process
  block/export: Fix incorrect length passed to vu_queue_push()
  block: Support passing NULL ops to blk_set_dev_ops()
  block: simplify handling of try to merge different sized bitmaps
  block: improve block_dirty_bitmap_merge(): don't allocate extra bitmap
  block: block_dirty_bitmap_merge(): fix error path
  block: get rid of blk->guest_block_size
  block: drop unused bdrv_co_drain() API

Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


Compare: https://github.com/qemu/qemu/compare/8b5669e40f05...40d522490714



reply via email to

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