All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Elena Ufimtseva <elena.ufimtseva@oracle.com>
Cc: qemu-devel@nongnu.org, eduardo@habkost.net,
	marcel.apfelbaum@gmail.com, philmd@linaro.org,
	wangyanan55@huawei.com, farosas@suse.de, eblake@redhat.com,
	armbru@redhat.com
Subject: Re: [PATCH RFC 1/2] migration: abort when switchover limit exceeded
Date: Mon, 24 Jun 2024 15:19:48 -0400	[thread overview]
Message-ID: <ZnnG1PrbQ_7nOu9e@x1n> (raw)
In-Reply-To: <20240621143221.198784-2-elena.ufimtseva@oracle.com>

On Fri, Jun 21, 2024 at 07:32:20AM -0700, Elena Ufimtseva wrote:
> @@ -16,6 +16,7 @@ bool migrate_background_snapshot(void);
>  bool migrate_dirty_limit(void);
>  bool migrate_postcopy_ram(void);
>  bool migrate_switchover_ack(void);
> +bool migrate_switchover_abort(void);

This does look like an interesting feature.  The challenge might reside in
the details.  For the interface part, one parameter should be enough?
Since when set to 0 it can already mean disabled.

Thanks,

-- 
Peter Xu



  reply	other threads:[~2024-06-24 19:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 14:32 [PATCH RFC 0/2] migration: introduce strict SLA Elena Ufimtseva
2024-06-21 14:32 ` [PATCH RFC 1/2] migration: abort when switchover limit exceeded Elena Ufimtseva
2024-06-24 19:19   ` Peter Xu [this message]
2024-06-25 19:05   ` Daniel P. Berrangé
2024-06-21 14:32 ` [PATCH RFC 2/2] migration: abort on destination if " Elena Ufimtseva
2024-06-24 19:41   ` Peter Xu
2024-06-25 11:38     ` Joao Martins
2024-06-25 14:53       ` Peter Xu
2024-06-25 16:31         ` Joao Martins
2024-06-25 19:03           ` Peter Xu
2024-06-26 11:04             ` Joao Martins
2024-06-26 18:41               ` Peter Xu
2024-07-26  7:41                 ` Elena Ufimtseva
2024-08-21 19:45                   ` Peter Xu
2024-06-25 18:37         ` Daniel P. Berrangé
2024-06-26 11:29           ` Joao Martins
2024-06-26 11:34             ` Daniel P. Berrangé
2024-06-26 12:12               ` Joao Martins
2024-06-26 12:20                 ` Daniel P. Berrangé
2024-06-25 19:12   ` Daniel P. Berrangé

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=ZnnG1PrbQ_7nOu9e@x1n \
    --to=peterx@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=elena.ufimtseva@oracle.com \
    --cc=farosas@suse.de \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wangyanan55@huawei.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 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.