From: Peter Xu <peterx@redhat.com>
To: Steve Sistare <steven.sistare@oracle.com>
Cc: qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Cedric Le Goater <clg@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Marc-Andre Lureau <marcandre.lureau@redhat.com>,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH V3 00/13] allow cpr-reboot for vfio
Date: Tue, 20 Feb 2024 15:49:58 +0800 [thread overview]
Message-ID: <ZdRZpiiD05JS_AkF@x1n> (raw)
In-Reply-To: <1707418446-134863-1-git-send-email-steven.sistare@oracle.com>
On Thu, Feb 08, 2024 at 10:53:53AM -0800, Steve Sistare wrote:
> Allow cpr-reboot for vfio if the guest is in the suspended runstate. The
> guest drivers' suspend methods flush outstanding requests and re-initialize
> the devices, and thus there is no device state to save and restore. The
> user is responsible for suspending the guest before initiating cpr, such as
> by issuing guest-suspend-ram to the qemu guest agent.
>
> Most of the patches in this series enhance migration notifiers so they can
> return an error status and message. The last few patches register a notifier
> for vfio that returns an error if the guest is not suspended.
>
> Changes in V3:
> * update to tip, add RB's
> * replace MigrationStatus with new enum MigrationEventType
> * simplify migrate_fd_connect error recovery
> * support vfio iommufd containers
> * add patches:
> migration: stop vm for cpr
> migration: update cpr-reboot description
This doesn't apply to master anymore, please rebase when repost, thanks.
--
Peter Xu
next prev parent reply other threads:[~2024-02-20 7:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 18:53 [PATCH V3 00/13] allow cpr-reboot for vfio Steve Sistare
2024-02-08 18:53 ` [PATCH V3 01/13] notify: pass error to notifier with return Steve Sistare
2024-02-12 9:08 ` David Hildenbrand
2024-02-08 18:53 ` [PATCH V3 02/13] migration: remove error from notifier data Steve Sistare
2024-02-12 9:08 ` David Hildenbrand
2024-02-08 18:53 ` [PATCH V3 03/13] migration: convert to NotifierWithReturn Steve Sistare
2024-02-12 9:10 ` David Hildenbrand
2024-02-08 18:53 ` [PATCH V3 04/13] migration: MigrationEvent for notifiers Steve Sistare
2024-02-12 9:11 ` David Hildenbrand
2024-02-20 6:38 ` Peter Xu
2024-02-08 18:53 ` [PATCH V3 05/13] migration: remove postcopy_after_devices Steve Sistare
2024-02-20 6:42 ` Peter Xu
2024-02-08 18:53 ` [PATCH V3 06/13] migration: MigrationNotifyFunc Steve Sistare
2024-02-12 9:14 ` David Hildenbrand
2024-02-20 6:48 ` Peter Xu
2024-02-08 18:54 ` [PATCH V3 07/13] migration: per-mode notifiers Steve Sistare
2024-02-12 9:16 ` David Hildenbrand
2024-02-20 6:51 ` Peter Xu
2024-02-08 18:54 ` [PATCH V3 08/13] migration: refactor migrate_fd_connect failures Steve Sistare
2024-02-12 9:17 ` David Hildenbrand
2024-02-08 18:54 ` [PATCH V3 09/13] migration: notifier error checking Steve Sistare
2024-02-12 9:24 ` David Hildenbrand
2024-02-12 15:37 ` Steven Sistare
2024-02-20 7:12 ` Peter Xu
2024-02-20 22:12 ` Steven Sistare
2024-02-08 18:54 ` [PATCH V3 10/13] migration: stop vm for cpr Steve Sistare
2024-02-20 7:33 ` Peter Xu
2024-02-20 22:19 ` Steven Sistare
2024-02-21 21:20 ` Steven Sistare
2024-02-22 9:12 ` Peter Xu
2024-02-22 9:30 ` Peter Xu
2024-02-22 13:29 ` Steven Sistare
2024-02-21 21:23 ` Steven Sistare
2024-02-22 9:03 ` Peter Xu
2024-02-22 13:24 ` Steven Sistare
2024-02-08 18:54 ` [PATCH V3 11/13] vfio: register container " Steve Sistare
2024-02-08 18:54 ` [PATCH V3 12/13] vfio: allow cpr-reboot migration if suspended Steve Sistare
2024-02-21 18:32 ` Steven Sistare
2024-02-08 18:54 ` [PATCH V3 13/13] migration: update cpr-reboot description Steve Sistare
2024-02-20 7:49 ` Peter Xu [this message]
2024-02-20 22:32 ` [PATCH V3 00/13] allow cpr-reboot for vfio Steven Sistare
2024-02-21 2:13 ` Peter Xu
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=ZdRZpiiD05JS_AkF@x1n \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=david@redhat.com \
--cc=farosas@suse.de \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=steven.sistare@oracle.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.