From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: David Stevens <stevensd@chromium.org>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH v3 1/1] Define a low power mode for devices
Date: Wed, 6 Dec 2023 05:17:27 -0500 [thread overview]
Message-ID: <20231206051652-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEuGY9y5Zt9UdL+4V3tntnR4EyHHCRqX_P4QtmAOL0-Pew@mail.gmail.com>
On Wed, Dec 06, 2023 at 05:16:04PM +0800, Jason Wang wrote:
> On Tue, Dec 5, 2023 at 6:58 PM David Stevens <stevensd@chromium.org> wrote:
> >
> > On Tue, Dec 5, 2023 at 1:18 PM Jason Wang <jasowang@redhat.com> wrote:
> > >
> > > On Mon, Dec 4, 2023 at 5:41 PM David Stevens <stevensd@chromium.org> wrote:
> > > >
> > > > Define a low power mode for virtio devices where the devices are
> > > > expected to maintain their state. This gives drivers an option for power
> > > > management besides simply resetting their device. In the virtualization
> > > > use case, this allows the guest to be suspended even with stateful
> > > > virtio devices like gpu and fs.
> > > >
> > > > Low power mode is primarily defined at the transport layer. The only
> > > > part that depends on device-type specific details is whether a given
> > > > virtqueue is device driven or driver driven.
> > > >
> > > > This change only defines the transport-specific implementation for
> > > > Virtio over PCI.
> > >
> > > A dumb question, if this is only for PCI, can the device just
> > > implement no_soft_reset via PMC?
> >
> > This is basically No_Soft_Reset, yes. If a change similar to [1] would
> > be acceptable based only on the No_Soft_Reset bit even with no concept
> > of power management in the virtio spec, then I personally don't have
> > any problems with that.
> >
> > [1] https://lore.kernel.org/lkml/20231113055138.117392-1-stevensd@chromium.org/
>
> So if I read the code correctly, the current Qemu advertises PM but
> without no_soft_reset.
>
> So this patch seems to break e.g virtio-net and doesn't fix virtio-GPU.
>
> Thanks
>
> >
> > -David
> >
what is the breakage exactly? Maybe we need a new feature bit?
--
MST
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/
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: David Stevens <stevensd@chromium.org>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org
Subject: [virtio-dev] Re: [virtio-comment] [PATCH v3 1/1] Define a low power mode for devices
Date: Wed, 6 Dec 2023 05:17:27 -0500 [thread overview]
Message-ID: <20231206051652-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEuGY9y5Zt9UdL+4V3tntnR4EyHHCRqX_P4QtmAOL0-Pew@mail.gmail.com>
On Wed, Dec 06, 2023 at 05:16:04PM +0800, Jason Wang wrote:
> On Tue, Dec 5, 2023 at 6:58 PM David Stevens <stevensd@chromium.org> wrote:
> >
> > On Tue, Dec 5, 2023 at 1:18 PM Jason Wang <jasowang@redhat.com> wrote:
> > >
> > > On Mon, Dec 4, 2023 at 5:41 PM David Stevens <stevensd@chromium.org> wrote:
> > > >
> > > > Define a low power mode for virtio devices where the devices are
> > > > expected to maintain their state. This gives drivers an option for power
> > > > management besides simply resetting their device. In the virtualization
> > > > use case, this allows the guest to be suspended even with stateful
> > > > virtio devices like gpu and fs.
> > > >
> > > > Low power mode is primarily defined at the transport layer. The only
> > > > part that depends on device-type specific details is whether a given
> > > > virtqueue is device driven or driver driven.
> > > >
> > > > This change only defines the transport-specific implementation for
> > > > Virtio over PCI.
> > >
> > > A dumb question, if this is only for PCI, can the device just
> > > implement no_soft_reset via PMC?
> >
> > This is basically No_Soft_Reset, yes. If a change similar to [1] would
> > be acceptable based only on the No_Soft_Reset bit even with no concept
> > of power management in the virtio spec, then I personally don't have
> > any problems with that.
> >
> > [1] https://lore.kernel.org/lkml/20231113055138.117392-1-stevensd@chromium.org/
>
> So if I read the code correctly, the current Qemu advertises PM but
> without no_soft_reset.
>
> So this patch seems to break e.g virtio-net and doesn't fix virtio-GPU.
>
> Thanks
>
> >
> > -David
> >
what is the breakage exactly? Maybe we need a new feature bit?
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-12-06 10:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 9:41 [virtio-comment] [PATCH v3 0/1] Define low power mode for devices David Stevens
2023-12-04 9:41 ` [virtio-dev] " David Stevens
2023-12-04 9:41 ` [virtio-comment] [PATCH v3 1/1] Define a " David Stevens
2023-12-04 9:41 ` [virtio-dev] " David Stevens
2023-12-05 4:18 ` [virtio-comment] " Jason Wang
2023-12-05 4:18 ` [virtio-dev] " Jason Wang
2023-12-05 10:58 ` David Stevens
2023-12-05 10:58 ` [virtio-dev] " David Stevens
2023-12-06 9:16 ` Jason Wang
2023-12-06 9:16 ` [virtio-dev] " Jason Wang
2023-12-06 10:17 ` Michael S. Tsirkin [this message]
2023-12-06 10:17 ` Michael S. Tsirkin
2023-12-07 4:16 ` Jason Wang
2023-12-07 4:16 ` [virtio-dev] " Jason Wang
2023-12-07 4:54 ` David Stevens
2023-12-07 4:54 ` [virtio-dev] " David Stevens
2023-12-07 5:35 ` Jason Wang
2023-12-07 5:35 ` [virtio-dev] " 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=20231206051652-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=stevensd@chromium.org \
--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.