qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bohdan Trach <bohdan.trach@mailbox.tu-dresden.de>
To: Bohdan Trach <bv.trach@gmail.com>, qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, thomas.knauth@googlemail.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC, Ping 0/3] Checkpoint-assisted migration proposal
Date: Fri, 24 Apr 2015 13:38:54 +0200	[thread overview]
Message-ID: <553A2B4E.7070600@mailbox.tu-dresden.de> (raw)
In-Reply-To: <cover.1429272036.git.bv.trach@gmail.com>

Ping.

The patches are:
http://patchwork.ozlabs.org/patch/462043/
http://patchwork.ozlabs.org/patch/462040/
http://patchwork.ozlabs.org/patch/462045/

Description:
https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg01555.html
https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg02014.html

Feedback  is most welcome on the following aspects:
1. Code related to migration (ram_save_page, ram_load).
2. Hashing function choice (adding OpenSSL as a dependency just for one
function is probably not the best option).
3. Overall code organization.

Thank You!

On 04/17/2015 02:12 PM, Bohdan Trach wrote:
> From: Bohdan Trach <bohdan.trach@mailbox.tu-dresden.de>
> 
> This patchset contains a checkpoint-assisted migration feature as
> proposed earlier on this list [1]. It allows reusing existing memory
> snapshots of guests to speed up migration of VMs between physical
> hosts.
> 
> [1] https://lists.gnu.org/archive/html/qemu-devel/2015-04/msg01555.html
> 
> Bohdan Trach (3):
>   memory: Add dump-pc-mem command for checkpointing
>   memory: implement checkpoint handling
>   migration: use checkpoint during migration

-- 
With best regards,
Bohdan Trach

  parent reply	other threads:[~2015-04-24 11:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 12:12 [Qemu-devel] [PATCH RFC 0/3] Checkpoint-assisted migration proposal Bohdan Trach
2015-04-17 12:13 ` [Qemu-devel] [PATCH RFC 1/3] memory: Add dump-pc-mem command for checkpointing Bohdan Trach
2015-04-17 13:53   ` Eric Blake
2015-04-18  7:40     ` Bohdan Trach
2015-11-16 16:46   ` Dr. David Alan Gilbert
2015-11-17 15:38     ` Bohdan Trach
2015-11-17 16:02       ` Dr. David Alan Gilbert
2015-04-17 12:13 ` [Qemu-devel] [PATCH RFC 2/3] memory: implement checkpoint handling Bohdan Trach
2015-11-16 16:56   ` Dr. David Alan Gilbert
2015-11-17 15:38     ` Bohdan Trach
2015-04-17 12:13 ` [Qemu-devel] [PATCH RFC 3/3] migration: use checkpoint during migration Bohdan Trach
2015-11-17 12:26   ` Dr. David Alan Gilbert
2015-11-17 15:38     ` Bohdan Trach
2015-11-17 16:05       ` Dr. David Alan Gilbert
2015-11-17 16:34         ` Bohdan Trach
2015-11-17 16:39           ` Dr. David Alan Gilbert
2015-04-24 11:38 ` Bohdan Trach [this message]
2015-05-11 11:13   ` [Qemu-devel] [PATCH RFC, Ping 0/3] Checkpoint-assisted migration proposal Amit Shah
2015-06-09 10:00     ` Bohdan Trach
2015-08-19  9:19       ` Bohdan Trach
2015-09-15 10:39 ` [Qemu-devel] [PATCH RFC " Amit Shah
2015-10-05  8:33   ` Thomas Knauth
2015-10-05  8:59     ` Amit Shah

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=553A2B4E.7070600@mailbox.tu-dresden.de \
    --to=bohdan.trach@mailbox.tu-dresden.de \
    --cc=amit.shah@redhat.com \
    --cc=bv.trach@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=thomas.knauth@googlemail.com \
    /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).