From: Steven Sistare <steven.sistare@oracle.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, "Juan Quintela" <quintela@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Leonardo Bras" <leobras@redhat.com>
Subject: Re: [PATCH V7 00/12] fix migration of suspended runstate
Date: Mon, 11 Dec 2023 08:31:17 -0500 [thread overview]
Message-ID: <e96986f5-6e7a-4c78-a016-057a98d9a3f5@oracle.com> (raw)
In-Reply-To: <ZXaytc6glZWRC8O9@x1n>
On 12/11/2023 1:56 AM, Peter Xu wrote:
> On Wed, Dec 06, 2023 at 12:30:02PM -0500, Steven Sistare wrote:
>> cpus: stop vm in suspended runstate
>
> This patch still didn't copy the QAPI maintainers, please remember to do so
> in a new post.
>
> Maybe it would be easier to move the QAPI doc changes into a separate
> patch?
This was intentional. I did not cc them for the whole series to spare them from
excess email. You cc'd them for "[PATCH V6 03/14] cpus: stop vm in suspended runstate"
they had no comments, and there is no change for V7, so I assumed we are OK, but I will
cc them again for that patch to be sure.
- Steve
next prev parent reply other threads:[~2023-12-11 13:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 17:23 [PATCH V7 00/12] fix migration of suspended runstate Steve Sistare
2023-12-06 17:23 ` [PATCH V7 01/12] cpus: vm_was_suspended Steve Sistare
2023-12-06 17:23 ` [PATCH V7 02/12] cpus: stop vm in suspended runstate Steve Sistare
2023-12-06 18:45 ` Philippe Mathieu-Daudé
2023-12-06 19:19 ` Steven Sistare
2023-12-06 20:48 ` Philippe Mathieu-Daudé
2023-12-06 21:09 ` Philippe Mathieu-Daudé
2023-12-11 6:25 ` Peter Xu
2023-12-11 13:37 ` Steven Sistare
2023-12-06 17:23 ` [PATCH V7 03/12] cpus: check running not RUN_STATE_RUNNING Steve Sistare
2023-12-06 17:23 ` [PATCH V7 04/12] cpus: vm_resume Steve Sistare
2023-12-06 17:23 ` [PATCH V7 05/12] migration: propagate suspended runstate Steve Sistare
2023-12-08 16:37 ` Fabiano Rosas
2023-12-08 17:28 ` Steven Sistare
2023-12-11 6:46 ` Peter Xu
2023-12-11 13:23 ` Steven Sistare
2023-12-06 17:23 ` [PATCH V7 06/12] migration: preserve " Steve Sistare
2023-12-06 17:23 ` [PATCH V7 07/12] migration: preserve suspended for snapshot Steve Sistare
2023-12-06 17:23 ` [PATCH V7 08/12] migration: preserve suspended for bg_migration Steve Sistare
2023-12-06 17:23 ` [PATCH V7 09/12] tests/qtest: migration events Steve Sistare
2023-12-06 17:23 ` [PATCH V7 10/12] tests/qtest: option to suspend during migration Steve Sistare
2023-12-06 17:23 ` [PATCH V7 11/12] tests/qtest: precopy migration with suspend Steve Sistare
2023-12-08 16:37 ` Fabiano Rosas
2023-12-11 6:54 ` Peter Xu
2023-12-06 17:23 ` [PATCH V7 12/12] tests/qtest: postcopy " Steve Sistare
2023-12-11 6:54 ` Peter Xu
2023-12-06 17:30 ` [PATCH V7 00/12] fix migration of suspended runstate Steven Sistare
2023-12-11 6:56 ` Peter Xu
2023-12-11 13:31 ` Steven Sistare [this message]
2023-12-12 8:54 ` Peter Xu
-- strict thread matches above, loose matches on Subject: below --
2023-12-06 17:12 Steve Sistare
2023-12-06 17:16 ` Steven Sistare
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=e96986f5-6e7a-4c78-a016-057a98d9a3f5@oracle.com \
--to=steven.sistare@oracle.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@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).