From: David Stevens <stevensd@chromium.org>
To: "Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org
Cc: parav@nvidia.com, David Stevens <stevensd@chromium.org>
Subject: [virtio-comment] [PATCH v5 0/1] Define a low power mode for devices
Date: Tue, 27 Feb 2024 10:53:44 +0900 [thread overview]
Message-ID: <20240227015345.3614965-1-stevensd@chromium.org> (raw)
The Linux patch [1] added support for suspending virtio devices using
native PCI power management. However, Linux does PCI power management
during the noirq phase of suspend and resume. Without a mechanism to
suspend/resume virtio devices when the driver is suspended/resumed in
the early phase of suspend/late phase of resume, there is a window where
interrupts can be lost.
This revision of the patch tries to reconcile with the similar proposal
[2], which was pulled out of one of a patch series attempting to add
live migration support to virtio [3].
[1] https://lore.kernel.org/lkml/20231208070754.3132339-1-stevensd@chromium.org/
[2] https://lore.kernel.org/all/20240218132306.83456-1-lingshan.zhu@intel.com/
[3] https://lore.kernel.org/all/20231103103437.72784-1-lingshan.zhu@intel.com/
v4 -> v5:
- Use a device status bit instead of a pci capability.
- Reconcile differences with [2] by specifying that devices should
finish processing buffers before suspending and that devices
shouldn't access virtqueues while suspended.
- Add more details about state transition acknowledgment.
v3 -> v4:
- Define virtio-pci specific power management that can be used in
conjunction with PCI power management.
v2 -> v3:
- Use different words for some concepts to avoid conflicts with other
parts of the spec.
- Rewrite various sentences to improve clarity.
v1 -> v2:
- Define virtio-pci support on top of PCI power management.
- Add more conformance requirements.
David Stevens (1):
Add SUSPEND bit to device status
content.tex | 89 ++++++++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 84 insertions(+), 5 deletions(-)
--
2.44.0.rc0.258.g7320e95886-goog
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/
next reply other threads:[~2024-02-27 1:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 1:53 David Stevens [this message]
2024-02-27 1:53 ` [virtio-comment] [PATCH v5 1/1] Add SUSPEND bit to device status David Stevens
2024-02-27 2:22 ` [virtio-comment] " Zhu, Lingshan
2024-02-27 7:59 ` David Stevens
2024-02-27 8:51 ` Zhu, Lingshan
2024-02-28 1:18 ` David Stevens
2024-02-28 6:45 ` Zhu, Lingshan
2024-02-29 3:20 ` David Stevens
2024-02-29 8:55 ` [virtio-comment] Re: [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=20240227015345.3614965-1-stevensd@chromium.org \
--to=stevensd@chromium.org \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).