From: "Tian, Kevin" <kevin.tian@intel.com>
To: Anthony DeRossi <ajderossi@gmail.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: "alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"abhsahu@nvidia.com" <abhsahu@nvidia.com>,
"yishaih@nvidia.com" <yishaih@nvidia.com>
Subject: RE: [PATCH v5 2/3] vfio: Export the device set open count
Date: Wed, 9 Nov 2022 03:37:25 +0000 [thread overview]
Message-ID: <BN9PR11MB5276FBE954A04B3A2970AFE98C3E9@BN9PR11MB5276.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221105224458.8180-3-ajderossi@gmail.com>
> From: Anthony DeRossi <ajderossi@gmail.com>
> Sent: Sunday, November 6, 2022 6:45 AM
>
> The open count of a device set is the sum of the open counts of all
> devices in the set. Drivers can use this value to determine whether
> shared resources are in use without tracking them manually or accessing
> the private open_count in vfio_device.
>
> Signed-off-by: Anthony DeRossi <ajderossi@gmail.com>
Apart from remarks from Alex/Jason, good to me:
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
next prev parent reply other threads:[~2022-11-09 3:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 22:44 [PATCH v5 0/3] vfio/pci: Check the device set open count on reset Anthony DeRossi
2022-11-05 22:44 ` [PATCH v5 1/3] vfio: Fix container device registration life cycle Anthony DeRossi
2022-11-09 0:43 ` Jason Gunthorpe
2022-11-09 3:36 ` Tian, Kevin
2022-11-05 22:44 ` [PATCH v5 2/3] vfio: Export the device set open count Anthony DeRossi
2022-11-08 23:52 ` Alex Williamson
2022-11-09 0:48 ` Jason Gunthorpe
2022-11-09 16:04 ` Alex Williamson
2022-11-09 3:37 ` Tian, Kevin [this message]
2022-11-05 22:44 ` [PATCH v5 3/3] vfio/pci: Check the device set open count on reset Anthony DeRossi
2022-11-09 0:53 ` Jason Gunthorpe
2022-11-09 3:38 ` Tian, Kevin
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=BN9PR11MB5276FBE954A04B3A2970AFE98C3E9@BN9PR11MB5276.namprd11.prod.outlook.com \
--to=kevin.tian@intel.com \
--cc=abhsahu@nvidia.com \
--cc=ajderossi@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kvm@vger.kernel.org \
--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.