All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-stable@nongnu.org, qemu-devel@nongnu.org,
	Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PULL v2 0/7] Block patches for 4.1.0-rc4
Date: Tue,  6 Aug 2019 13:59:45 +0200	[thread overview]
Message-ID: <20190806115952.8456-1-mreitz@redhat.com> (raw)

The following changes since commit 9bb68d34dda9be60335e73e65c8fb61bca035362:

  Merge remote-tracking branch 'remotes/philmd-gitlab/tags/edk2-next-20190803' into staging (2019-08-05 11:05:36 +0100)

are available in the Git repository at:

  https://github.com/XanClic/qemu.git tags/pull-block-2019-08-06

for you to fetch changes up to 110571be4e70ac015628e76d2731f96dd8d1998c:

  block/backup: disable copy_range for compressed backup (2019-08-06 13:17:27 +0200)
----------------------------------------------------------------
v2: Added “Cc: qemu-stable” tag where necessary

----------------------------------------------------------------
Block patches for 4.1.0-rc4:
- Fix the backup block job when using copy offloading
- Fix the mirror block job when using the write-blocking copy mode
- Fix incremental backups after the image has been grown with the
  respective bitmap attached to it

----------------------------------------------------------------
Max Reitz (5):
  backup: Copy only dirty areas
  iotests: Test backup job with two guest writes
  iotests: Test incremental backup after truncation
  mirror: Only mirror granularity-aligned chunks
  iotests: Test unaligned blocking mirror write

Vladimir Sementsov-Ogievskiy (2):
  util/hbitmap: update orig_size on truncate
  block/backup: disable copy_range for compressed backup

 block/backup.c             | 15 ++++++++++++---
 block/mirror.c             | 29 ++++++++++++++++++++++++++++
 util/hbitmap.c             |  6 +++++-
 tests/qemu-iotests/056     | 39 ++++++++++++++++++++++++++++++++++++++
 tests/qemu-iotests/056.out |  4 ++--
 tests/qemu-iotests/124     | 38 +++++++++++++++++++++++++++++++++----
 tests/qemu-iotests/124.out |  4 ++--
 tests/qemu-iotests/151     | 25 ++++++++++++++++++++++++
 tests/qemu-iotests/151.out |  4 ++--
 9 files changed, 150 insertions(+), 14 deletions(-)

-- 
2.21.0



             reply	other threads:[~2019-08-06 12:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 11:59 Max Reitz [this message]
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 1/7] backup: Copy only dirty areas Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 2/7] iotests: Test backup job with two guest writes Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 3/7] util/hbitmap: update orig_size on truncate Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 4/7] iotests: Test incremental backup after truncation Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 5/7] mirror: Only mirror granularity-aligned chunks Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 6/7] iotests: Test unaligned blocking mirror write Max Reitz
2019-08-06 11:59 ` [Qemu-devel] [PULL v2 7/7] block/backup: disable copy_range for compressed backup Max Reitz
2019-08-06 14:44 ` [Qemu-devel] [PULL v2 0/7] Block patches for 4.1.0-rc4 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=20190806115952.8456-1-mreitz@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.