Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1690847 > unrolled thread
| Started by | "Zhang, Tina" <tina.zhang@intel.com> |
|---|---|
| First post | 2017-07-19 02:20 +0200 |
| Last post | 2017-07-19 14:00 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
RE: [PATCH v10] vfio: ABI for mdev display dma-buf operation "Zhang, Tina" <tina.zhang@intel.com> - 2017-07-19 02:20 +0200
Re: [PATCH v10] vfio: ABI for mdev display dma-buf operation Gerd Hoffmann <kraxel@redhat.com> - 2017-07-19 08:30 +0200
Re: [PATCH v10] vfio: ABI for mdev display dma-buf operation Kirti Wankhede <kwankhede@nvidia.com> - 2017-07-19 14:00 +0200
| From | "Zhang, Tina" <tina.zhang@intel.com> |
|---|---|
| Date | 2017-07-19 02:20 +0200 |
| Subject | RE: [PATCH v10] vfio: ABI for mdev display dma-buf operation |
| Message-ID | <u4KSC-SO-3@gated-at.bofh.it> |
> -----Original Message----- > From: Gerd Hoffmann [mailto:kraxel@redhat.com] > Sent: Monday, July 17, 2017 7:03 PM > To: Kirti Wankhede <kwankhede@nvidia.com>; Zhang, Tina > <tina.zhang@intel.com>; Tian, Kevin <kevin.tian@intel.com>; linux- > kernel@vger.kernel.org; intel-gfx@lists.freedesktop.org; > alex.williamson@redhat.com; zhenyuw@linux.intel.com; chris@chris- > wilson.co.uk; Lv, Zhiyuan <zhiyuan.lv@intel.com>; intel-gvt- > dev@lists.freedesktop.org; Wang, Zhi A <zhi.a.wang@intel.com> > Subject: Re: [PATCH v10] vfio: ABI for mdev display dma-buf operation > > Hi, > > > No need of flag here. If vGPU driver is not loaded in the guest, there > > is no surface being managed by vGPU, in that case this size will be > > zero. > > Ok, we certainly have the same situation with intel. When the guest driver is not > loaded (yet) there is no valid surface. > > We should cleanly define what the ioctl should do in that case, so all drivers > behave the same way. > > I'd suggest that all fields defining the surface (drm_format, width, height, stride, > size) should be set to zero in that case. Yeah, it's reasonable. How about the return value? Currently, the ioctl also returns "-ENODEV" in that situation. thanks, Tina > > cheers, > Gerd
[toc] | [next] | [standalone]
| From | Gerd Hoffmann <kraxel@redhat.com> |
|---|---|
| Date | 2017-07-19 08:30 +0200 |
| Message-ID | <u4QEF-4FE-17@gated-at.bofh.it> |
| In reply to | #1690847 |
On Wed, 2017-07-19 at 00:16 +0000, Zhang, Tina wrote: > > -----Original Message----- > > From: Gerd Hoffmann [mailto:kraxel@redhat.com] > > Sent: Monday, July 17, 2017 7:03 PM > > To: Kirti Wankhede <kwankhede@nvidia.com>; Zhang, Tina > > <tina.zhang@intel.com>; Tian, Kevin <kevin.tian@intel.com>; linux- > > kernel@vger.kernel.org; intel-gfx@lists.freedesktop.org; > > alex.williamson@redhat.com; zhenyuw@linux.intel.com; chris@chris- > > wilson.co.uk; Lv, Zhiyuan <zhiyuan.lv@intel.com>; intel-gvt- > > dev@lists.freedesktop.org; Wang, Zhi A <zhi.a.wang@intel.com> > > Subject: Re: [PATCH v10] vfio: ABI for mdev display dma-buf > > operation > > > > Hi, > > > > > No need of flag here. If vGPU driver is not loaded in the guest, > > > there > > > is no surface being managed by vGPU, in that case this size will > > > be > > > zero. > > > > Ok, we certainly have the same situation with intel. When the > > guest driver is not > > loaded (yet) there is no valid surface. > > > > We should cleanly define what the ioctl should do in that case, so > > all drivers > > behave the same way. > > > > I'd suggest that all fields defining the surface (drm_format, > > width, height, stride, > > size) should be set to zero in that case. > > Yeah, it's reasonable. How about the return value? Currently, the > ioctl also returns "-ENODEV" in that situation. I think it should not return an error. Querying the plane parameters worked fine. cheers, Gerd
[toc] | [prev] | [next] | [standalone]
| From | Kirti Wankhede <kwankhede@nvidia.com> |
|---|---|
| Date | 2017-07-19 14:00 +0200 |
| Message-ID | <u4VO3-85k-43@gated-at.bofh.it> |
| In reply to | #1691013 |
On 7/19/2017 11:55 AM, Gerd Hoffmann wrote: > On Wed, 2017-07-19 at 00:16 +0000, Zhang, Tina wrote: >>> -----Original Message----- >>> From: Gerd Hoffmann [mailto:kraxel@redhat.com] >>> Sent: Monday, July 17, 2017 7:03 PM >>> To: Kirti Wankhede <kwankhede@nvidia.com>; Zhang, Tina >>> <tina.zhang@intel.com>; Tian, Kevin <kevin.tian@intel.com>; linux- >>> kernel@vger.kernel.org; intel-gfx@lists.freedesktop.org; >>> alex.williamson@redhat.com; zhenyuw@linux.intel.com; chris@chris- >>> wilson.co.uk; Lv, Zhiyuan <zhiyuan.lv@intel.com>; intel-gvt- >>> dev@lists.freedesktop.org; Wang, Zhi A <zhi.a.wang@intel.com> >>> Subject: Re: [PATCH v10] vfio: ABI for mdev display dma-buf >>> operation >>> >>> Hi, >>> >>>> No need of flag here. If vGPU driver is not loaded in the guest, >>>> there >>>> is no surface being managed by vGPU, in that case this size will >>>> be >>>> zero. >>> >>> Ok, we certainly have the same situation with intel. When the >>> guest driver is not >>> loaded (yet) there is no valid surface. >>> >>> We should cleanly define what the ioctl should do in that case, so >>> all drivers >>> behave the same way. >>> >>> I'd suggest that all fields defining the surface (drm_format, >>> width, height, stride, >>> size) should be set to zero in that case. >> >> Yeah, it's reasonable. How about the return value? Currently, the >> ioctl also returns "-ENODEV" in that situation. > > I think it should not return an error. Querying the plane parameters > worked fine. > Sounds good to me too. Thanks, Kirti
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web