From: Jason Gunthorpe <jgg@nvidia.com>
To: Abhishek Sahu <abhsahu@nvidia.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Yishai Hadas <yishaih@nvidia.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
Kevin Tian <kevin.tian@intel.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-pm@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v5 1/5] vfio: Add the device features for the low power entry and exit
Date: Tue, 26 Jul 2022 14:23:56 -0300 [thread overview]
Message-ID: <20220726172356.GH4438@nvidia.com> (raw)
In-Reply-To: <bd7bca18-ae07-c04a-23d3-bf71245da0cc@nvidia.com>
On Tue, Jul 26, 2022 at 06:17:18PM +0530, Abhishek Sahu wrote:
> Thanks Alex for your thorough review of uAPI.
> I have incorporated all the suggestions.
> Following is the updated uAPI.
>
> /*
> * Upon VFIO_DEVICE_FEATURE_SET, allow the device to be moved into a low power
> * state with the platform-based power management. Device use of lower power
> * states depends on factors managed by the runtime power management core,
> * including system level support and coordinating support among dependent
> * devices. Enabling device low power entry does not guarantee lower power
> * usage by the device, nor is a mechanism provided through this feature to
> * know the current power state of the device. If any device access happens
> * (either from the host or through the vfio uAPI) when the device is in the
> * low power state, then the host will move the device out of the low power
> * state as necessary prior to the access. Once the access is completed, the
> * device may re-enter the low power state. For single shot low power support
> * with wake-up notification, see
> * VFIO_DEVICE_FEATURE_LOW_POWER_ENTRY_WITH_WAKEUP below. Access to mmap'd
> * device regions is disabled on LOW_POWER_ENTRY and may only be resumed after
> * calling LOW_POWER_EXIT.
> */
> #define VFIO_DEVICE_FEATURE_LOW_POWER_ENTRY 3
>
> /*
> * This device feature has the same behavior as
> * VFIO_DEVICE_FEATURE_LOW_POWER_ENTRY with the exception that the user
> * provides an eventfd for wake-up notification.
It feels like this should be one entry point instead of two.
A flag "automatic re-sleep" and an optional eventfd (-1 means not
provided) seems to capture both of these behaviors in a bit clearer
and extendable way.
Jason
next prev parent reply other threads:[~2022-07-26 17:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 12:15 [PATCH v5 0/5] vfio/pci: power management changes Abhishek Sahu
2022-07-19 12:15 ` [PATCH v5 1/5] vfio: Add the device features for the low power entry and exit Abhishek Sahu
2022-07-21 22:34 ` Alex Williamson
2022-07-25 14:40 ` Abhishek Sahu
2022-07-25 22:09 ` Alex Williamson
2022-07-26 12:47 ` Abhishek Sahu
2022-07-26 13:13 ` Cornelia Huck
2022-07-26 14:17 ` Alex Williamson
2022-07-26 17:23 ` Jason Gunthorpe [this message]
2022-07-27 6:07 ` Abhishek Sahu
2022-08-01 18:42 ` Alex Williamson
2022-08-02 14:04 ` Jason Gunthorpe
2022-08-02 15:41 ` Alex Williamson
2022-08-02 16:35 ` Jason Gunthorpe
2022-08-02 16:57 ` Alex Williamson
2022-08-02 17:01 ` Jason Gunthorpe
2022-08-03 6:32 ` Abhishek Sahu
2022-07-19 12:15 ` [PATCH v5 2/5] vfio: Increment the runtime PM usage count during IOCTL call Abhishek Sahu
2022-07-21 22:34 ` Alex Williamson
2022-07-19 12:15 ` [PATCH v5 3/5] vfio/pci: Mask INTx during runtime suspend Abhishek Sahu
2022-07-19 12:15 ` [PATCH v5 4/5] vfio/pci: Implement VFIO_DEVICE_FEATURE_LOW_POWER_ENTRY/EXIT Abhishek Sahu
2022-07-21 22:34 ` Alex Williamson
2022-07-25 14:48 ` Abhishek Sahu
2022-07-19 12:15 ` [PATCH v5 5/5] vfio/pci: Implement VFIO_DEVICE_FEATURE_LOW_POWER_ENTRY_WITH_WAKEUP Abhishek Sahu
2022-07-21 22:34 ` Alex Williamson
2022-07-25 15:04 ` Abhishek Sahu
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=20220726172356.GH4438@nvidia.com \
--to=jgg@nvidia.com \
--cc=abhsahu@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=cohuck@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=rafael@kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=yishaih@nvidia.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.