From: Stefan Hajnoczi <stefanha@redhat.com>
To: Zhu Lingshan <lingshan.zhu@intel.com>
Cc: jasowang@redhat.com, mst@redhat.com, eperezma@redhat.com,
cohuck@redhat.com, virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-comment] [RFC PATCH 0/5] virtio: introduce SUSPEND bit and vq state
Date: Mon, 14 Aug 2023 11:47:17 -0400 [thread overview]
Message-ID: <20230814154717.GI3146793@fedora> (raw)
In-Reply-To: <20230814192904.30062-1-lingshan.zhu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2813 bytes --]
On Tue, Aug 15, 2023 at 03:28:59AM +0800, Zhu Lingshan wrote:
> This seires introduces
> 1)a new SUSPEND bit in the device status
> Which is used to suspend the device, so that the device states
> and virtqueue states are stablized.
>
> 2)virtqueue state and accessors, to get and set last_avail_idx
> and last_used_idx of virtqueues.
>
> The main usecase of these new facilities is Live Migration.
>
> Furture work: dirty page tracking and in-flight descriptors.
>
> This is RFC, this series carries on Jason and Eugenio's pervious work.
>
> Any comments are welcome.
In order to support stateful devices like virtiofs, virtio-gpu, or
virtio-crypto it would be necessary to add device state save/load
functionality too.
Even virtio-net needs device state save/load functionality if the VMM is
not intercepting the stateful controlq.
In-flight descriptors can be included in the device state.
In fact, the only reason why I think VIRTIO_F_QUEUE_STATE makes sense is
for easy integration into existing vhost software stacks. Otherwise we
should just define a device state save/load interface along with
standard device state serialization for devices where migration
interoperability is possible. VIRTIO_F_QUEUE_STATE is a small subset of
device state save/load.
I think the convenience of integrating into existing vhost software
stacks is worth the duplication, but I wanted to mention that this
interface will not be enough to live migrate all device types and we'll
need something more in the future.
Stefan
>
> Zhu Lingshan (5):
> virtio: introduce SUSPEND bit in device status
> virtio: introduce vq state as basic facility
> virtio: The actions by the device upon SUSPEND
> virtqueue: constraints for virtqueue state
> virtio-pci: implement VIRTIO_F_QUEUE_STATE
>
> content.tex | 120 ++++++++++++++++++++++++++++++++++++++++++++++
> transport-pci.tex | 15 ++++++
> 2 files changed, 135 insertions(+)
>
> --
> 2.35.3
>
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Zhu Lingshan <lingshan.zhu@intel.com>
Cc: jasowang@redhat.com, mst@redhat.com, eperezma@redhat.com,
cohuck@redhat.com, virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org
Subject: [virtio-dev] Re: [virtio-comment] [RFC PATCH 0/5] virtio: introduce SUSPEND bit and vq state
Date: Mon, 14 Aug 2023 11:47:17 -0400 [thread overview]
Message-ID: <20230814154717.GI3146793@fedora> (raw)
In-Reply-To: <20230814192904.30062-1-lingshan.zhu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2813 bytes --]
On Tue, Aug 15, 2023 at 03:28:59AM +0800, Zhu Lingshan wrote:
> This seires introduces
> 1)a new SUSPEND bit in the device status
> Which is used to suspend the device, so that the device states
> and virtqueue states are stablized.
>
> 2)virtqueue state and accessors, to get and set last_avail_idx
> and last_used_idx of virtqueues.
>
> The main usecase of these new facilities is Live Migration.
>
> Furture work: dirty page tracking and in-flight descriptors.
>
> This is RFC, this series carries on Jason and Eugenio's pervious work.
>
> Any comments are welcome.
In order to support stateful devices like virtiofs, virtio-gpu, or
virtio-crypto it would be necessary to add device state save/load
functionality too.
Even virtio-net needs device state save/load functionality if the VMM is
not intercepting the stateful controlq.
In-flight descriptors can be included in the device state.
In fact, the only reason why I think VIRTIO_F_QUEUE_STATE makes sense is
for easy integration into existing vhost software stacks. Otherwise we
should just define a device state save/load interface along with
standard device state serialization for devices where migration
interoperability is possible. VIRTIO_F_QUEUE_STATE is a small subset of
device state save/load.
I think the convenience of integrating into existing vhost software
stacks is worth the duplication, but I wanted to mention that this
interface will not be enough to live migrate all device types and we'll
need something more in the future.
Stefan
>
> Zhu Lingshan (5):
> virtio: introduce SUSPEND bit in device status
> virtio: introduce vq state as basic facility
> virtio: The actions by the device upon SUSPEND
> virtqueue: constraints for virtqueue state
> virtio-pci: implement VIRTIO_F_QUEUE_STATE
>
> content.tex | 120 ++++++++++++++++++++++++++++++++++++++++++++++
> transport-pci.tex | 15 ++++++
> 2 files changed, 135 insertions(+)
>
> --
> 2.35.3
>
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-08-14 16:29 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 19:28 [virtio-comment] [RFC PATCH 0/5] virtio: introduce SUSPEND bit and vq state Zhu Lingshan
2023-08-14 19:28 ` [virtio-dev] " Zhu Lingshan
2023-08-14 14:20 ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 14:20 ` [virtio-dev] " Stefan Hajnoczi
2023-08-14 15:47 ` Stefan Hajnoczi [this message]
2023-08-14 15:47 ` Stefan Hajnoczi
2023-08-15 1:38 ` Jason Wang
2023-08-15 1:38 ` [virtio-dev] " Jason Wang
2023-08-15 10:14 ` Zhu, Lingshan
2023-08-15 10:14 ` [virtio-dev] " Zhu, Lingshan
2023-08-14 19:29 ` [virtio-comment] [RFC PATCH 1/5] virtio: introduce SUSPEND bit in device status Zhu Lingshan
2023-08-14 19:29 ` [virtio-dev] " Zhu Lingshan
2023-08-14 14:30 ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 14:30 ` [virtio-dev] " Stefan Hajnoczi
2023-08-15 10:31 ` Zhu, Lingshan
2023-08-15 10:31 ` [virtio-dev] " Zhu, Lingshan
2023-08-15 12:29 ` Stefan Hajnoczi
2023-08-15 12:29 ` [virtio-dev] " Stefan Hajnoczi
2023-08-17 15:15 ` Eugenio Perez Martin
2023-08-17 15:15 ` [virtio-dev] " Eugenio Perez Martin
2023-08-17 16:04 ` Stefan Hajnoczi
2023-08-17 16:04 ` [virtio-dev] " Stefan Hajnoczi
2023-08-18 9:55 ` Zhu, Lingshan
2023-08-18 9:55 ` [virtio-dev] " Zhu, Lingshan
2023-08-21 13:45 ` Stefan Hajnoczi
2023-08-21 13:45 ` [virtio-dev] " Stefan Hajnoczi
2023-08-15 0:26 ` [virtio-comment] " Jason Wang
2023-08-15 0:26 ` [virtio-dev] " Jason Wang
2023-08-15 0:37 ` [virtio-comment] " Jason Wang
2023-08-15 0:37 ` [virtio-dev] " Jason Wang
2023-08-15 10:48 ` [virtio-comment] " Zhu, Lingshan
2023-08-15 10:48 ` [virtio-dev] " Zhu, Lingshan
2023-08-16 1:58 ` [virtio-comment] " Jason Wang
2023-08-16 1:58 ` [virtio-dev] " Jason Wang
2023-08-16 2:17 ` [virtio-comment] " Zhu, Lingshan
2023-08-16 2:17 ` [virtio-dev] " Zhu, Lingshan
2023-08-15 10:50 ` [virtio-comment] " Zhu, Lingshan
2023-08-15 10:50 ` [virtio-dev] " Zhu, Lingshan
2023-08-16 2:05 ` [virtio-comment] " Jason Wang
2023-08-16 2:05 ` [virtio-dev] " Jason Wang
2023-08-16 2:20 ` Zhu, Lingshan
2023-08-16 2:20 ` [virtio-dev] " Zhu, Lingshan
2023-08-14 19:29 ` [virtio-comment] [RFC PATCH 2/5] virtio: introduce vq state as basic facility Zhu Lingshan
2023-08-14 19:29 ` [virtio-dev] " Zhu Lingshan
2023-08-14 14:49 ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 14:49 ` Stefan Hajnoczi
2023-08-15 10:53 ` [virtio-comment] " Zhu, Lingshan
2023-08-15 10:53 ` Zhu, Lingshan
2023-08-14 19:29 ` [virtio-comment] [RFC PATCH 3/5] virtio: The actions by the device upon SUSPEND Zhu Lingshan
2023-08-14 19:29 ` [virtio-dev] " Zhu Lingshan
2023-08-14 15:00 ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 15:00 ` [virtio-dev] " Stefan Hajnoczi
2023-08-15 11:07 ` Zhu, Lingshan
2023-08-15 11:07 ` [virtio-dev] " Zhu, Lingshan
2023-08-15 12:33 ` Stefan Hajnoczi
2023-08-15 12:33 ` [virtio-dev] " Stefan Hajnoczi
2023-08-16 4:25 ` Zhu, Lingshan
2023-08-16 4:25 ` [virtio-dev] " Zhu, Lingshan
2023-08-16 12:33 ` Stefan Hajnoczi
2023-08-16 12:33 ` [virtio-dev] " Stefan Hajnoczi
2023-08-15 0:29 ` [virtio-comment] " Jason Wang
2023-08-15 0:29 ` [virtio-dev] " Jason Wang
2023-08-15 11:16 ` [virtio-comment] " Zhu, Lingshan
2023-08-15 11:16 ` Zhu, Lingshan
2023-08-16 2:10 ` [virtio-comment] " Jason Wang
2023-08-16 2:10 ` Jason Wang
2023-08-16 4:53 ` [virtio-comment] " Zhu, Lingshan
2023-08-16 4:53 ` Zhu, Lingshan
2023-08-14 19:29 ` [virtio-comment] [RFC PATCH 4/5] virtqueue: constraints for virtqueue state Zhu Lingshan
2023-08-14 19:29 ` [virtio-dev] " Zhu Lingshan
2023-08-14 15:15 ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 15:15 ` Stefan Hajnoczi
2023-08-15 11:18 ` [virtio-comment] " Zhu, Lingshan
2023-08-15 11:18 ` Zhu, Lingshan
2023-08-15 0:34 ` [virtio-comment] " Jason Wang
2023-08-15 0:34 ` [virtio-dev] " Jason Wang
2023-08-15 11:30 ` [virtio-comment] " Zhu, Lingshan
2023-08-15 11:30 ` [virtio-dev] " Zhu, Lingshan
2023-08-16 2:11 ` [virtio-comment] " Jason Wang
2023-08-16 2:11 ` [virtio-dev] " Jason Wang
2023-08-16 5:07 ` [virtio-comment] " Zhu, Lingshan
2023-08-16 5:07 ` Zhu, Lingshan
2023-08-17 8:31 ` [virtio-comment] " Uminski, Piotr
2023-08-17 8:42 ` Zhu, Lingshan
2023-08-17 8:42 ` [virtio-dev] " Zhu, Lingshan
2023-08-21 4:03 ` Jason Wang
2023-08-21 4:03 ` [virtio-dev] " Jason Wang
2023-08-17 15:19 ` Eugenio Perez Martin
2023-08-17 15:19 ` [virtio-dev] " Eugenio Perez Martin
2023-08-18 9:44 ` [virtio-comment] " Zhu, Lingshan
2023-08-18 9:44 ` [virtio-dev] " Zhu, Lingshan
2023-08-21 9:26 ` [virtio-comment] " Eugenio Perez Martin
2023-08-21 9:26 ` [virtio-dev] " Eugenio Perez Martin
2023-08-21 10:32 ` [virtio-comment] " Zhu, Lingshan
2023-08-21 10:32 ` [virtio-dev] " Zhu, Lingshan
2023-09-05 9:08 ` Zhu, Lingshan
2023-09-05 9:08 ` [virtio-dev] " Zhu, Lingshan
2023-09-07 8:09 ` Eugenio Perez Martin
2023-09-07 8:09 ` [virtio-dev] " Eugenio Perez Martin
2023-09-07 9:34 ` Zhu, Lingshan
2023-09-07 9:34 ` [virtio-dev] " Zhu, Lingshan
2023-09-08 6:23 ` Si-Wei Liu
2023-09-08 6:23 ` [virtio-dev] " Si-Wei Liu
2023-09-08 8:41 ` Zhu, Lingshan
2023-09-08 8:41 ` [virtio-dev] " Zhu, Lingshan
2023-08-14 19:29 ` [virtio-comment] [RFC PATCH 5/5] virtio-pci: implement VIRTIO_F_QUEUE_STATE Zhu Lingshan
2023-08-14 19:29 ` [virtio-dev] " Zhu Lingshan
2023-08-14 15:18 ` [virtio-comment] " Stefan Hajnoczi
2023-08-14 15:18 ` Stefan Hajnoczi
2023-08-15 11:31 ` [virtio-comment] " Zhu, Lingshan
2023-08-15 11:31 ` [virtio-dev] " Zhu, Lingshan
2023-08-15 0:35 ` [virtio-comment] " Jason Wang
2023-08-15 0:35 ` [virtio-dev] " Jason Wang
2023-08-15 11:31 ` [virtio-comment] " Zhu, Lingshan
2023-08-15 11:31 ` [virtio-dev] " Zhu, Lingshan
2023-08-17 3:04 ` [virtio-comment] Re: [RFC PATCH 0/5] virtio: introduce SUSPEND bit and vq state Zhu, Lingshan
2023-08-17 3:04 ` [virtio-dev] " Zhu, Lingshan
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=20230814154717.GI3146793@fedora \
--to=stefanha@redhat.com \
--cc=cohuck@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
/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.