From: Jason Gunthorpe <jgg@ziepe.ca>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Zhi Wang <zhi.a.wang@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Eric Farman <farman@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Tony Krowiak <akrowiak@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Diana Craciun <diana.craciun@oss.nxp.com>,
Cornelia Huck <cohuck@redhat.com>,
Longfang Liu <liulongfang@huawei.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
Yishai Hadas <yishaih@nvidia.com>,
Eric Auger <eric.auger@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Abhishek Sahu <abhsahu@nvidia.com>,
intel-gvt-dev@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, Yi Liu <yi.l.liu@intel.com>
Subject: Re: [PATCH 15/15] vfio: Add struct device to vfio_device
Date: Tue, 30 Aug 2022 20:53:17 -0300 [thread overview]
Message-ID: <Yw6i7btDKcUDPADP@ziepe.ca> (raw)
In-Reply-To: <20220830161838.4aa47045.alex.williamson@redhat.com>
On Tue, Aug 30, 2022 at 04:18:38PM -0600, Alex Williamson wrote:
> On Sun, 28 Aug 2022 01:10:37 +0800
> Kevin Tian <kevin.tian@intel.com> wrote:
>
> > From: Yi Liu <yi.l.liu@intel.com>
> >
> > and replace kref. With it a 'vfio-dev/vfioX' node is created under the
> > sysfs path of the parent, indicating the device is bound to a vfio
> > driver, e.g.:
> >
> > /sys/devices/pci0000\:6f/0000\:6f\:01.0/vfio-dev/vfio0
> >
> > It is also a preparatory step toward adding cdev for supporting future
> > device-oriented uAPI.
>
> Shall we start Documentation/ABI/testing/vfio-dev now? Thanks.
I always thought that was something to use when adding new custom
sysfs attributes?
Here we are just creating a standard struct device with its standard
sysfs?
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Matthew Rosato <mjrosato@linux.ibm.com>,
David Airlie <airlied@linux.ie>,
Eric Farman <farman@linux.ibm.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Kirti Wankhede <kwankhede@nvidia.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Diana Craciun <diana.craciun@oss.nxp.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Longfang Liu <liulongfang@huawei.com>,
linux-s390@vger.kernel.org, Yi Liu <yi.l.liu@intel.com>,
kvm@vger.kernel.org, Leon Romanovsky <leon@kernel.org>,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
intel-gfx@lists.freedesktop.org, Zhi Wang <zhi.a.wang@intel.com>,
Tony Krowiak <akrowiak@linux.ibm.com>,
Kevin Tian <kevin.tian@intel.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Eric Auger <eric.auger@redhat.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gvt-dev@lists.freedesktop.org,
Jason Herne <jjherne@linux.ibm.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Yishai Hadas <yishaih@nvidia.com>,
Cornelia Huck <cohuck@redhat.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
Sven Schnelle <svens@linux.ibm.com>,
Abhishek Sahu <abhsahu@nvidia.com>
Subject: Re: [PATCH 15/15] vfio: Add struct device to vfio_device
Date: Tue, 30 Aug 2022 20:53:17 -0300 [thread overview]
Message-ID: <Yw6i7btDKcUDPADP@ziepe.ca> (raw)
In-Reply-To: <20220830161838.4aa47045.alex.williamson@redhat.com>
On Tue, Aug 30, 2022 at 04:18:38PM -0600, Alex Williamson wrote:
> On Sun, 28 Aug 2022 01:10:37 +0800
> Kevin Tian <kevin.tian@intel.com> wrote:
>
> > From: Yi Liu <yi.l.liu@intel.com>
> >
> > and replace kref. With it a 'vfio-dev/vfioX' node is created under the
> > sysfs path of the parent, indicating the device is bound to a vfio
> > driver, e.g.:
> >
> > /sys/devices/pci0000\:6f/0000\:6f\:01.0/vfio-dev/vfio0
> >
> > It is also a preparatory step toward adding cdev for supporting future
> > device-oriented uAPI.
>
> Shall we start Documentation/ABI/testing/vfio-dev now? Thanks.
I always thought that was something to use when adding new custom
sysfs attributes?
Here we are just creating a standard struct device with its standard
sysfs?
Jason
next prev parent reply other threads:[~2022-08-30 23:53 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 17:10 [Intel-gfx] [PATCH 00/15] Tidy up vfio_device life cycle Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-27 10:09 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-08-27 10:29 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-08-27 17:10 ` [Intel-gfx] [PATCH 01/15] vfio: Add helpers for unifying " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-30 13:42 ` [Intel-gfx] " Anthony Krowiak
2022-08-30 13:42 ` Anthony Krowiak
2022-08-30 15:10 ` Jason Gunthorpe
2022-08-30 15:10 ` Jason Gunthorpe
2022-08-30 19:43 ` [Intel-gfx] " Anthony Krowiak
2022-08-30 19:43 ` Anthony Krowiak
2022-08-30 19:43 ` Anthony Krowiak
2022-08-31 6:03 ` [Intel-gfx] " Tian, Kevin
2022-08-31 6:03 ` Tian, Kevin
2022-08-31 6:03 ` Tian, Kevin
2022-08-27 17:10 ` [Intel-gfx] [PATCH 02/15] vfio/pci: Use the new device life cycle helpers Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-27 17:10 ` [Intel-gfx] [PATCH 03/15] vfio/mlx5: " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-27 17:10 ` [Intel-gfx] [PATCH 04/15] vfio/hisi_acc: " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-31 7:36 ` Shameerali Kolothum Thodi
2022-08-27 17:10 ` [Intel-gfx] [PATCH 05/15] vfio/mdpy: " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-27 17:10 ` [Intel-gfx] [PATCH 06/15] vfio/mtty: " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-27 17:10 ` [Intel-gfx] [PATCH 07/15] vfio/mbochs: " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-27 17:10 ` [Intel-gfx] [PATCH 08/15] drm/i915/gvt: " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-27 17:10 ` [Intel-gfx] [PATCH 09/15] vfio/ap: " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-30 13:43 ` [Intel-gfx] " Anthony Krowiak
2022-08-30 13:43 ` Anthony Krowiak
2022-08-27 17:10 ` [Intel-gfx] [PATCH 10/15] vfio/fsl-mc: " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-31 0:22 ` Jason Gunthorpe
2022-08-31 0:22 ` Jason Gunthorpe
2022-08-31 6:14 ` [Intel-gfx] " Tian, Kevin
2022-08-31 6:14 ` Tian, Kevin
2022-08-31 6:14 ` Tian, Kevin
2022-08-27 17:10 ` [Intel-gfx] [PATCH 11/15] vfio/platform: " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-27 17:10 ` [Intel-gfx] [PATCH 12/15] vfio/amba: " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-27 11:29 ` [Intel-gfx] " kernel test robot
2022-08-27 17:10 ` [Intel-gfx] [PATCH 13/15] vfio/ccw: " Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-27 10:39 ` [Intel-gfx] " Tian, Kevin
2022-08-27 10:39 ` Tian, Kevin
2022-08-27 17:10 ` [Intel-gfx] [PATCH 14/15] vfio: Rename vfio_device_put() and vfio_device_try_get() Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-27 17:10 ` [Intel-gfx] [PATCH 15/15] vfio: Add struct device to vfio_device Kevin Tian
2022-08-27 17:10 ` Kevin Tian
2022-08-30 22:18 ` [Intel-gfx] " Alex Williamson
2022-08-30 22:18 ` Alex Williamson
2022-08-30 22:18 ` Alex Williamson
2022-08-30 23:53 ` Jason Gunthorpe [this message]
2022-08-30 23:53 ` Jason Gunthorpe
2022-08-31 6:10 ` [Intel-gfx] " Tian, Kevin
2022-08-31 6:10 ` Tian, Kevin
2022-08-31 6:10 ` Tian, Kevin
2022-08-31 17:15 ` [Intel-gfx] " Alex Williamson
2022-08-31 17:15 ` Alex Williamson
2022-08-31 17:15 ` Alex Williamson
2022-09-01 0:46 ` [Intel-gfx] " Tian, Kevin
2022-09-01 0:46 ` Tian, Kevin
2022-09-01 0:46 ` Tian, Kevin
2022-09-01 2:05 ` [Intel-gfx] " Alex Williamson
2022-09-01 2:05 ` Alex Williamson
2022-09-01 2:05 ` Alex Williamson
2022-08-31 0:32 ` Jason Gunthorpe
2022-08-31 0:32 ` Jason Gunthorpe
2022-08-31 6:14 ` [Intel-gfx] " Tian, Kevin
2022-08-31 6:14 ` Tian, Kevin
2022-08-31 6:14 ` Tian, Kevin
2022-08-27 22:41 ` [Intel-gfx] [PATCH 00/15] Tidy up vfio_device life cycle Tian, Kevin
2022-08-27 22:41 ` Tian, Kevin
2022-08-30 18:55 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2022-08-31 0:34 ` [Intel-gfx] [PATCH 00/15] " Jason Gunthorpe
2022-08-31 0:34 ` Jason Gunthorpe
2022-08-31 0:34 ` Jason Gunthorpe
2022-08-31 6:14 ` [Intel-gfx] " Tian, Kevin
2022-08-31 6:14 ` Tian, Kevin
2022-08-31 6:14 ` Tian, Kevin
2022-08-31 6:36 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Tidy up vfio_device life cycle (rev2) Patchwork
2022-08-31 6:36 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-08-31 6:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-08-31 16:46 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=Yw6i7btDKcUDPADP@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=abhsahu@nvidia.com \
--cc=agordeev@linux.ibm.com \
--cc=airlied@linux.ie \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=daniel@ffwll.ch \
--cc=diana.craciun@oss.nxp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.auger@redhat.com \
--cc=farman@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jjherne@linux.ibm.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=mjrosato@linux.ibm.com \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=rodrigo.vivi@intel.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=svens@linux.ibm.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=vneethv@linux.ibm.com \
--cc=yi.l.liu@intel.com \
--cc=yishaih@nvidia.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.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.