qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "Leonardo Brás" <leobras@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	qemu-devel@nongnu.org, Li Xiaohui <xiaohli@redhat.com>
Subject: Re: [PATCH v1 1/1] migration: Fix yank on postcopy multifd crashing guest after migration
Date: Thu, 9 Feb 2023 09:22:53 -0500	[thread overview]
Message-ID: <Y+UBvUfHlkqFcoUn@x1n> (raw)
In-Reply-To: <038b3c6d5f0ee3b3da5c9e53029a51b8b39d4922.camel@redhat.com>

On Thu, Feb 09, 2023 at 01:14:12AM -0300, Leonardo Brás wrote:
> I got side-tracked on this issue.
> 
> Is there any patch disabling multifd + postcopy, or would it be fine to go back
> working on a V2 for this one?

IMHO it'll always make sense to post a new version for the immediate crash.

Personally I still think we should disable the two features being present
together until the full solution, but that can be discussed separately.

Thanks,

-- 
Peter Xu



      reply	other threads:[~2023-02-09 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  5:56 [PATCH v1 1/1] migration: Fix yank on postcopy multifd crashing guest after migration Leonardo Bras
2022-11-09 13:31 ` Dr. David Alan Gilbert
2022-11-09 16:59   ` Leonardo Bras Soares Passos
2022-11-10 13:47 ` Juan Quintela
2022-11-15  2:32   ` Leonardo Bras Soares Passos
2022-11-24 16:04 ` Peter Xu
2022-11-29 20:28   ` Leonardo Bras Soares Passos
2022-11-29 20:50     ` Peter Xu
2023-02-09  4:14       ` Leonardo Brás
2023-02-09 14:22         ` 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=Y+UBvUfHlkqFcoUn@x1n \
    --to=peterx@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=leobras@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=xiaohli@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).