qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: qemu-devel@nongnu.org,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Leonardo Bras Soares Passos" <lsoaresp@redhat.com>,
	"Juan Quintela" <quintela@redhat.com>
Subject: Re: [PATCH] docs/migration: Update postcopy bits
Date: Thu, 6 Jul 2023 07:53:49 -0400	[thread overview]
Message-ID: <ZKarTWisVKjpo+Wr@x1n> (raw)
In-Reply-To: <ddb293c6-2475-8fbb-7d84-f276ce17956a@redhat.com>

On Thu, Jul 06, 2023 at 12:15:47PM +0200, Laszlo Ersek wrote:
> One suggestion, to squash in:
> 
> diff --git a/docs/devel/migration.rst b/docs/devel/migration.rst
> index 6f65c23b47dc..3294679936b2 100644
> --- a/docs/devel/migration.rst
> +++ b/docs/devel/migration.rst
> @@ -594,8 +594,7 @@ Postcopy
>  'Postcopy' migration is a way to deal with migrations that refuse to converge
>  (or take too long to converge) its plus side is that there is an upper bound on
>  the amount of migration traffic and time it takes, the down side is that during
> -the postcopy phase, a failure of *either* side or the network connection causes
> -the guest to be lost.
> +the postcopy phase, a failure of *either* side causes the guest to be lost.
>  
>  In postcopy the destination CPUs are started before all the memory has been
>  transferred, and accesses to pages that are yet to be transferred cause
> 
> This removes "or the network connection" as a fatal failure.

Makes sense.

> 
> Acked-by: Laszlo Ersek <lersek@redhat.com>

Thanks!

-- 
Peter Xu



      reply	other threads:[~2023-07-06 11:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 20:02 [PATCH] docs/migration: Update postcopy bits Peter Xu
2023-07-06 10:15 ` Laszlo Ersek
2023-07-06 11:53   ` Peter Xu [this message]

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=ZKarTWisVKjpo+Wr@x1n \
    --to=peterx@redhat.com \
    --cc=berrange@redhat.com \
    --cc=lersek@redhat.com \
    --cc=lsoaresp@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).