qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>,
	Hanna Reitz <hreitz@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, Fam Zheng <fam@euphon.net>
Subject: [PULL 0/2] Block patches
Date: Thu, 11 Jul 2024 11:17:07 +0200	[thread overview]
Message-ID: <20240711091709.584450-1-stefanha@redhat.com> (raw)

The following changes since commit 59084feb256c617063e0dbe7e64821ae8852d7cf:

  Merge tag 'pull-aspeed-20240709' of https://github.com/legoater/qemu into staging (2024-07-09 07:13:55 -0700)

are available in the Git repository at:

  https://gitlab.com/stefanha/qemu.git tags/block-pull-request

for you to fetch changes up to d05ae948cc887054495977855b0859d0d4ab2613:

  Consider discard option when writing zeros (2024-07-11 11:06:36 +0200)

----------------------------------------------------------------
Pull request

A discard fix from Nir Soffer.

----------------------------------------------------------------

Nir Soffer (2):
  qemu-iotest/245: Add missing discard=unmap
  Consider discard option when writing zeros

 block/io.c                                    |   9 +-
 tests/qemu-iotests/245                        |   2 +-
 tests/qemu-iotests/tests/write-zeroes-unmap   | 127 ++++++++++++++++++
 .../qemu-iotests/tests/write-zeroes-unmap.out |  81 +++++++++++
 4 files changed, 214 insertions(+), 5 deletions(-)
 create mode 100755 tests/qemu-iotests/tests/write-zeroes-unmap
 create mode 100644 tests/qemu-iotests/tests/write-zeroes-unmap.out

-- 
2.45.2



             reply	other threads:[~2024-07-11  9:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11  9:17 Stefan Hajnoczi [this message]
2024-07-11  9:17 ` [PULL 1/2] qemu-iotest/245: Add missing discard=unmap Stefan Hajnoczi
2024-07-11  9:17 ` [PULL 2/2] Consider discard option when writing zeros Stefan Hajnoczi
2024-07-11 18:51 ` [PULL 0/2] Block patches Richard Henderson
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 16:01 Stefan Hajnoczi
2024-01-25 15:11 ` Peter Maydell
2024-01-25 15:47 ` Michael Tokarev
2023-04-24 17:55 Stefan Hajnoczi
2023-04-25 11:15 ` Richard Henderson
2022-07-07  8:12 Stefan Hajnoczi
2022-07-07 10:51 ` Richard Henderson
2021-10-11 12:40 Stefan Hajnoczi
2021-10-11 18:23 ` Richard Henderson
2021-03-24 14:52 Stefan Hajnoczi
2021-03-24 18:05 ` Peter Maydell
2021-03-24 20:18   ` Vladimir Sementsov-Ogievskiy
2021-03-24 20:42     ` Peter Maydell
2021-03-25  9:56       ` Stefan Hajnoczi
2021-03-25 10:17         ` Vladimir Sementsov-Ogievskiy
2021-03-25 16:28           ` Stefan Hajnoczi
2021-03-25 16:36             ` Peter Maydell
2021-03-25 17:40               ` Stefan Hajnoczi
2021-03-26 10:22 ` Peter Maydell
2020-02-10  9:23 Stefan Hajnoczi
2020-02-10 18:09 ` Peter Maydell
2019-12-13 14:33 Stefan Hajnoczi
2019-12-13 21:10 ` Peter Maydell
2019-10-25 19:18 Stefan Hajnoczi
2019-10-26  9:13 ` Peter Maydell
2019-09-25 17:43 Stefan Hajnoczi
2019-09-26  6:16 ` no-reply
2019-09-26 12:06   ` Vladimir Sementsov-Ogievskiy
2019-09-26 12:56 ` 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=20240711091709.584450-1-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=fam@euphon.net \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).