From: David Stevens <stevensd@chromium.org>
To: "Michael S . Tsirkin" <mst@redhat.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org
Cc: David Stevens <stevensd@chromium.org>
Subject: [virtio-comment] [PATCH v3 0/1] Define low power mode for devices
Date: Mon, 4 Dec 2023 18:41:22 +0900 [thread overview]
Message-ID: <20231204094123.856214-1-stevensd@chromium.org> (raw)
The virtio spec currently does not include the concept of device power
management. The lack means that there is no good action drivers can take
when they are requested to put the device into a low power state (e.g.
when a guest is entering a system-wide low power state like S0ix/S3).
Stateless devices can be handled - albeit inefficiently - by resetting
and reinitialzing the device. However, stateful devices cannot support
this situation. This patch defines a low power mode for devices that can
be used in this situation.
Low power mode is mostly defined at the transport layer, and all
device-side power optimizations are optional. This avoids the need for
invasive device-by-device definitions. It also pushes the requirement
onto the device side, to simplify what driver side changes are
necessary to just [1].
I believe this patch may address the virtio-gpu issue which [2] is
trying to address by avoiding the reset altogether when the guest enters
S3.
[1] https://lore.kernel.org/lkml/20231113055138.117392-1-stevensd@chromium.org/
[2] https://lore.kernel.org/lkml/20230919114242.2283646-1-Jiqian.Chen@amd.com/
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):
Define a low power mode for devices
content.tex | 61 +++++++++++++++++++++++++++++++++++++++++++++++
transport-pci.tex | 9 +++++++
2 files changed, 70 insertions(+)
--
2.43.0.rc2.451.g8631bc7472-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:[~2023-12-04 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 9:41 David Stevens [this message]
2023-12-04 9:41 ` [virtio-comment] [PATCH v3 1/1] Define a low power mode for devices David Stevens
2023-12-05 4:18 ` Jason Wang
2023-12-05 10:58 ` David Stevens
2023-12-06 9:16 ` Jason Wang
2023-12-06 10:17 ` Michael S. Tsirkin
2023-12-07 4:16 ` Jason Wang
2023-12-07 4:54 ` David Stevens
2023-12-07 5:35 ` Jason Wang
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=20231204094123.856214-1-stevensd@chromium.org \
--to=stevensd@chromium.org \
--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 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).