All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Patrik Janoušek" <pj@patrikjanousek.cz>
To: qemu-devel@nongnu.org
Cc: "Patrik Janoušek" <pj@patrikjanousek.cz>, lmatejka@kiv.zcu.cz
Subject: [PATCH 0/2] block/raw: implemented persistent dirty bitmap and ability to dump bitmap content via qapi
Date: Sat, 20 Mar 2021 10:32:33 +0100	[thread overview]
Message-ID: <20210320093235.461485-1-pj@patrikjanousek.cz> (raw)

Currently, QEMU doesn't support persistent dirty bitmaps for raw format
and also dirty bitmaps are for internal use only, and cannot be accessed
using third-party applications. These facts are very limiting
in case someone would like to develop their own backup tool becaouse
without access to the dirty bitmap it would be possible to implement
only full backups. And without persistent dirty bitmaps, it wouldn't
be possible to keep track of changed data after QEMU is restarted. And
this is exactly what I do as a part of my bachelor thesis. I've
developed a tool that is able to create incremental backups of drives
in raw format that are LVM volumes (ability to create snapshot is
required).

Please keep in mind that this is my first submission to such a large
project and also the first time when I send patch over the email.
So I hope I did it correctly.

Patrik Janoušek (2):
  block/raw: added support of persistent dirty bitmaps
  qapi: implementation of the block-dirty-bitmap-dump command

 block/meson.build               |   1 +
 block/monitor/bitmap-qmp-cmds.c |  61 ++++++++
 block/raw-format-bitmap.c       | 163 ++++++++++++++++++++
 block/raw-format.c              | 256 ++++++++++++++++++++++++++++++--
 block/raw-format.h              |  50 +++++++
 qapi/block-core.json            |  64 +++++++-
 6 files changed, 583 insertions(+), 12 deletions(-)
 create mode 100644 block/raw-format-bitmap.c
 create mode 100644 block/raw-format.h

-- 
2.31.0



             reply	other threads:[~2021-03-20  9:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20  9:32 Patrik Janoušek [this message]
2021-03-20  9:32 ` [PATCH 1/2] block/raw: added support of persistent dirty bitmaps Patrik Janoušek
2021-03-22  8:41   ` Vladimir Sementsov-Ogievskiy
2021-03-22 10:18     ` Patrik Janoušek
2021-03-22 10:46       ` Vladimir Sementsov-Ogievskiy
2021-03-22 11:18         ` Vladimir Sementsov-Ogievskiy
2021-03-22 11:36           ` Patrik Janoušek
2021-03-22 20:27             ` Lubos Matejka
2021-03-22 15:43   ` Kevin Wolf
2021-03-20  9:32 ` [PATCH 2/2] qapi: implementation of the block-dirty-bitmap-dump command Patrik Janoušek
2021-03-22  9:02   ` Vladimir Sementsov-Ogievskiy
2021-03-22 15:12   ` Kevin Wolf
2021-03-22  8:29 ` [PATCH 0/2] block/raw: implemented persistent dirty bitmap and ability to dump bitmap content via qapi Vladimir Sementsov-Ogievskiy
2021-03-22  8:57   ` Patrik Janoušek
2021-03-22 14:53     ` Kevin Wolf
     [not found] ` <856ca6ba-3871-068f-f821-269c40a5a4d5@patrikjanousek.cz>
2021-03-22 10:48   ` Fwd: " Max Reitz
2021-03-22 11:27     ` Patrik Janoušek
2021-03-22 12:06       ` Max Reitz
2021-03-22 21:45         ` Patrik Janoušek
2021-03-22 12:44       ` Fabian Grünbichler

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=20210320093235.461485-1-pj@patrikjanousek.cz \
    --to=pj@patrikjanousek.cz \
    --cc=lmatejka@kiv.zcu.cz \
    --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 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.