[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220530122546.GZ1343366@nvidia.com>
Date: Mon, 30 May 2022 09:25:46 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Abhishek Sahu <abhsahu@...dia.com>
Cc: Alex Williamson <alex.williamson@...hat.com>,
Cornelia Huck <cohuck@...hat.com>,
Yishai Hadas <yishaih@...dia.com>,
Shameer Kolothum <shameerali.kolothum.thodi@...wei.com>,
Kevin Tian <kevin.tian@...el.com>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Max Gurtovoy <mgurtovoy@...dia.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
linux-pm@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH v3 8/8] vfio/pci: Add the support for PCI D3cold state
On Mon, May 30, 2022 at 04:45:59PM +0530, Abhishek Sahu wrote:
> 1. In real use case, config or any other ioctl should not come along
> with VFIO_DEVICE_FEATURE_POWER_MANAGEMENT ioctl request.
>
> 2. Maintain some 'access_count' which will be incremented when we
> do any config space access or ioctl.
Please don't open code locks - if you need a lock then write a proper
lock. You can use the 'try' variants to bail out in cases where that
is appropriate.
Jason
Powered by blists - more mailing lists