From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PULL 00/14] Block layer patches
Date: Wed, 6 Sep 2023 11:13:20 -0400 [thread overview]
Message-ID: <CAJSP0QV+aADrdBGJD1LyWxeKtFAprK8=mMeDCt-F5_1qx0KYVg@mail.gmail.com> (raw)
In-Reply-To: <20230904143643.259916-1-kwolf@redhat.com>
test-bdrv-drain is failing. I think my coroutine wrapper patch might
be necessary:
https://gitlab.com/qemu-project/qemu/-/jobs/5029372308#L4907
I have dropped this patch series for the time being. Feel free to
remove my patches and send a new revision.
I will debug the test-bdrv-drain issue.
Stefan
On Mon, 4 Sept 2023 at 10:37, Kevin Wolf <kwolf@redhat.com> wrote:
>
> The following changes since commit 17780edd81d27fcfdb7a802efc870a99788bd2fc:
>
> Merge tag 'quick-fix-pull-request' of https://gitlab.com/bsdimp/qemu into staging (2023-08-31 10:06:29 -0400)
>
> are available in the Git repository at:
>
> https://repo.or.cz/qemu/kevin.git tags/for-upstream
>
> for you to fetch changes up to bb86eb45297840c31dbc4df6bac02e50596f2376:
>
> block: Remove unnecessary variable in bdrv_block_device_info (2023-09-04 11:03:28 +0200)
>
> ----------------------------------------------------------------
> Block layer patches
>
> - Process I/O in the current AioContext (instead of the BB AioContext)
> - Optimise reqs_lock to make multiqueue actually scale
> - iotests: Fix reference output for some tests after recent changes
> - vpc: Avoid dynamic stack allocation
> - Code cleanup, improved documentation
>
> ----------------------------------------------------------------
> Dmitry Frolov (1):
> vmdk: Clean up bdrv_open_child() return value check
>
> Fabiano Rosas (2):
> block: Remove bdrv_query_block_node_info
> block: Remove unnecessary variable in bdrv_block_device_info
>
> Fiona Ebner (1):
> iotests: adapt test output for new qemu_cleanup() behavior
>
> Hanna Czenczek (1):
> block: Be more verbose in create fallback
>
> Kevin Wolf (1):
> qemu-img: Update documentation for compressed images
>
> Michael Tokarev (1):
> qemu-img: omit errno value in error message
>
> Peter Maydell (1):
> block/iscsi: Document why we use raw malloc()
>
> Philippe Mathieu-Daudé (1):
> block/vpc: Avoid dynamic stack allocation
>
> Stefan Hajnoczi (5):
> block: minimize bs->reqs_lock section in tracked_request_end()
> block: change reqs_lock to QemuMutex
> block: remove AIOCBInfo->get_aio_context()
> block-backend: process I/O in the current AioContext
> block-backend: process zoned requests in the current AioContext
>
> docs/tools/qemu-img.rst | 19 ++++++++++++--
> include/block/aio.h | 1 -
> include/block/block-global-state.h | 2 ++
> include/block/block-io.h | 1 -
> include/block/block_int-common.h | 2 +-
> include/block/qapi.h | 3 ---
> block.c | 10 ++++---
> block/block-backend.c | 35 +++++++------------------
> block/io.c | 53 +++++++++++++++++++-------------------
> block/iscsi.c | 1 +
> block/qapi.c | 32 ++---------------------
> block/vmdk.c | 2 +-
> block/vpc.c | 4 +--
> hw/nvme/ctrl.c | 7 -----
> qemu-img.c | 4 +--
> softmmu/dma-helpers.c | 8 ------
> util/thread-pool.c | 8 ------
> tests/qemu-iotests/080.out | 6 ++---
> tests/qemu-iotests/109.out | 24 +++++++++++++++++
> tests/qemu-iotests/112.out | 6 ++---
> tests/qemu-iotests/185 | 2 ++
> tests/qemu-iotests/185.out | 4 +++
> tests/qemu-iotests/244.out | 2 +-
> 23 files changed, 107 insertions(+), 129 deletions(-)
>
>
next prev parent reply other threads:[~2023-09-06 15:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 14:36 [PULL 00/14] Block layer patches Kevin Wolf
2023-09-04 14:36 ` [PULL 01/14] block/vpc: Avoid dynamic stack allocation Kevin Wolf
2023-09-04 14:36 ` [PULL 02/14] iotests: adapt test output for new qemu_cleanup() behavior Kevin Wolf
2023-09-04 14:36 ` [PULL 03/14] block: minimize bs->reqs_lock section in tracked_request_end() Kevin Wolf
2023-09-04 14:36 ` [PULL 04/14] block: change reqs_lock to QemuMutex Kevin Wolf
2023-09-04 14:36 ` [PULL 05/14] qemu-img: omit errno value in error message Kevin Wolf
2023-09-04 14:36 ` [PULL 06/14] block/iscsi: Document why we use raw malloc() Kevin Wolf
2023-09-04 14:36 ` [PULL 07/14] block: Be more verbose in create fallback Kevin Wolf
2023-09-04 14:36 ` [PULL 08/14] qemu-img: Update documentation for compressed images Kevin Wolf
2023-09-04 14:36 ` [PULL 09/14] vmdk: Clean up bdrv_open_child() return value check Kevin Wolf
2023-09-04 14:36 ` [PULL 10/14] block: remove AIOCBInfo->get_aio_context() Kevin Wolf
2023-09-04 14:36 ` [PULL 11/14] block-backend: process I/O in the current AioContext Kevin Wolf
2023-09-04 14:36 ` [PULL 12/14] block-backend: process zoned requests " Kevin Wolf
2023-09-04 14:36 ` [PULL 13/14] block: Remove bdrv_query_block_node_info Kevin Wolf
2023-09-04 14:36 ` [PULL 14/14] block: Remove unnecessary variable in bdrv_block_device_info Kevin Wolf
2023-09-06 15:13 ` Stefan Hajnoczi [this message]
2023-09-07 8:17 ` [PULL 00/14] Block layer patches Kevin Wolf
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 18:13 Kevin Wolf
2024-01-20 17:21 ` Peter Maydell
2024-01-22 11:14 ` Kevin Wolf
2024-01-22 11:44 ` Peter Maydell
2021-05-14 16:31 Kevin Wolf
2021-05-16 21:09 ` Philippe Mathieu-Daudé
2021-05-17 10:29 ` Peter Maydell
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='CAJSP0QV+aADrdBGJD1LyWxeKtFAprK8=mMeDCt-F5_1qx0KYVg@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=kwolf@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).