drm/i915/gvt: Dma-buf support for GVT-g
v6 cover drm/i915/gvt: Dma-buf support for GVT-g
v5->v6:
1) align the dma-buf life cycle with the vfio device.
2) add the dma-buf releated operations in a separate patch.
3) i915 releated changes.
v4->v5:
1) fix bug while checking whether the gem obj is gvt's dma-buf when user change caching mode or domains. Add a helper function to do it.
2) add definition for the query plane and create dma-buf.
v3->v4:
1) fix bug while checking whether the gem obj is gvt's dma-buf when set caching mode or doamins.
v2->v3:
1) add a field gvt_plane_info in the drm_i915_gem_obj structure to save the decoded plane information to avoid look up while need the plane info.
2) declare a new flag I915_GEM_OBJECT_IS_GVT_DMABUF in drm_i915_gem_object to represent the gem obj for gvt's dma-buf. The tiling mode, caching mode and domains can not be changed for this kind of gem object.
3) change dma-buf related information to be more generic. So other vendor can use the same interface.
v1->v2:
1) create a management fd for dma-buf operations.
2) alloc gem object's backing storage in gem obj's get_pages() callback.
This patch set adds the dma-buf support for intel GVT-g. dma-buf is a uniform mechanism to share DMA buffers across different devices and sub-systems.
dma-buf for intel GVT-g is mainly used to share the vgpu's framebuffer to other users or sub-systems so they can use the dma-buf to show the desktop of a vm which uses intel vgpu.
The main idea is we create a gem object and set vgpu's framebuffer as the backing storage of this gem object. And associate this gem obj to a dma-buf object then export this dma-buf at the meantime generate a file descriptor for this dma-buf. Finally deliver this file descriptor to user space. And user can use this dma-buf fd to do render or other operations.
User need to create a fd(for intel GVT-g dma-buf support it is a:dma-buf management fd) then user can use this fd to query the plane information or create a dma-buf. The life cycle of this fd is managed by GVT-g user do not need to care about that.
We have an example program on how to use the dma-buf. You can download the program to have a try. Good luck :)
git repo: https://github.com/01org/igvtg-qemu branch:kvmgt_dmabuf_example
Xiaoguang Chen (6):
drm/i915/gvt: Extend the GVT-g architecture to support vfio device
region
drm/i915/gvt: OpRegion support for GVT-g
drm/i915/gvt: Frame buffer decoder support for GVT-g
vfio: Define vfio based vgpu's dma-buf operations drm/i915/gvt: Dmabuf support for GVT-g
drm/i915/gvt: Adding interface so user space can get the dma-buf
drivers/gpu/drm/i915/gvt/Makefile | 3 +- drivers/gpu/drm/i915/gvt/display.c | 2 +- drivers/gpu/drm/i915/gvt/display.h | 2 + drivers/gpu/drm/i915/gvt/dmabuf.c | 281 +++++++++++++++++++ drivers/gpu/drm/i915/gvt/dmabuf.h | 42 +++ drivers/gpu/drm/i915/gvt/fb_decoder.c | 479 +++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/gvt/fb_decoder.h | 166 ++++++++++++ drivers/gpu/drm/i915/gvt/gvt.c | 2 + drivers/gpu/drm/i915/gvt/gvt.h | 7 + drivers/gpu/drm/i915/gvt/kvmgt.c | 262 +++++++++++++++++- drivers/gpu/drm/i915/gvt/opregion.c | 8 +- drivers/gpu/drm/i915/gvt/vgpu.c | 1 + drivers/gpu/drm/i915/i915_gem.c | 26 +- drivers/gpu/drm/i915/i915_gem_object.h | 9 + include/uapi/linux/vfio.h | 50 ++++ 15 files changed, 1333 insertions(+), 7 deletions(-) create mode 100644 drivers/gpu/drm/i915/gvt/dmabuf.c create mode 100644 drivers/gpu/drm/i915/gvt/dmabuf.h create mode 100644 drivers/gpu/drm/i915/gvt/fb_decoder.c create mode 100644 drivers/gpu/drm/i915/gvt/fb_decoder.h
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v6 1/6 drm/i915/gvt: Extend the GVT-g architecture to support vfio device region
--- drivers/gpu/drm/i915/gvt/kvmgt.c | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/gvt/kvmgt.c +18 -3
@@ -53,11 +53,21 @@ static const struct intel_gvt_ops *intel_gvt_ops;#define VFIO_PCI_INDEX_TO_OFFSET (index) ((u64)(index) << VFIO_PCI_OFFSET_SHIFT)#define VFIO_PCI_OFFSET_MASK (((u64)(1) << VFIO_PCI_OFFSET_SHIFT) - 1) +struct vfio_region ; +struct intel_vgpu_regops { +size_t (*rw)(struct intel_vgpu *vgpu,char *buf, +size_t count,loff_t *ppos,bool iswrite); +void (*release)(struct intel_vgpu *vgpu, +struct vfio_region *region); +}; +struct vfio_region {u32 type;u32 subtype;size_t size;u32 flags; +const struct intel_vgpu_regops *ops; +void *data; };struct kvmgt_pgfn {
@@ -642,7 +652,7 @@ static ssize_t intel_vgpu_rw(struct mdev_device *mdev, char *buf,int ret = -EINVAL ; -if (index >=VFIO_PCI_NUM_REGIONS ) { +if (index >=VFIO_PCI_NUM_REGIONS + vgpu->vdev.num_regions) {gvt_vgpu_err ("invalid index: %u\n" , index);return -EINVAL ; }
@@ -676,8 +686,11 @@ static ssize_t intel_vgpu_rw(struct mdev_device *mdev, char *buf,case VFIO_PCI_BAR5_REGION_INDEX :case VFIO_PCI_VGA_REGION_INDEX :case VFIO_PCI_ROM_REGION_INDEX : +break ;default : -gvt_vgpu_err ("unsupported region: %u\n" , index); + index -=VFIO_PCI_NUM_REGIONS ; +return vgpu->vdev.region[index].ops->rw (vgpu, buf, count, + ppos, is_write); }return ret ==0 ? count : ret;
@@ -940,7 +953,8 @@ static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, info.flags =VFIO_DEVICE_FLAGS_PCI ; info.flags |=VFIO_DEVICE_FLAGS_RESET ; - info.num_regions =VFIO_PCI_NUM_REGIONS ; + info.num_regions =VFIO_PCI_NUM_REGIONS + + vgpu->vdev.num_regions; info.num_irqs =VFIO_PCI_NUM_IRQS ; return copy_to_user((void __user *)arg, &info, minsz) ?
@@ -1061,6 +1075,7 @@ static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, }if (caps.size) { + info.flags |=VFIO_REGION_INFO_FLAG_CAPS ;if (info.argsz <sizeof (info) + caps.size) { info.argsz =sizeof (info) + caps.size; info.cap_offset =0 ;
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v6 2/6 drm/i915/gvt: OpRegion support for GVT-g
In reply to Xiaoguang ChenOpRegion is needed to support display related operation for intel vgpu.
A vfio device region is added to intel vgpu to deliver the host OpRegion information to user space so user space can construct the OpRegion for vgpu.
--- drivers/gpu/drm/i915/gvt/kvmgt.c | 97 +++++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/gvt/opregion.c | 8 ++- 2 files changed, 104 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/gvt/kvmgt.c +97 -0
@@ -53,6 +53,8 @@ static const struct intel_gvt_ops *intel_gvt_ops;#define VFIO_PCI_INDEX_TO_OFFSET (index) ((u64)(index) << VFIO_PCI_OFFSET_SHIFT)#define VFIO_PCI_OFFSET_MASK (((u64)(1) << VFIO_PCI_OFFSET_SHIFT) - 1) +#define OPREGION_SIGNATURE "IntelGraphicsMem" +struct vfio_region ;struct intel_vgpu_regops { size_t (*rw)(struct intel_vgpu *vgpu, char *buf,
@@ -436,6 +438,92 @@ static void kvmgt_protect_table_del(struct kvmgt_guest_info *info, } } +static size_t intel_vgpu_reg_rw_opregion (struct intel_vgpu *vgpu,char *buf, +size_t count,loff_t *ppos,bool iswrite) +{ +unsigned int i =VFIO_PCI_OFFSET_TO_INDEX (*ppos) - +VFIO_PCI_NUM_REGIONS ; +void *base = vgpu->vdev.region[i].data; +loff_t pos = *ppos &VFIO_PCI_OFFSET_MASK ; + +if (pos >= vgpu->vdev.region[i].size || iswrite) { +gvt_vgpu_err ("invalid op or offset for Intel vgpu OpRegion\n" ); +return -EINVAL ; + } + count =min (count, (size_t )(vgpu->vdev.region[i].size - pos)); +memcpy (buf, base + pos, count); + +return count; +} + +static void intel_vgpu_reg_release_opregion (struct intel_vgpu *vgpu, +struct vfio_region *region) +{ +memunmap (region->data); +} + +static const struct intel_vgpu_regops intel_vgpu_regops_opregion = { + .rw = intel_vgpu_reg_rw_opregion, + .release = intel_vgpu_reg_release_opregion, +}; + +static int intel_vgpu_register_reg (struct intel_vgpu *vgpu, +unsigned int type,unsigned int subtype, +const struct intel_vgpu_regops *ops, +size_t size,u32 flags,void *data) +{ +struct vfio_region *region; + + region =krealloc (vgpu->vdev.region, + (vgpu->vdev.num_regions +1 ) *sizeof (*region), +GFP_KERNEL ); +if (!region) +return -ENOMEM ; + + vgpu->vdev.region = region; + vgpu->vdev.region[vgpu->vdev.num_regions].type = type; + vgpu->vdev.region[vgpu->vdev.num_regions].subtype = subtype; + vgpu->vdev.region[vgpu->vdev.num_regions].ops = ops; + vgpu->vdev.region[vgpu->vdev.num_regions].size = size; + vgpu->vdev.region[vgpu->vdev.num_regions].flags = flags; + vgpu->vdev.region[vgpu->vdev.num_regions].data = data; + vgpu->vdev.num_regions++; + +return 0 ; +} + +static int intel_vgpu_reg_init_opregion (struct intel_vgpu *vgpu) +{ +unsigned int addr; +void *base; +int ret; + + addr = vgpu->gvt->opregion.opregion_pa; +if (!addr || !(~addr)) +return -ENODEV ; + + base =memremap (addr,OPREGION_SIZE ,MEMREMAP_WB ); +if (!base) +return -ENOMEM ; + +if (memcmp (base,OPREGION_SIGNATURE ,16 )) { +memunmap (base); +return -EINVAL ; + } + + ret =intel_vgpu_register_reg (vgpu, +PCI_VENDOR_ID_INTEL |VFIO_REGION_TYPE_PCI_VENDOR_TYPE , +VFIO_REGION_SUBTYPE_INTEL_IGD_OPREGION , + &intel_vgpu_regops_opregion,OPREGION_SIZE , +VFIO_REGION_INFO_FLAG_READ , base); +if (ret) { +memunmap (base); +return ret; + } + +return ret; +} +static int intel_vgpu_create (struct kobject *kobj,struct mdev_device *mdev) {struct intel_vgpu *vgpu =NULL ;
@@ -467,6 +555,15 @@ static int intel_vgpu_create(struct kobject *kobj, struct mdev_device *mdev) vgpu->vdev.mdev = mdev;mdev_set_drvdata (mdev, vgpu); + ret =intel_vgpu_reg_init_opregion (vgpu); +if (ret) { +gvt_vgpu_err ("create OpRegion failed\n" ); + goto out; + } + +gvt_dbg_core ("create OpRegion succeeded for mdev:%s\n" , +dev_name (mdev_dev (mdev))); +gvt_dbg_core ("intel_vgpu_create succeeded for mdev: %s\n" ,dev_name (mdev_dev (mdev))); ret =0 ;
drivers/gpu/drm/i915/gvt/opregion.c +7 -1
@@ -114,6 +114,7 @@ void intel_vgpu_clean_opregion(struct intel_vgpu *vgpu)int intel_vgpu_init_opregion (struct intel_vgpu *vgpu,u32 gpa) {int ret; +unsigned long pfn;gvt_dbg_core ("vgpu%d: init vgpu opregion\n" , vgpu->id);
@@ -127,7 +128,12 @@ int intel_vgpu_init_opregion(struct intel_vgpu *vgpu, u32 gpa) ret =map_vgpu_opregion (vgpu, true);if (ret)return ret; - } + }else { + pfn =intel_gvt_hypervisor_gfn_to_mfn (vgpu, gpa >>PAGE_SHIFT ); +vgpu_opregion (vgpu)->va =memremap (pfn <<PAGE_SHIFT , +INTEL_GVT_OPREGION_SIZE , +MEMREMAP_WB ); + }return 0 ; }
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 2/6] drm/i915/gvt: OpRegion support for GVT-g
Quoted 121 lines · Xiaoguang Chen
OpRegion is needed to support display related operation for intel vgpu.
A vfio device region is added to intel vgpu to deliver the host OpRegion information to user space so user space can construct the OpRegion for vgpu.
Signed-off-by Bing Niu <[email protected]>Signed-off-by Xiaoguang Chen <[email protected]>--- drivers/gpu/drm/i915/gvt/kvmgt.c | 97 +++++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/gvt/opregion.c | 8 ++- 2 files changed, 104 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/gvt/kvmgt.c +88
-0@@ -53,6 +53,8 @@ static const struct intel_gvt_ops *intel_gvt_ops;#define VFIO_PCI_INDEX_TO_OFFSET (index) ((u64)(index) << VFIO_PCI_OFFSET_SHIFT)#define VFIO_PCI_OFFSET_MASK (((u64)(1) << VFIO_PCI_OFFSET_SHIFT) - 1) +#define OPREGION_SIGNATURE "IntelGraphicsMem" +struct vfio_region ;struct intel_vgpu_regops { size_t (*rw)(struct intel_vgpu *vgpu, char *buf,@@ -436,6 +438,92 @@ static void kvmgt_protect_table_del(struct kvmgt_guest_info *info, } } +static size_t intel_vgpu_reg_rw_opregion (struct intel_vgpu *vgpu,char *buf, +size_t count,loff_t *ppos,bool iswrite) +{ +unsigned int i =VFIO_PCI_OFFSET_TO_INDEX (*ppos) - +VFIO_PCI_NUM_REGIONS ; +void *base = vgpu->vdev.region[i].data; +loff_t pos = *ppos &VFIO_PCI_OFFSET_MASK ; + +if (pos >= vgpu->vdev.region[i].size || iswrite) { +gvt_vgpu_err ("invalid op or offset for Intel vgpu OpRegion\n" ); +return -EINVAL ; + } + count =min (count, (size_t )(vgpu->vdev.region[i].size - pos)); +memcpy (buf, base + pos, count); + +return count; +} + +static void intel_vgpu_reg_release_opregion (struct intel_vgpu *vgpu, +struct vfio_region *region) +{ +memunmap (region->data); +} + +static const struct intel_vgpu_regops intel_vgpu_regops_opregion = { + .rw = intel_vgpu_reg_rw_opregion, + .release = intel_vgpu_reg_release_opregion, +}; + +static int intel_vgpu_register_reg (struct intel_vgpu *vgpu, +unsigned int type,unsigned int subtype, +const struct intel_vgpu_regops *ops, +size_t size,u32 flags,void *data) +{ +struct vfio_region *region; + + region =krealloc (vgpu->vdev.region, + (vgpu->vdev.num_regions +1 ) *sizeof (*region), +GFP_KERNEL ); +if (!region) +return -ENOMEM ; + + vgpu->vdev.region = region; + vgpu->vdev.region[vgpu->vdev.num_regions].type = type; + vgpu->vdev.region[vgpu->vdev.num_regions].subtype = subtype; + vgpu->vdev.region[vgpu->vdev.num_regions].ops = ops; + vgpu->vdev.region[vgpu->vdev.num_regions].size = size; + vgpu->vdev.region[vgpu->vdev.num_regions].flags = flags; + vgpu->vdev.region[vgpu->vdev.num_regions].data = data; + vgpu->vdev.num_regions++; + +return 0 ; +} + +static int intel_vgpu_reg_init_opregion (struct intel_vgpu *vgpu) +{ +unsigned int addr; +void *base; +int ret; + + addr = vgpu->gvt->opregion.opregion_pa; +if (!addr || !(~addr)) +return -ENODEV ; + + base =memremap (addr,OPREGION_SIZE ,MEMREMAP_WB ); +if (!base) +return -ENOMEM ; + +if (memcmp (base,OPREGION_SIGNATURE ,16 )) { +memunmap (base); +return -EINVAL ; + } + + ret =intel_vgpu_register_reg (vgpu, +PCI_VENDOR_ID_INTEL |VFIO_REGION_TYPE_PCI_VENDOR_TYPE , +VFIO_REGION_SUBTYPE_INTEL_IGD_OPREGION , + &intel_vgpu_regops_opregion,OPREGION_SIZE , +VFIO_REGION_INFO_FLAG_READ , base); +if (ret) { +memunmap (base); +return ret; + } + +return ret; +} +static int intel_vgpu_create (struct kobject *kobj,struct mdev_device *mdev) {struct intel_vgpu *vgpu =NULL ;
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_create(struct kobject *kobj, struct mdev_device *mdev) · line 562
Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +5
-0@@ -467,6 +555,15 @@ static int intel_vgpu_create(struct kobject *kobj, struct mdev_device *mdev) vgpu->vdev.mdev = mdev;mdev_set_drvdata (mdev, vgpu); + ret =intel_vgpu_reg_init_opregion (vgpu); +if (ret) { +gvt_vgpu_err ("create OpRegion failed\n" ); + goto out; + }
Still need to handle error path for created vgpu.
Quoted 20 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +4
-0+ +gvt_dbg_core ("create OpRegion succeeded for mdev:%s\n" , +dev_name (mdev_dev (mdev))); +gvt_dbg_core ("intel_vgpu_create succeeded for mdev: %s\n" ,dev_name (mdev_dev (mdev))); ret =0 ;drivers/gpu/drm/i915/gvt/opregion.c +1
-0@@ -114,6 +114,7 @@ void intel_vgpu_clean_opregion(struct intel_vgpu *vgpu)int intel_vgpu_init_opregion (struct intel_vgpu *vgpu,u32 gpa) {int ret; +unsigned long pfn;gvt_dbg_core ("vgpu%d: init vgpu opregion\n" , vgpu->id);
drivers/gpu/drm/i915/gvt/opregion.c int intel_vgpu_init_opregion(struct intel_vgpu *vgpu, u32 gpa) · line 136
Quoted 10 lines
drivers/gpu/drm/i915/gvt/opregion.c +6
-1@@ -127,7 +128,12 @@ int intel_vgpu_init_opregion(struct intel_vgpu *vgpu, u32 gpa) ret =map_vgpu_opregion (vgpu, true);if (ret)return ret; - } + }else { + pfn =intel_gvt_hypervisor_gfn_to_mfn (vgpu, gpa >>PAGE_SHIFT ); +vgpu_opregion (vgpu)->va =memremap (pfn <<PAGE_SHIFT , +INTEL_GVT_OPREGION_SIZE , +MEMREMAP_WB ); + }
better to use switch for explicit KVM case, and no return check?
Quoted 6 lines
drivers/gpu/drm/i915/gvt/opregion.c +0
-0return 0 ; }Signature · 1 line
2.7.4
Signature · 3 lines
Open Source Technology Center, Intel ltd. $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
RE: [PATCH v6 2/6] drm/i915/gvt: OpRegion support for GVT-g
Hi
Quoted 138 lines
-----Original Message-----
From: intel-gvt-dev [mailto:[email protected]] On Behalf Of Zhenyu Wang
Sent: Wednesday, May 31, 2017 12:47 PM
To: Chen, Xiaoguang <[email protected]>
Cc: Tian, Kevin <[email protected]>; [email protected]; linux- [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Niu, Bing <[email protected]>; [email protected]; Wang, Zhi A <[email protected]>; Lv, Zhiyuan <[email protected]>
Subject: Re: [PATCH v6 2/6] drm/i915/gvt: OpRegion support for GVT-gQuoted 11 lines · Xiaoguang Chen
OpRegion is needed to support display related operation for intel vgpu.
A vfio device region is added to intel vgpu to deliver the host OpRegion information to user space so user space can construct the OpRegion for vgpu.
Signed-off-by Bing Niu <[email protected]>Signed-off-by Xiaoguang Chen <[email protected]>--- drivers/gpu/drm/i915/gvt/kvmgt.c | 97+++++++++++++++++++++++++++++++++++++
drivers/gpu/drm/i915/gvt/kvmgt.c static const struct intel_gvt_ops *intel_gvt_ops; · line 53
Quoted 10 lines
drivers/gpu/drm/i915/gvt/opregion.c | 8 ++- 2 files changed, 104 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/gvt/kvmgt.c +0
-0@@ -53,6 +53,8 @@ static const struct intel_gvt_ops *intel_gvt_ops;#define VFIO_PCI_INDEX_TO_OFFSET (index) ((u64)(index) <<
VFIO_PCI_OFFSET_SHIFT)Quoted 72 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +2
-0#define VFIO_PCI_OFFSET_MASK (((u64)(1) << VFIO_PCI_OFFSET_SHIFT) - 1) +#define OPREGION_SIGNATURE "IntelGraphicsMem" +struct vfio_region ;struct intel_vgpu_regops { size_t (*rw)(struct intel_vgpu *vgpu, char *buf, @@ -436,6 +438,92@@ static void kvmgt_protect_table_del(struct
kvmgt_guest_info*info,drivers/gpu/drm/i915/gvt/kvmgt.c +61
-0} } +static size_t intel_vgpu_reg_rw_opregion (struct intel_vgpu *vgpu,char *buf, +size_t count,loff_t *ppos,bool iswrite) { +unsigned int i =VFIO_PCI_OFFSET_TO_INDEX (*ppos) - +VFIO_PCI_NUM_REGIONS ; +void *base = vgpu->vdev.region[i].data; +loff_t pos = *ppos &VFIO_PCI_OFFSET_MASK ; + +if (pos >= vgpu->vdev.region[i].size || iswrite) { +gvt_vgpu_err ("invalid op or offset for Intel vgpu OpRegion\n" ); +return -EINVAL ; + } + count =min (count, (size_t )(vgpu->vdev.region[i].size - pos)); +memcpy (buf, base + pos, count); + +return count; +} + +static void intel_vgpu_reg_release_opregion (struct intel_vgpu *vgpu, +struct vfio_region *region) +{ +memunmap (region->data); +} + +static const struct intel_vgpu_regops intel_vgpu_regops_opregion = { + .rw = intel_vgpu_reg_rw_opregion, + .release = intel_vgpu_reg_release_opregion, }; + +static int intel_vgpu_register_reg (struct intel_vgpu *vgpu, +unsigned int type,unsigned int subtype, +const struct intel_vgpu_regops *ops, +size_t size,u32 flags,void *data) { +struct vfio_region *region; + + region =krealloc (vgpu->vdev.region, + (vgpu->vdev.num_regions +1 ) *sizeof (*region), +GFP_KERNEL ); +if (!region) +return -ENOMEM ; + + vgpu->vdev.region = region; + vgpu->vdev.region[vgpu->vdev.num_regions].type = type; + vgpu->vdev.region[vgpu->vdev.num_regions].subtype = subtype; + vgpu->vdev.region[vgpu->vdev.num_regions].ops = ops; + vgpu->vdev.region[vgpu->vdev.num_regions].size = size; + vgpu->vdev.region[vgpu->vdev.num_regions].flags = flags; + vgpu->vdev.region[vgpu->vdev.num_regions].data = data; + vgpu->vdev.num_regions++; + +return 0 ; +} + +static int intel_vgpu_reg_init_opregion (struct intel_vgpu *vgpu) { +unsigned int addr; +void *base; +int ret; + + addr = vgpu->gvt->opregion.opregion_pa; +if (!addr || !(~addr)) +return -ENODEV ; + + base =memremap (addr,OPREGION_SIZE ,MEMREMAP_WB );drivers/gpu/drm/i915/gvt/kvmgt.c static void kvmgt_protect_table_del(struct kvmgt_guest_info *info,
Quoted 10 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +10
-0+if (!base) +return -ENOMEM ; + +if (memcmp (base,OPREGION_SIGNATURE ,16 )) { +memunmap (base); +return -EINVAL ; + } + + ret = intel_vgpu_register_reg(vgpu, + PCI_VENDOR_ID_INTEL |
VFIO_REGION_TYPE_PCI_VENDOR_TYPE,drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_create(struct kobject *kobj,
Quoted 15 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +11
-0+VFIO_REGION_SUBTYPE_INTEL_IGD_OPREGION , + &intel_vgpu_regops_opregion,OPREGION_SIZE , + VFIO_REGION_INFO_FLAG_READ, base); +if (ret) { +memunmap (base); +return ret; + } + +return ret; +} + static int intel_vgpu_create(struct kobject *kobj, struct mdev_device*mdev) {
drivers/gpu/drm/i915/gvt/kvmgt.c +0
-0struct intel_vgpu *vgpu =NULL ;@@ -467,6 +555,15 @@ static int intel_vgpu_create(struct kobject *kobj,struct
mdev_device*mdev)Quoted 3 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +0
-0vgpu->vdev.mdev = mdev;mdev_set_drvdata (mdev, vgpu);
Quoted 7 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_create(struct kobject *kobj, struct mdev_device *mdev) · line 562
Quoted 5 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +5
-0+ ret =intel_vgpu_reg_init_opregion (vgpu); +if (ret) { +gvt_vgpu_err ("create OpRegion failed\n" ); + goto out; + }Still need to handle error path for created vgpu.
Just checked the code, if initialize the opregion failed we should first release vfio/mdev releated work(maybe call intel_vgpu_release function) and then destroy the vgpu. Will update in the next version.
Quoted 30 lines
drivers/gpu/drm/i915/gvt/opregion.c int intel_vgpu_init_opregion(struct intel_vgpu *vgpu,
Quoted 22 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +4
-0+ +gvt_dbg_core ("create OpRegion succeeded for mdev:%s\n" , +dev_name (mdev_dev (mdev))); +gvt_dbg_core ("intel_vgpu_create succeeded for mdev: %s\n" ,dev_name (mdev_dev (mdev))); ret =0 ;drivers/gpu/drm/i915/gvt/opregion.c +1
-0@@ -114,6 +114,7 @@ void intel_vgpu_clean_opregion(struct intel_vgpu *vgpu) int intel_vgpu_init_opregion(struct intel_vgpu *vgpu, u32 gpa) {int ret; +unsigned long pfn;gvt_dbg_core ("vgpu%d: init vgpu opregion\n" , vgpu->id);@@ -127,7 +128,12 @@ int intel_vgpu_init_opregion(struct intel_vgpu *vgpu,u32 gpa)
drivers/gpu/drm/i915/gvt/opregion.c int intel_vgpu_init_opregion(struct intel_vgpu *vgpu, u32 gpa)
Quoted 6 lines
drivers/gpu/drm/i915/gvt/opregion.c +2
-1ret =map_vgpu_opregion (vgpu, true);if (ret)return ret; - } + }else { + pfn = intel_gvt_hypervisor_gfn_to_mfn(vgpu, gpa >>
PAGE_SHIFT);
Quoted 6 lines
drivers/gpu/drm/i915/gvt/opregion.c int intel_vgpu_init_opregion(struct intel_vgpu *vgpu, u32 gpa) · line 136
Quoted 4 lines
drivers/gpu/drm/i915/gvt/opregion.c +4
-0+vgpu_opregion (vgpu)->va =memremap (pfn <<PAGE_SHIFT , +INTEL_GVT_OPREGION_SIZE , +MEMREMAP_WB ); + }better to use switch for explicit KVM case, and no return check?
Will update and add NULL check.
Thanks for review.
Quoted 8 lines
Quoted 7 lines
drivers/gpu/drm/i915/gvt/opregion.c +0
-1return 0 ; } --2.7.4
Quoted 4 lines
--
Open Source Technology Center, Intel ltd.$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 2/6] drm/i915/gvt: OpRegion support for GVT-g
Quoted 5 lines · Xiaoguang
Quoted 5 lines
Review static int intel_vgpu_create(struct kobject *kobj,
Quoted 1 line
(quoted diff) +0
-0@@ -467,6 +555,15 @@ static int intel_vgpu_create(struct kobject *kobj,struct
mdev_device*mdev)Quoted 3 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +0
-0vgpu->vdev.mdev = mdev;mdev_set_drvdata (mdev, vgpu);
Quoted 9 lines
Quoted 7 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_create(struct kobject *kobj, struct mdev_device *mdev) · line 562
Quoted 5 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +5
-0+ ret =intel_vgpu_reg_init_opregion (vgpu); +if (ret) { +gvt_vgpu_err ("create OpRegion failed\n" ); + goto out; + }Still need to handle error path for created vgpu.
Just checked the code, if initialize the opregion failed we should first release vfio/mdev releated
work(maybe call intel_vgpu_release function)and then destroy the vgpu. Will update in the next version.
Better to init opregion inside of create vgpu and do proper error handling there too.
Signature · 3 lines
Open Source Technology Center, Intel ltd. $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
RE: [PATCH v6 2/6] drm/i915/gvt: OpRegion support for GVT-g
Quoted 27 lines
-----Original Message-----
From: Zhenyu Wang [mailto:[email protected]]
Sent: Wednesday, May 31, 2017 2:30 PM
To: Chen, Xiaoguang <[email protected]>
Cc: Tian, Kevin <[email protected]>; [email protected]; linux- [email protected]; [email protected]; [email protected]; [email protected]; Niu, Bing <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Lv, Zhiyuan <[email protected]>
Subject: Re: [PATCH v6 2/6] drm/i915/gvt: OpRegion support for GVT-gQuoted 13 lines · Xiaoguang
Quoted 13 lines
Review static int intel_vgpu_create(struct kobject · line 555
Quoted 2 lines
(quoted diff) +0
-0@@ -467,6 +555,15 @@ static int intel_vgpu_create(struct kobject *kobj,struct
mdev_device*mdev)drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_create(struct kobject *kobj, struct mdev_device *mdev) · line 562
Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +5
-0vgpu->vdev.mdev = mdev;mdev_set_drvdata (mdev, vgpu); + ret =intel_vgpu_reg_init_opregion (vgpu); +if (ret) { +gvt_vgpu_err ("create OpRegion failed\n" ); + goto out; + }Still need to handle error path for created vgpu.
Quoted 7 lines
Quoted 1 line
Just checked the code, if initialize the opregion failed we should first release
vfio/mdev releated
work(maybe call intel_vgpu_release function)and then destroy the vgpu. Will update in the next version.Quoted 1 line
Better to init opregion inside of create vgpu and do proper error handling there too.
Then we must add a new entry in intel_gvt_mpt interface something like "create_opregion".
Quoted 5 lines
--
Open Source Technology Center, Intel ltd.$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v6 3/6 drm/i915/gvt: Frame buffer decoder support for GVT-g
In reply to Xiaoguang Chendecode frambuffer attributes of primary, cursor and sprite plane
--- drivers/gpu/drm/i915/gvt/Makefile | 3 +- drivers/gpu/drm/i915/gvt/display.c | 2 +- drivers/gpu/drm/i915/gvt/display.h | 2 + drivers/gpu/drm/i915/gvt/fb_decoder.c | 479 ++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/gvt/fb_decoder.h | 166 ++++++++++++ drivers/gpu/drm/i915/gvt/gvt.h | 1 + 6 files changed, 651 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/drm/i915/gvt/fb_decoder.c create mode 100644 drivers/gpu/drm/i915/gvt/fb_decoder.h
drivers/gpu/drm/i915/gvt/Makefile +2 -1
@@ -1,7 +1,8 @@ GVT_DIR := gvt GVT_SOURCE := gvt.o aperture_gm.o handlers.o vgpu.o trace_points.o firmware.o \ interrupt.o gtt.o cfg_space.o opregion.o mmio.o display.o edid.o \ - execlist.o scheduler.o sched_policy.o render.o cmd_parser.o + execlist.o scheduler.o sched_policy.o render.o cmd_parser.o \ + fb_decoder.o ccflags-y += -I$(src) -I$(src)/$(GVT_DIR) -Wall i915-y += $(addprefix $(GVT_DIR)/, $(GVT_SOURCE))
drivers/gpu/drm/i915/gvt/display.c +1 -1
@@ -67,7 +67,7 @@ static int edp_pipe_is_enabled(struct intel_vgpu *vgpu)return 1 ; } -static int pipe_is_enabled (struct intel_vgpu *vgpu,int pipe) +int pipe_is_enabled (struct intel_vgpu *vgpu,int pipe) {struct drm_i915_private *dev_priv = vgpu->gvt->dev_priv;
drivers/gpu/drm/i915/gvt/display.h +2 -0
@@ -179,4 +179,6 @@ int intel_vgpu_init_display(struct intel_vgpu *vgpu, u64 resolution);void intel_vgpu_reset_display (struct intel_vgpu *vgpu);void intel_vgpu_clean_display (struct intel_vgpu *vgpu); +int pipe_is_enabled (struct intel_vgpu *vgpu,int pipe); +#endif
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +479 -0
479 lines not on this page · raw message
drivers/gpu/drm/i915/gvt/fb_decoder.h new file +166 -0
166 lines not on this page · raw message
drivers/gpu/drm/i915/gvt/gvt.h +1 -0
@@ -46,6 +46,7 @@#include "sched_policy.h" #include "render.h" #include "cmd_parser.h" +#include "fb_decoder.h" #define GVT_MAX_VGPU 8
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 3/6] drm/i915/gvt: Frame buffer decoder support for GVT-g
Quoted 92 lines · Xiaoguang Chen
decode frambuffer attributes of primary, cursor and sprite plane
Signed-off-by Xiaoguang Chen <[email protected]>--- drivers/gpu/drm/i915/gvt/Makefile | 3 +- drivers/gpu/drm/i915/gvt/display.c | 2 +- drivers/gpu/drm/i915/gvt/display.h | 2 + drivers/gpu/drm/i915/gvt/fb_decoder.c | 479 ++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/gvt/fb_decoder.h | 166 ++++++++++++ drivers/gpu/drm/i915/gvt/gvt.h | 1 + 6 files changed, 651 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/drm/i915/gvt/fb_decoder.c create mode 100644 drivers/gpu/drm/i915/gvt/fb_decoder.hdrivers/gpu/drm/i915/gvt/Makefile +2
-1@@ -1,7 +1,8 @@ GVT_DIR := gvt GVT_SOURCE := gvt.o aperture_gm.o handlers.o vgpu.o trace_points.o firmware.o \ interrupt.o gtt.o cfg_space.o opregion.o mmio.o display.o edid.o \ - execlist.o scheduler.o sched_policy.o render.o cmd_parser.o + execlist.o scheduler.o sched_policy.o render.o cmd_parser.o \ + fb_decoder.o ccflags-y += -I$(src) -I$(src)/$(GVT_DIR) -Wall i915-y += $(addprefix $(GVT_DIR)/, $(GVT_SOURCE))drivers/gpu/drm/i915/gvt/display.c +1
-1@@ -67,7 +67,7 @@ static int edp_pipe_is_enabled(struct intel_vgpu *vgpu)return 1 ; } -static int pipe_is_enabled (struct intel_vgpu *vgpu,int pipe) +int pipe_is_enabled (struct intel_vgpu *vgpu,int pipe) {struct drm_i915_private *dev_priv = vgpu->gvt->dev_priv;drivers/gpu/drm/i915/gvt/display.h +2
-0@@ -179,4 +179,6 @@ int intel_vgpu_init_display(struct intel_vgpu *vgpu, u64 resolution);void intel_vgpu_reset_display (struct intel_vgpu *vgpu);void intel_vgpu_clean_display (struct intel_vgpu *vgpu); +int pipe_is_enabled (struct intel_vgpu *vgpu,int pipe); +#endif drivers/gpu/drm/i915/gvt/fb_decoder.c new file +34
-0@@ -0,0 +1,479 @@ +/* +* Copyright(c) 2011-2016 Intel Corporation. All rights reserved. +* +* Permission is hereby granted, free of charge, to any person obtaining a +* copy of this software and associated documentation files (the "Software"), +* to deal in the Software without restriction, including without limitation +* the rights to use, copy, modify, merge, publish, distribute, sublicense, +* and/or sell copies of the Software, and to permit persons to whom the +* Software is furnished to do so, subject to the following conditions: +* +* The above copyright notice and this permission notice (including the next +* paragraph) shall be included in all copies or substantial portions of the +* Software. +* +* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL +* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +* SOFTWARE. +* +* Authors: +* Kevin Tian <[email protected]> +* +* Contributors: +* Bing Niu <[email protected]> +* Xu Han <[email protected]> +* Ping Gao <[email protected]> +* Xiaoguang Chen <[email protected]> +* Yang Liu <[email protected]> +* +*/ +
drivers/gpu/drm/i915/gvt/fb_decoder.c line 44
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+#include <uapi/drm/drm_fourcc.h> +#include "i915_drv.h" +#include "gvt.h" + +/* The below definitions are required by guest. */ +// [63:0] x:R:G:B 16:16:16:16 little endian +#define DRM_FORMAT_XRGB161616_GVT fourcc_code('X', 'R', '4', '8') +// [63:0] x:B:G:R 16:16:16:16 little endian +#define DRM_FORMAT_XBGR161616_GVT fourcc_code('X', 'B', '4', '8') +
Should be added to drm_fourcc?
drivers/gpu/drm/i915/gvt/fb_decoder.c line 45
Quoted 1 line
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +1
-0+#define FORMAT_NUM 16
PRIMARY_FORMAT_NUM
Quoted 11 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +11
-0+struct pixel_format { +int drm_format;/* Pixel format in DRM definition */ +int bpp;/* Bits per pixel, 0 indicates invalid */ +char *desc;/* The description */ +}; + +/* non-supported format has bpp default to 0 */ +static struct pixel_format primary_pixel_formats[FORMAT_NUM ] = { + [0x2 ] = {DRM_FORMAT_C8 ,8 ,"8-bit Indexed" }, + [0x5 ] = {DRM_FORMAT_RGB565 ,16 ,"16-bit BGRX (5:6:5 MSB-R:G:B)" }, + [0x6 ] = {DRM_FORMAT_XRGB8888 ,32 ,
drivers/gpu/drm/i915/gvt/fb_decoder.c line 66
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+ "32-bit BGRX (8:8:8:8 MSB-X:R:G:B)"}, + [0x8] = {DRM_FORMAT_XBGR2101010, 32, + "32-bit RGBX (2:10:10:10 MSB-X:B:G:R)"}, + [0xa] = {DRM_FORMAT_XRGB2101010, 32, + "32-bit BGRX (2:10:10:10 MSB-X:R:G:B)"}, + [0xc] = {DRM_FORMAT_XRGB161616_GVT, 64, + "64-bit RGBX Floating Point(16:16:16:16 MSB-X:B:G:R)"}, + [0xe] = {DRM_FORMAT_XBGR8888, 32, + "32-bit RGBX (8:8:8:8 MSB-X:B:G:R)"}, +};
might explicitly say this is bdw_pixel_formats?
Quoted 123 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +123
-0+ +/* non-supported format has bpp default to 0 */ +static struct pixel_format skl_pixel_formats[] = { + {DRM_FORMAT_YUYV ,16 ,"16-bit packed YUYV (8:8:8:8 MSB-V:Y2:U:Y1)" }, + {DRM_FORMAT_UYVY ,16 ,"16-bit packed UYVY (8:8:8:8 MSB-Y2:V:Y1:U)" }, + {DRM_FORMAT_YVYU ,16 ,"16-bit packed YVYU (8:8:8:8 MSB-U:Y2:V:Y1)" }, + {DRM_FORMAT_VYUY ,16 ,"16-bit packed VYUY (8:8:8:8 MSB-Y2:U:Y1:V)" }, + + {DRM_FORMAT_C8 ,8 ,"8-bit Indexed" }, + {DRM_FORMAT_RGB565 ,16 ,"16-bit BGRX (5:6:5 MSB-R:G:B)" }, + {DRM_FORMAT_ABGR8888 ,32 ,"32-bit RGBA (8:8:8:8 MSB-A:B:G:R)" }, + {DRM_FORMAT_XBGR8888 ,32 ,"32-bit RGBX (8:8:8:8 MSB-X:B:G:R)" }, + + {DRM_FORMAT_ARGB8888 ,32 ,"32-bit BGRA (8:8:8:8 MSB-A:R:G:B)" }, + {DRM_FORMAT_XRGB8888 ,32 ,"32-bit BGRX (8:8:8:8 MSB-X:R:G:B)" }, + {DRM_FORMAT_XBGR2101010 ,32 ,"32-bit RGBX (2:10:10:10 MSB-X:B:G:R)" }, + {DRM_FORMAT_XRGB2101010 ,32 ,"32-bit BGRX (2:10:10:10 MSB-X:R:G:B)" }, + + {DRM_FORMAT_XRGB161616_GVT ,64 , +"64-bit XRGB (16:16:16:16 MSB-X:R:G:B)" }, + {DRM_FORMAT_XBGR161616_GVT ,64 , +"64-bit XBGR (16:16:16:16 MSB-X:B:G:R)" }, + +/* non-supported format has bpp default to 0 */ + {0 ,0 ,NULL }, +}; + +static int skl_format_to_drm (int format,bool rgb_order,bool alpha, +int yuv_order) +{ +int skl_pixel_formats_index =14 ; + +switch (format) { +case PLANE_CTL_FORMAT_INDEXED : + skl_pixel_formats_index =4 ; +break ; +case PLANE_CTL_FORMAT_RGB_565 : + skl_pixel_formats_index =5 ; +break ; +case PLANE_CTL_FORMAT_XRGB_8888 : +if (rgb_order) + skl_pixel_formats_index = alpha ?6 :7 ; +else + skl_pixel_formats_index = alpha ?8 :9 ; +break ; +case PLANE_CTL_FORMAT_XRGB_2101010 : + skl_pixel_formats_index = rgb_order ?10 :11 ; +break ; + +case PLANE_CTL_FORMAT_XRGB_16161616F : + skl_pixel_formats_index = rgb_order ?12 :13 ; +break ; + +case PLANE_CTL_FORMAT_YUV422 : + skl_pixel_formats_index = yuv_order >>16 ; +if (skl_pixel_formats_index >3 ) +return -EINVAL ; +break ; + +default : +break ; + } + +return skl_pixel_formats_index; +} + +static u32 intel_vgpu_get_stride (struct intel_vgpu *vgpu,int pipe, +u32 tiled,int stride_mask,int bpp) +{ +struct drm_i915_private *dev_priv = vgpu->gvt->dev_priv; + +u32 stride_reg =vgpu_vreg (vgpu,DSPSTRIDE (pipe)) & stride_mask; +u32 stride = stride_reg; + +if (IS_SKYLAKE (dev_priv)) { +switch (tiled) { +case PLANE_CTL_TILED_LINEAR : + stride = stride_reg *64 ; +break ; +case PLANE_CTL_TILED_X : + stride = stride_reg *512 ; +break ; +case PLANE_CTL_TILED_Y : + stride = stride_reg *128 ; +break ; +case PLANE_CTL_TILED_YF : +if (bpp ==8 ) + stride = stride_reg *64 ; +else if (bpp ==16 || bpp ==32 || bpp ==64 ) + stride = stride_reg *128 ; +else +gvt_dbg_core ("skl: unsupported bpp:%d\n" , bpp); +break ; +default : +gvt_dbg_core ("skl: unsupported tile format:%x\n" , + tiled); + } + } + +return stride; +} + +static int intel_vgpu_decode_primary_plane_format (struct intel_vgpu *vgpu, +int pipe,struct intel_vgpu_primary_plane_format *plane) +{ +u32 val, fmt; +struct drm_i915_private *dev_priv = vgpu->gvt->dev_priv; + + val =vgpu_vreg (vgpu,DSPCNTR (pipe)); + plane->enabled = !!(val &DISPLAY_PLANE_ENABLE ); +if (!plane->enabled) +return 0 ; + +if (IS_SKYLAKE (dev_priv)) { + plane->tiled = (val &PLANE_CTL_TILED_MASK ) >> + _PLANE_CTL_TILED_SHIFT; + fmt =skl_format_to_drm ( + val &PLANE_CTL_FORMAT_MASK , + val &PLANE_CTL_ORDER_RGBX , + val &PLANE_CTL_ALPHA_MASK , + val &PLANE_CTL_YUV422_ORDER_MASK ); + plane->bpp = skl_pixel_formats[fmt].bpp; + plane->drm_format = skl_pixel_formats[fmt].drm_format;
drivers/gpu/drm/i915/gvt/fb_decoder.c line 199
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+ }else { + plane->tiled = !!(val &DISPPLANE_TILED ); + fmt = (val &DISPPLANE_PIXFORMAT_MASK ) >> _PRI_PLANE_FMT_SHIFT; + plane->bpp = primary_pixel_formats[fmt].bpp; + plane->drm_format = primary_pixel_formats[fmt].drm_format; + } + +if ((IS_SKYLAKE (dev_priv) && !skl_pixel_formats[fmt].bpp) + || (!IS_SKYLAKE (dev_priv) && + !primary_pixel_formats[fmt].bpp)) {
Just if (!plane->bpp)?
Quoted 19 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +19
-0+gvt_vgpu_err ("Non-supported pixel format (0x%x)\n" , fmt); +return -EINVAL ; + } + + plane->hw_format = fmt; + + plane->base =vgpu_vreg (vgpu,DSPSURF (pipe)) >T_PAGE_MASK ; + + plane->stride =intel_vgpu_get_stride (vgpu, pipe, (plane->tiled <<10 ), + (IS_SKYLAKE (dev_priv)) ? (_PRI_PLANE_STRIDE_MASK >>6 ) : + _PRI_PLANE_STRIDE_MASK, plane->bpp); + + plane->width = (vgpu_vreg (vgpu,PIPESRC (pipe)) & _PIPE_H_SRCSZ_MASK) >> + _PIPE_H_SRCSZ_SHIFT; + plane->width +=1 ; + plane->height = (vgpu_vreg (vgpu,PIPESRC (pipe)) & + _PIPE_V_SRCSZ_MASK) >> _PIPE_V_SRCSZ_SHIFT; + plane->height +=1 ;/* raw height is one minus the real value */ +
drivers/gpu/drm/i915/gvt/fb_decoder.c line 228
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+ val =vgpu_vreg (vgpu,DSPTILEOFF (pipe)); + plane->x_offset = (val & _PRI_PLANE_X_OFF_MASK) >> + _PRI_PLANE_X_OFF_SHIFT; + plane->y_offset = (val & _PRI_PLANE_Y_OFF_MASK) >> + _PRI_PLANE_Y_OFF_SHIFT; + +return 0 ; +} + +#define CURSOR_MODE_NUM (1 << 6)
CURSOR_FORMAT_NUM
Quoted 50 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +50
-0+struct cursor_mode_format { +int drm_format;/* Pixel format in DRM definition */ +u8 bpp;/* Bits per pixel; 0 indicates invalid */ +u32 width;/* In pixel */ +u32 height;/* In lines */ +char *desc;/* The description */ +}; + +/* non-supported format has bpp default to 0 */ +static struct cursor_mode_format cursor_pixel_formats[CURSOR_MODE_NUM ] = { + [0x22 ] = {DRM_FORMAT_ARGB8888 ,32 ,128 ,128 ,"128x128 32bpp ARGB" }, + [0x23 ] = {DRM_FORMAT_ARGB8888 ,32 ,256 ,256 ,"256x256 32bpp ARGB" }, + [0x27 ] = {DRM_FORMAT_ARGB8888 ,32 ,64 ,64 ,"64x64 32bpp ARGB" }, + [0x7 ] = {DRM_FORMAT_ARGB8888 ,32 ,64 ,64 ,"64x64 32bpp ARGB" }, +}; + +static int intel_vgpu_decode_cursor_plane_format (struct intel_vgpu *vgpu, +int pipe,struct intel_vgpu_cursor_plane_format *plane) +{ +u32 val, mode; +u32 alpha_plane, alpha_force; +struct drm_i915_private *dev_priv = vgpu->gvt->dev_priv; + + val =vgpu_vreg (vgpu,CURCNTR (pipe)); + mode = val &CURSOR_MODE ; + plane->enabled = (mode !=CURSOR_MODE_DISABLE ); +if (!plane->enabled) +return 0 ; + +if (!cursor_pixel_formats[mode].bpp) { +gvt_vgpu_err ("Non-supported cursor mode (0x%x)\n" , mode); +return -EINVAL ; + } + plane->mode = mode; + plane->bpp = cursor_pixel_formats[mode].bpp; + plane->drm_format = cursor_pixel_formats[mode].drm_format; + plane->width = cursor_pixel_formats[mode].width; + plane->height = cursor_pixel_formats[mode].height; + + alpha_plane = (val & _CURSOR_ALPHA_PLANE_MASK) >> + _CURSOR_ALPHA_PLANE_SHIFT; + alpha_force = (val & _CURSOR_ALPHA_FORCE_MASK) >> + _CURSOR_ALPHA_FORCE_SHIFT; +if (alpha_plane || alpha_force) +gvt_dbg_core ("alpha_plane=0x%x, alpha_force=0x%x\n" , + alpha_plane, alpha_force); + + plane->base =vgpu_vreg (vgpu,CURBASE (pipe)) >T_PAGE_MASK ; + + val =vgpu_vreg (vgpu,CURPOS (pipe));
drivers/gpu/drm/i915/gvt/fb_decoder.c line 288
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+ plane->x_pos = (val & _CURSOR_POS_X_MASK) >> _CURSOR_POS_X_SHIFT; + plane->x_sign = (val & _CURSOR_SIGN_X_MASK) >> _CURSOR_SIGN_X_SHIFT; + plane->y_pos = (val & _CURSOR_POS_Y_MASK) >> _CURSOR_POS_Y_SHIFT; + plane->y_sign = (val & _CURSOR_SIGN_Y_MASK) >> _CURSOR_SIGN_Y_SHIFT; + +return 0 ; +} + +#define FORMAT_NUM_SRRITE (1 << 3) +
SPRITE_FORMAT_NUM
Quoted 40 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +40
-0+static struct pixel_format sprite_pixel_formats[FORMAT_NUM_SRRITE ] = { + [0x0 ] = {DRM_FORMAT_YUV422 ,16 ,"YUV 16-bit 4:2:2 packed" }, + [0x1 ] = {DRM_FORMAT_XRGB2101010 ,32 ,"RGB 32-bit 2:10:10:10" }, + [0x2 ] = {DRM_FORMAT_XRGB8888 ,32 ,"RGB 32-bit 8:8:8:8" }, + [0x3 ] = {DRM_FORMAT_XRGB161616_GVT ,64 , +"RGB 64-bit 16:16:16:16 Floating Point" }, + [0x4 ] = {DRM_FORMAT_AYUV ,32 , +"YUV 32-bit 4:4:4 packed (8:8:8:8 MSB-X:Y:U:V)" }, +}; + +static int intel_vgpu_decode_sprite_plane_format (struct intel_vgpu *vgpu, +int pipe,struct intel_vgpu_sprite_plane_format *plane) +{ +u32 val, fmt; +u32 width; +u32 color_order, yuv_order; +int drm_format; + + val =vgpu_vreg (vgpu,SPRCTL (pipe)); + plane->enabled = !!(val &SPRITE_ENABLE ); +if (!plane->enabled) +return 0 ; + + plane->tiled = !!(val &SPRITE_TILED ); + color_order = !!(val &SPRITE_RGB_ORDER_RGBX ); + yuv_order = (val &SPRITE_YUV_BYTE_ORDER_MASK ) >> + _SPRITE_YUV_ORDER_SHIFT; + + fmt = (val &SPRITE_PIXFORMAT_MASK ) >> _SPRITE_FMT_SHIFT; +if (!sprite_pixel_formats[fmt].bpp) { +gvt_vgpu_err ("Non-supported pixel format (0x%x)\n" , fmt); +return -EINVAL ; + } + plane->hw_format = fmt; + plane->bpp = sprite_pixel_formats[fmt].bpp; + drm_format = sprite_pixel_formats[fmt].drm_format; + +/* Order of RGB values in an RGBxxx buffer may be ordered RGB or +* BGR depending on the state of the color_order field +*/
drivers/gpu/drm/i915/gvt/fb_decoder.c line 338
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+if (!color_order) { +if (drm_format ==DRM_FORMAT_XRGB2101010 ) + drm_format =DRM_FORMAT_XBGR2101010 ; +else if (drm_format ==DRM_FORMAT_XRGB8888 ) + drm_format =DRM_FORMAT_XBGR8888 ; + } + +if (drm_format ==DRM_FORMAT_YUV422 ) { +switch (yuv_order) { +case 0 :
no extra space
Quoted 23 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +23
-0+ drm_format =DRM_FORMAT_YUYV ; +break ; +case 1 : + drm_format =DRM_FORMAT_UYVY ; +break ; +case 2 : + drm_format =DRM_FORMAT_YVYU ; +break ; +case 3 : + drm_format =DRM_FORMAT_VYUY ; +break ; +default : +/* yuv_order has only 2 bits */ +break ; + } + } + + plane->drm_format = drm_format; + + plane->base =vgpu_vreg (vgpu,SPRSURF (pipe)) >T_PAGE_MASK ; + plane->width =vgpu_vreg (vgpu,SPRSTRIDE (pipe)) & + _SPRITE_STRIDE_MASK; + plane->width /= plane->bpp /8 ;/* raw width in bytes */
drivers/gpu/drm/i915/gvt/fb_decoder.c line 371
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+ + val =vgpu_vreg (vgpu,SPRSIZE (pipe)); + plane->height = (val & _SPRITE_SIZE_HEIGHT_MASK) >> + _SPRITE_SIZE_HEIGHT_SHIFT; + width = (val & _SPRITE_SIZE_WIDTH_MASK) >> _SPRITE_SIZE_WIDTH_SHIFT; + plane->height +=1 ;/* raw height is one minus the real value */ + width +=1 ;/* raw width is one minus the real value */ +if (plane->width != width) +gvt_dbg_core ("sprite_plane: plane->width=%d, width=%d\n" , + plane->width, width);
should report error?
Quoted 75 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +75
-0+static int intel_vgpu_decode_fb_format (struct intel_gvt *gvt,int id, +struct intel_vgpu_fb_format *fb) +{ +int i; +struct intel_vgpu *vgpu =NULL ; +int ret =0 ; +struct drm_i915_private *dev_priv = gvt->dev_priv; + +if (!fb) +return -EINVAL ; + +/* TODO: use fine-grained refcnt later */ +mutex_lock (&gvt->lock); + +for_each_active_vgpu (gvt, vgpu, i) +if (vgpu->id == id) +break ; + +if (!vgpu) { +gvt_vgpu_err ("Invalid vgpu ID (%d)\n" , id); +mutex_unlock (&gvt->lock); +return -ENODEV ; + } + +for (i =0 ; i <I915_MAX_PIPES ; i++) { +struct intel_vgpu_pipe_format *pipe = &fb->pipes[i]; +u32 ddi_func_ctl =vgpu_vreg (vgpu,TRANS_DDI_FUNC_CTL (i)); + +if (!(ddi_func_ctl &TRANS_DDI_FUNC_ENABLE )) { + pipe->ddi_port =DDI_PORT_NONE ; + }else { +u32 port = (ddi_func_ctl &TRANS_DDI_PORT_MASK ) >> +TRANS_DDI_PORT_SHIFT ; +if (port <=DDI_PORT_E ) + pipe->ddi_port = port; +else + pipe->ddi_port =DDI_PORT_NONE ; + } + + ret |=intel_vgpu_decode_primary_plane_format (vgpu, + i, &pipe->primary); + ret |=intel_vgpu_decode_sprite_plane_format (vgpu, + i, &pipe->sprite); + ret |=intel_vgpu_decode_cursor_plane_format (vgpu, + i, &pipe->cursor); + +if (ret) { +gvt_vgpu_err ("Decode format error for pipe(%d)\n" , i); + ret = -EINVAL ; +break ; + } + } + +mutex_unlock (&gvt->lock); + +return ret; +} + +/** +* intel_vgpu_decode_plane - Decode plane based on plane id +* @dev: drm device +* @vgpu: input vgpu +* This function is called for decoding plane +* +* Returns: +* pipe on success, NULL if failed. +*/ +struct intel_vgpu_pipe_format *intel_vgpu_decode_plane (struct drm_device *dev, +struct intel_vgpu *vgpu) +{ +struct drm_i915_private *dev_priv = dev->dev_private; +struct intel_vgpu_fb_format fb; +struct intel_vgpu_pipe_format *pipe; +int i; +
drivers/gpu/drm/i915/gvt/fb_decoder.c line 469
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+if (intel_vgpu_decode_fb_format (dev_priv->gvt, vgpu->id, &fb)) +return NULL ; + +for (i =0 ; i <I915_MAX_PIPES ; i++) +if (pipe_is_enabled (vgpu, i)) +break ; +if (i >=I915_MAX_PIPES ) { +gvt_dbg_core ("No enabled pipes\n" ); +return NULL ; + }
Looks this check should be moved in above decode_fb_format function which doesn't check if pipe is actually enabled.
drivers/gpu/drm/i915/gvt/fb_decoder.c line 475
Quoted 6 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +6
-0+ pipe = &fb.pipes[i]; + +if (!pipe || !pipe->primary.enabled) { +gvt_dbg_core ("Invalid pipe_id :%d\n" , i); +return NULL ; + }
And this function is to find primary plane actually? Should name it like intel_vgpu_decode_primary_plane().
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +4
-0+ +return pipe; +} +drivers/gpu/drm/i915/gvt/fb_decoder.h new file +1
-0+
drivers/gpu/drm/i915/gvt/fb_decoder.h line 161
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.h new file +10
-0+struct intel_vgpu_pipe_format { +struct intel_vgpu_primary_plane_format primary; +struct intel_vgpu_sprite_plane_format sprite; +struct intel_vgpu_cursor_plane_format cursor; +enum DDI_PORT ddi_port;/* the DDI port that pipe is connected to */ +}; + +struct intel_vgpu_fb_format { +struct intel_vgpu_pipe_format pipes[4 ]; +};
Should use MAX_PIPE definition.
Signature · 3 lines
Open Source Technology Center, Intel ltd. $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
RE: [PATCH v6 3/6] drm/i915/gvt: Frame buffer decoder support for GVT-g
Quoted 134 lines
-----Original Message-----
From: Zhenyu Wang [mailto:[email protected]]
Sent: Wednesday, May 31, 2017 1:12 PM
To: Chen, Xiaoguang <[email protected]>
Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 3/6] drm/i915/gvt: Frame buffer decoder support for GVT- gQuoted 21 lines · Xiaoguang Chen
decode frambuffer attributes of primary, cursor and sprite plane
Signed-off-by Xiaoguang Chen <[email protected]>--- drivers/gpu/drm/i915/gvt/Makefile | 3 +- drivers/gpu/drm/i915/gvt/display.c | 2 +- drivers/gpu/drm/i915/gvt/display.h | 2 + drivers/gpu/drm/i915/gvt/fb_decoder.c | 479 ++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/gvt/fb_decoder.h | 166 ++++++++++++ drivers/gpu/drm/i915/gvt/gvt.h | 1 + 6 files changed, 651 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/drm/i915/gvt/fb_decoder.c create mode 100644 drivers/gpu/drm/i915/gvt/fb_decoder.hdrivers/gpu/drm/i915/gvt/Makefile +0
-0drivers/gpu/drm/i915/gvt/Makefile line 2
Quoted 2 lines
drivers/gpu/drm/i915/gvt/Makefile +0
-0@@ -1,7 +1,8 @@ GVT_DIR := gvt GVT_SOURCE := gvt.o aperture_gm.o handlers.o vgpu.o trace_points.ofirmware.o \
drivers/gpu/drm/i915/gvt/Makefile
Quoted 7 lines
drivers/gpu/drm/i915/gvt/Makefile +2
-1interrupt.o gtt.o cfg_space.o opregion.o mmio.o display.o edid.o \ - execlist.o scheduler.o sched_policy.o render.o cmd_parser.o + execlist.o scheduler.o sched_policy.o render.o cmd_parser.o \ + fb_decoder.o ccflags-y += -I$(src) -I$(src)/$(GVT_DIR) -Wall i915-y += $(addprefix $(GVT_DIR)/,$(GVT_SOURCE))
Quoted 50 lines
drivers/gpu/drm/i915/gvt/display.c +1
-1@@ -67,7 +67,7 @@ static int edp_pipe_is_enabled(struct intel_vgpu *vgpu)return 1 ; } -static int pipe_is_enabled (struct intel_vgpu *vgpu,int pipe) +int pipe_is_enabled (struct intel_vgpu *vgpu,int pipe) {struct drm_i915_private *dev_priv = vgpu->gvt->dev_priv;drivers/gpu/drm/i915/gvt/display.h +0
-0@@ -179,4 +179,6 @@ int intel_vgpu_init_display(struct intel_vgpu *vgpu, u64 resolution); void intel_vgpu_reset_display(struct
intel_vgpu*vgpu); voidintel_vgpu_clean_display(struct intel_vgpu *vgpu);drivers/gpu/drm/i915/gvt/display.h +2
-0+int pipe_is_enabled (struct intel_vgpu *vgpu,int pipe); +#endif drivers/gpu/drm/i915/gvt/fb_decoder.c new file +16
-0@@ -0,0 +1,479 @@ +/* +* Copyright(c) 2011-2016 Intel Corporation. All rights reserved. +* +* Permission is hereby granted, free of charge, to any person +obtaining a +* copy of this software and associated documentation files (the +"Software"), +* to deal in the Software without restriction, including without +limitation +* the rights to use, copy, modify, merge, publish, distribute, +sublicense, +* and/or sell copies of the Software, and to permit persons to whom +the +* Software is furnished to do so, subject to the following conditions: +* +* The above copyright notice and this permission notice (including drivers/gpu/drm/i915/gvt/fb_decoder.c line 26
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+the next + * paragraph) shall be included in all copies or substantial portions +of the + * Software. + * + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +EXPRESS OR + * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF +MERCHANTABILITY , + * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NOEVENT
drivers/gpu/drm/i915/gvt/fb_decoder.c line 28
Quoted 2 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +2
-0+SHALL + * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,DAMAGES
Quoted 23 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +23
-0+OR OTHER +* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, +ARISING FROM, +* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER +DEALINGS IN THE +* SOFTWARE. +* +* Authors: +* Kevin Tian <[email protected]> +* +* Contributors: +* Bing Niu <[email protected]> +* Xu Han <[email protected]> +* Ping Gao <[email protected]> +* Xiaoguang Chen <[email protected]> +* Yang Liu <[email protected]> +* +*/ + +#include <uapi/drm/drm_fourcc.h> +#include "i915_drv.h" +#include "gvt.h" +
Quoted 8 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c line 57
Quoted 6 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +6
-0+/* The below definitions are required by guest. */ // [63:0] x:R:G:B +16:16:16:16 little endian #define DRM_FORMAT_XRGB161616_GVT +fourcc_code('X', 'R', '4', '8') // [63:0] x:B:G:R 16:16:16:16 little +endian #define DRM_FORMAT_XBGR161616_GVT fourcc_code('X', 'B', '4', +'8') +Should be added to
drm_fourcc?
Will add to drm_fourcc.
Quoted 19 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c line 45
Quoted 2 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +1
-0+#define FORMAT_NUM 16
PRIMARY_FORMAT_NUMQuoted 14 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +14
-0+struct pixel_format { +int drm_format;/* Pixel format in DRM definition */ +int bpp;/* Bits per pixel, 0 indicates invalid */ +char *desc;/* The description */ +}; + +/* non-supported format has bpp default to 0 */ static struct +pixel_format primary_pixel_formats[FORMAT_NUM ] = { + [0x2 ] = {DRM_FORMAT_C8 ,8 ,"8-bit Indexed" }, + [0x5 ] = {DRM_FORMAT_RGB565 ,16 ,"16-bit BGRX (5:6:5 MSB-R:G:B)" }, + [0x6 ] = {DRM_FORMAT_XRGB8888 ,32 , +"32-bit BGRX (8:8:8:8 MSB-X:R:G:B)" }, + [0x8 ] = {DRM_FORMAT_XBGR2101010 ,32 , +"32-bit RGBX (2:10:10:10 MSB-X:B:G:R)" },
Quoted 8 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c
Quoted 6 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +6
-0+ [0xa ] = {DRM_FORMAT_XRGB2101010 ,32 , + "32-bit BGRX (2:10:10:10 MSB-X:R:G:B)"}, + [0xc ] = {DRM_FORMAT_XRGB161616_GVT ,64 , + "64-bit RGBX Floating Point(16:16:16:16 MSB-X:B:G:R)"}, + [0xe ] = {DRM_FORMAT_XBGR8888 ,32 , + "32-bit RGBX (8:8:8:8 MSB-X:B:G:R)"}, };might explicitly say this is
bdw_pixel_formats?
Good suggestion :)
Quoted 132 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c line 82
Quoted 5 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +4
-0+ +/* non-supported format has bpp default to 0 */ static struct +pixel_format skl_pixel_formats[] = { + {DRM_FORMAT_YUYV, 16, "16-bit packed YUYV (8:8:8:8 MSB-V:Y2:U:Y1)"},
drivers/gpu/drm/i915/gvt/fb_decoder.c line 83
Quoted 1 line
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +1
-0+ {DRM_FORMAT_UYVY, 16, "16-bit packed UYVY (8:8:8:8 MSB-Y2:V:Y1:U)"},
drivers/gpu/drm/i915/gvt/fb_decoder.c line 84
Quoted 1 line
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +1
-0+ {DRM_FORMAT_YVYU, 16, "16-bit packed YVYU (8:8:8:8 MSB-U:Y2:V:Y1)"},
drivers/gpu/drm/i915/gvt/fb_decoder.c line 85
Quoted 1 line
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +1
-0+ {DRM_FORMAT_VYUY, 16, "16-bit packed VYUY (8:8:8:8 MSB-Y2:U:Y1:V)"},
drivers/gpu/drm/i915/gvt/fb_decoder.c
Quoted 9 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +9
-0+ + {DRM_FORMAT_C8, 8, "8-bit Indexed"}, + {DRM_FORMAT_RGB565, 16, "16-bit BGRX (5:6:5 MSB-R:G:B)"}, + {DRM_FORMAT_ABGR8888, 32, "32-bit RGBA (8:8:8:8 MSB-A:B:G:R)"}, + {DRM_FORMAT_XBGR8888, 32, "32-bit RGBX (8:8:8:8 MSB-X:B:G:R)"}, + + {DRM_FORMAT_ARGB8888, 32, "32-bit BGRA (8:8:8:8 MSB-A:R:G:B)"}, + {DRM_FORMAT_XRGB8888, 32, "32-bit BGRX (8:8:8:8 MSB-X:R:G:B)"}, + {DRM_FORMAT_XBGR2101010, 32, "32-bit RGBX (2:10:10:10 MSB-X:B:G:R)"},
Quoted 99 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +99
-0+ {DRM_FORMAT_XRGB2101010, 32, "32-bit BGRX (2:10:10:10 +MSB-X:R:G:B)"}, + + {DRM_FORMAT_XRGB161616_GVT, 64, + "64-bit XRGB (16:16:16:16 MSB-X:R:G:B)"}, + {DRM_FORMAT_XBGR161616_GVT, 64, + "64-bit XBGR (16:16:16:16 MSB-X:B:G:R)"}, + + /* non-supported format has bpp default to 0 */ + {0, 0, NULL}, +}; + +static int skl_format_to_drm(int format, bool rgb_order, bool alpha, + int yuv_order) +{ + int skl_pixel_formats_index = 14; + + switch (format) { + case PLANE_CTL_FORMAT_INDEXED: + skl_pixel_formats_index = 4; + break; + case PLANE_CTL_FORMAT_RGB_565: + skl_pixel_formats_index = 5; + break; + case PLANE_CTL_FORMAT_XRGB_8888: + if (rgb_order) + skl_pixel_formats_index = alpha ? 6 : 7; + else + skl_pixel_formats_index = alpha ? 8 : 9; + break; + case PLANE_CTL_FORMAT_XRGB_2101010: + skl_pixel_formats_index = rgb_order ? 10 : 11; + break; + + case PLANE_CTL_FORMAT_XRGB_16161616F: + skl_pixel_formats_index = rgb_order ? 12 : 13; + break; + + case PLANE_CTL_FORMAT_YUV422: + skl_pixel_formats_index = yuv_order >> 16; + if (skl_pixel_formats_index > 3) + return -EINVAL; + break; + + default: + break; + } + + return skl_pixel_formats_index; +} + +static u32 intel_vgpu_get_stride(struct intel_vgpu *vgpu, int pipe, + u32 tiled, int stride_mask, int bpp) { + struct drm_i915_private *dev_priv = vgpu->gvt->dev_priv; + + u32 stride_reg = vgpu_vreg(vgpu, DSPSTRIDE(pipe)) & stride_mask; + u32 stride = stride_reg; + + if (IS_SKYLAKE(dev_priv)) { + switch (tiled) { + case PLANE_CTL_TILED_LINEAR: + stride = stride_reg * 64; + break; + case PLANE_CTL_TILED_X: + stride = stride_reg * 512; + break; + case PLANE_CTL_TILED_Y: + stride = stride_reg * 128; + break; + case PLANE_CTL_TILED_YF: + if (bpp == 8) + stride = stride_reg * 64; + else if (bpp == 16 || bpp == 32 || bpp == 64) + stride = stride_reg * 128; + else + gvt_dbg_core("skl: unsupported bpp:%d\n", bpp); + break; + default: + gvt_dbg_core("skl: unsupported tile format:%x\n", + tiled); + } + } + + return stride; +} + +static int intel_vgpu_decode_primary_plane_format(struct intel_vgpu *vgpu, + int pipe, struct intel_vgpu_primary_plane_format *plane) { + u32 val, fmt; + struct drm_i915_private *dev_priv = vgpu->gvt->dev_priv; + + val = vgpu_vreg(vgpu, DSPCNTR(pipe)); + plane->enabled = !!(val & DISPLAY_PLANE_ENABLE); + if (!plane->enabled) + return 0; + + if (IS_SKYLAKE(dev_priv)) { + plane->tiled = (val & PLANE_CTL_TILED_MASK) >> + _PLANE_CTL_TILED_SHIFT;drivers/gpu/drm/i915/gvt/fb_decoder.c
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+ fmt =skl_format_to_drm ( + val &PLANE_CTL_FORMAT_MASK , + val &PLANE_CTL_ORDER_RGBX , + val &PLANE_CTL_ALPHA_MASK , + val &PLANE_CTL_YUV422_ORDER_MASK ); + plane->bpp = skl_pixel_formats[fmt].bpp; + plane->drm_format = skl_pixel_formats[fmt].drm_format; + }else { + plane->tiled = !!(val &DISPPLANE_TILED ); + fmt = (val & DISPPLANE_PIXFORMAT_MASK) >>
_PRI_PLANE_FMT_SHIFT;
Quoted 9 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c line 199
Quoted 7 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +7
-0+ plane->bpp = primary_pixel_formats[fmt].bpp; + plane->drm_format = primary_pixel_formats[fmt].drm_format; + } + +if ((IS_SKYLAKE (dev_priv) && !skl_pixel_formats[fmt].bpp) + || (!IS_SKYLAKE (dev_priv) && + !primary_pixel_formats[fmt].bpp)) {Just if (!plane->bpp)?
Good suggestion :)
Quoted 181 lines
Quoted 4 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +3
-0+gvt_vgpu_err ("Non-supported pixel format (0x%x)\n" , fmt); +return -EINVAL ; + }drivers/gpu/drm/i915/gvt/fb_decoder.c
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+ + plane->hw_format = fmt; + + plane->base =vgpu_vreg (vgpu,DSPSURF (pipe)) >T_PAGE_MASK ; + + plane->stride =intel_vgpu_get_stride (vgpu, pipe, (plane->tiled <<10 ), + (IS_SKYLAKE (dev_priv)) ? (_PRI_PLANE_STRIDE_MASK >>6 ) : + _PRI_PLANE_STRIDE_MASK, plane->bpp); + + plane->width = (vgpu_vreg(vgpu, PIPESRC(pipe)) &
_PIPE_H_SRCSZ_MASK) >>Quoted 6 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +6
-0+ _PIPE_H_SRCSZ_SHIFT; + plane->width +=1 ; + plane->height = (vgpu_vreg (vgpu,PIPESRC (pipe)) & + _PIPE_V_SRCSZ_MASK) >> _PIPE_V_SRCSZ_SHIFT; + plane->height +=1 ;/* raw height is one minus the real value */ +drivers/gpu/drm/i915/gvt/fb_decoder.c line 228
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+ val =vgpu_vreg (vgpu,DSPTILEOFF (pipe)); + plane->x_offset = (val & _PRI_PLANE_X_OFF_MASK) >> + _PRI_PLANE_X_OFF_SHIFT; + plane->y_offset = (val & _PRI_PLANE_Y_OFF_MASK) >> + _PRI_PLANE_Y_OFF_SHIFT; + +return 0 ; +} + +#define CURSOR_MODE_NUM (1 << 6)
CURSOR_FORMAT_NUMdrivers/gpu/drm/i915/gvt/fb_decoder.c
Quoted 11 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +11
-0+struct cursor_mode_format { +int drm_format;/* Pixel format in DRM definition */ +u8 bpp;/* Bits per pixel; 0 indicates invalid */ +u32 width;/* In pixel */ +u32 height;/* In lines */ +char *desc;/* The description */ +}; + +/* non-supported format has bpp default to 0 */ static struct +cursor_mode_format cursor_pixel_formats[CURSOR_MODE_NUM ] = { + [0x22] = {DRM_FORMAT_ARGB8888, 32, 128, 128, "128x128 32bppARGB"},
drivers/gpu/drm/i915/gvt/fb_decoder.c line 251
Quoted 1 line
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +1
-0+ [0x23] = {DRM_FORMAT_ARGB8888, 32, 256, 256, "256x256 32bppARGB"},
Quoted 27 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +27
-0+ [0x27] = {DRM_FORMAT_ARGB8888, 32, 64, 64, "64x64 32bpp ARGB"}, + [0x7] = {DRM_FORMAT_ARGB8888, 32, 64, 64, "64x64 32bpp ARGB"}, }; + +static int intel_vgpu_decode_cursor_plane_format (struct intel_vgpu *vgpu, +int pipe,struct intel_vgpu_cursor_plane_format *plane) { +u32 val, mode; +u32 alpha_plane, alpha_force; +struct drm_i915_private *dev_priv = vgpu->gvt->dev_priv; + + val =vgpu_vreg (vgpu,CURCNTR (pipe)); + mode = val &CURSOR_MODE ; + plane->enabled = (mode !=CURSOR_MODE_DISABLE ); +if (!plane->enabled) +return 0 ; + +if (!cursor_pixel_formats[mode].bpp) { +gvt_vgpu_err ("Non-supported cursor mode (0x%x)\n" , mode); +return -EINVAL ; + } + plane->mode = mode; + plane->bpp = cursor_pixel_formats[mode].bpp; + plane->drm_format = cursor_pixel_formats[mode].drm_format; + plane->width = cursor_pixel_formats[mode].width; + plane->height = cursor_pixel_formats[mode].height; + + alpha_plane = (val & _CURSOR_ALPHA_PLANE_MASK) >> + _CURSOR_ALPHA_PLANE_SHIFT;drivers/gpu/drm/i915/gvt/fb_decoder.c
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+ alpha_force = (val & _CURSOR_ALPHA_FORCE_MASK) >> + _CURSOR_ALPHA_FORCE_SHIFT; +if (alpha_plane || alpha_force) +gvt_dbg_core ("alpha_plane=0x%x, alpha_force=0x%x\n" , + alpha_plane, alpha_force); + + plane->base =vgpu_vreg (vgpu,CURBASE (pipe)) >T_PAGE_MASK ; + + val =vgpu_vreg (vgpu,CURPOS (pipe)); + plane->x_pos = (val & _CURSOR_POS_X_MASK) >>
_CURSOR_POS_X_SHIFT;drivers/gpu/drm/i915/gvt/fb_decoder.c line 289
Quoted 1 line
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +1
-0+ plane->x_sign = (val & _CURSOR_SIGN_X_MASK) >>
_CURSOR_SIGN_X_SHIFT;drivers/gpu/drm/i915/gvt/fb_decoder.c line 290
Quoted 1 line
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +1
-0+ plane->y_pos = (val & _CURSOR_POS_Y_MASK) >>
_CURSOR_POS_Y_SHIFT;drivers/gpu/drm/i915/gvt/fb_decoder.c line 291
Quoted 1 line
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +1
-0+ plane->y_sign = (val & _CURSOR_SIGN_Y_MASK) >>
_CURSOR_SIGN_Y_SHIFT;drivers/gpu/drm/i915/gvt/fb_decoder.c line 288
Quoted 6 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +6
-0+ +return 0 ; +} + +#define FORMAT_NUM_SRRITE (1 << 3) +
SPRITE_FORMAT_NUMQuoted 38 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +38
-0+static struct pixel_format sprite_pixel_formats[FORMAT_NUM_SRRITE ] = { + [0x0 ] = {DRM_FORMAT_YUV422 ,16 ,"YUV 16-bit 4:2:2 packed" }, + [0x1 ] = {DRM_FORMAT_XRGB2101010 ,32 ,"RGB 32-bit 2:10:10:10" }, + [0x2 ] = {DRM_FORMAT_XRGB8888 ,32 ,"RGB 32-bit 8:8:8:8" }, + [0x3 ] = {DRM_FORMAT_XRGB161616_GVT ,64 , +"RGB 64-bit 16:16:16:16 Floating Point" }, + [0x4 ] = {DRM_FORMAT_AYUV ,32 , +"YUV 32-bit 4:4:4 packed (8:8:8:8 MSB-X:Y:U:V)" }, }; + +static int intel_vgpu_decode_sprite_plane_format (struct intel_vgpu *vgpu, +int pipe,struct intel_vgpu_sprite_plane_format *plane) { +u32 val, fmt; +u32 width; +u32 color_order, yuv_order; +int drm_format; + + val =vgpu_vreg (vgpu,SPRCTL (pipe)); + plane->enabled = !!(val &SPRITE_ENABLE ); +if (!plane->enabled) +return 0 ; + + plane->tiled = !!(val &SPRITE_TILED ); + color_order = !!(val &SPRITE_RGB_ORDER_RGBX ); + yuv_order = (val &SPRITE_YUV_BYTE_ORDER_MASK ) >> + _SPRITE_YUV_ORDER_SHIFT; + + fmt = (val &SPRITE_PIXFORMAT_MASK ) >> _SPRITE_FMT_SHIFT; +if (!sprite_pixel_formats[fmt].bpp) { +gvt_vgpu_err ("Non-supported pixel format (0x%x)\n" , fmt); +return -EINVAL ; + } + plane->hw_format = fmt; + plane->bpp = sprite_pixel_formats[fmt].bpp; + drm_format = sprite_pixel_formats[fmt].drm_format; + +/* Order of RGB values in an RGBxxx buffer may be ordered RGB or +* BGR depending on the state of the color_order field +*/ drivers/gpu/drm/i915/gvt/fb_decoder.c line 338
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+if (!color_order) { +if (drm_format ==DRM_FORMAT_XRGB2101010 ) + drm_format =DRM_FORMAT_XBGR2101010 ; +else if (drm_format ==DRM_FORMAT_XRGB8888 ) + drm_format =DRM_FORMAT_XBGR8888 ; + } + +if (drm_format ==DRM_FORMAT_YUV422 ) { +switch (yuv_order) { +case 0 :no extra space
Quoted 18 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +18
-0+ drm_format =DRM_FORMAT_YUYV ; +break ; +case 1 : + drm_format =DRM_FORMAT_UYVY ; +break ; +case 2 : + drm_format =DRM_FORMAT_YVYU ; +break ; +case 3 : + drm_format =DRM_FORMAT_VYUY ; +break ; +default : +/* yuv_order has only 2 bits */ +break ; + } + } + + plane->drm_format = drm_format;drivers/gpu/drm/i915/gvt/fb_decoder.c
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+ + plane->base =vgpu_vreg (vgpu,SPRSURF (pipe)) >T_PAGE_MASK ; + plane->width =vgpu_vreg (vgpu,SPRSTRIDE (pipe)) & + _SPRITE_STRIDE_MASK; + plane->width /= plane->bpp /8 ;/* raw width in bytes */ + + val =vgpu_vreg (vgpu,SPRSIZE (pipe)); + plane->height = (val & _SPRITE_SIZE_HEIGHT_MASK) >> + _SPRITE_SIZE_HEIGHT_SHIFT; + width = (val & _SPRITE_SIZE_WIDTH_MASK) >>
_SPRITE_SIZE_WIDTH_SHIFT;
Quoted 7 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c line 371
Quoted 5 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +5
-0+ plane->height +=1 ;/* raw height is one minus the real value */ + width +=1 ;/* raw width is one minus the real value */ +if (plane->width != width) +gvt_dbg_core ("sprite_plane: plane->width=%d, width=%d\n" , + plane->width, width);should report error?
OK.
Quoted 82 lines
Quoted 59 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +58
-0+static int intel_vgpu_decode_fb_format (struct intel_gvt *gvt,int id, +struct intel_vgpu_fb_format *fb) +{ +int i; +struct intel_vgpu *vgpu =NULL ; +int ret =0 ; +struct drm_i915_private *dev_priv = gvt->dev_priv; + +if (!fb) +return -EINVAL ; + +/* TODO: use fine-grained refcnt later */ +mutex_lock (&gvt->lock); + +for_each_active_vgpu (gvt, vgpu, i) +if (vgpu->id == id) +break ; + +if (!vgpu) { +gvt_vgpu_err ("Invalid vgpu ID (%d)\n" , id); +mutex_unlock (&gvt->lock); +return -ENODEV ; + } + +for (i =0 ; i <I915_MAX_PIPES ; i++) { +struct intel_vgpu_pipe_format *pipe = &fb->pipes[i]; +u32 ddi_func_ctl =vgpu_vreg (vgpu,TRANS_DDI_FUNC_CTL (i)); + +if (!(ddi_func_ctl &TRANS_DDI_FUNC_ENABLE )) { + pipe->ddi_port =DDI_PORT_NONE ; + }else { +u32 port = (ddi_func_ctl &TRANS_DDI_PORT_MASK ) >> +TRANS_DDI_PORT_SHIFT ; +if (port <=DDI_PORT_E ) + pipe->ddi_port = port; +else + pipe->ddi_port =DDI_PORT_NONE ; + } + + ret |=intel_vgpu_decode_primary_plane_format (vgpu, + i, &pipe->primary); + ret |=intel_vgpu_decode_sprite_plane_format (vgpu, + i, &pipe->sprite); + ret |=intel_vgpu_decode_cursor_plane_format (vgpu, + i, &pipe->cursor); + +if (ret) { +gvt_vgpu_err ("Decode format error for pipe(%d)\n" , i); + ret = -EINVAL ; +break ; + } + } + +mutex_unlock (&gvt->lock); + +return ret; +} +drivers/gpu/drm/i915/gvt/fb_decoder.c
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +10
-0+/** +* intel_vgpu_decode_plane - Decode plane based on plane id +* @dev: drm device +* @vgpu: input vgpu +* This function is called for decoding plane +* +* Returns: +* pipe on success, NULL if failed. +*/ +struct intel_vgpu_pipe_format *intel_vgpu_decode_plane(struct drm_device*dev,
Quoted 12 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +12
-0+ struct intel_vgpu *vgpu) +{ +struct drm_i915_private *dev_priv = dev->dev_private; +struct intel_vgpu_fb_format fb; +struct intel_vgpu_pipe_format *pipe; +int i; + +if (intel_vgpu_decode_fb_format (dev_priv->gvt, vgpu->id, &fb)) +return NULL ; + +for (i =0 ; i <I915_MAX_PIPES ; i++) +if (pipe_is_enabled (vgpu, i))
Quoted 8 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c line 469
Quoted 5 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +5
-0+break ; +if (i >=I915_MAX_PIPES ) { +gvt_dbg_core ("No enabled pipes\n" ); +return NULL ; + }Looks this check should be moved in above
decode_fb_formatfunction which doesn't check if pipe is actually enabled.
Good suggestion :)
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c line 475
Quoted 7 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +6
-0+ pipe = &fb.pipes[i]; + +if (!pipe || !pipe->primary.enabled) { +gvt_dbg_core ("Invalid pipe_id :%d\n" , i); +return NULL ; + }And this function is to find primary plane actually? Should name it like
intel_vgpu_decode_primary_plane().
Not exactly. This function will decode plane based on the input plane id in our case: primary plane and cursor plane.
Quoted 25 lines
Quoted 12 lines
drivers/gpu/drm/i915/gvt/fb_decoder.c new file +4
-0+ +return pipe; +} +drivers/gpu/drm/i915/gvt/fb_decoder.h new file +1
-0+drivers/gpu/drm/i915/gvt/fb_decoder.h line 161
Quoted 10 lines
drivers/gpu/drm/i915/gvt/fb_decoder.h new file +10
-0+struct intel_vgpu_pipe_format { +struct intel_vgpu_primary_plane_format primary; +struct intel_vgpu_sprite_plane_format sprite; +struct intel_vgpu_cursor_plane_format cursor; +enum DDI_PORT ddi_port;/* the DDI port that pipe is connected to +*/ }; + +struct intel_vgpu_fb_format { +struct intel_vgpu_pipe_format pipes[4 ]; +};Should use
MAX_PIPEdefinition.
Quoted 4 lines
--
Open Source Technology Center, Intel ltd.$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v6 4/6 vfio: Define vfio based vgpu's dma-buf operations
In reply to Xiaoguang ChenHere we defined a new ioctl to create a fd for a vfio device based on the input type. Now only one type is supported that is a dma-buf management fd.
Two ioctls are defined for the dma-buf management fd: query the vfio vgpu's plane information and create a dma-buf for a plane.
--- include/uapi/linux/vfio.h | 50 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+)
include/uapi/linux/vfio.h +50 -0
@@ -502,6 +502,56 @@ struct vfio_pci_hot_reset {#define VFIO_DEVICE_PCI_HOT_RESET _IO(VFIO_TYPE, VFIO_BASE + 13) +/** +* VFIO_DEVICE_GET_FD - _IO(VFIO_TYPE, VFIO_BASE + 14, __u32) +* +* Create a fd for a vfio device based on the input type +* Vendor driver should handle this ioctl to create a fd and manage the +* life cycle of this fd. +* +* Return: a fd if vendor support that type, -errno if not supported +*/ + +#define VFIO_DEVICE_GET_FD _IO(VFIO_TYPE, VFIO_BASE + 14) + +#define VFIO_DEVICE_DMABUF_MGR_FD 0/* Supported fd types */ + +/* +* VFIO_DEVICE_QUERY_PLANE - _IO(VFIO_TYPE, VFIO_BASE + 15, struct plane_info) +* Query plane information for a plane +*/ +struct vfio_vgpu_plane_info { +__u32 argsz; +__u32 flags; +__u32 plane_id; +__u32 drm_format; +__u32 width; +__u32 height; +__u32 stride; +__u32 start; +__u32 x_pos; +__u32 y_pos; +__u64 drm_format_mod; +__u32 size; +__u32 pad; +}; + +#define VFIO_DEVICE_QUERY_PLANE _IO(VFIO_TYPE, VFIO_BASE + 15) + +/* +* VFIO_DEVICE_CREATE_DMABUF - _IO(VFIO, VFIO_BASE + 16, struct dmabuf_info) +* +* Create a dma-buf for a plane +*/ +struct vfio_vgpu_dmabuf_info { +__u32 argsz; +__u32 flags; +struct vfio_vgpu_plane_info plane_info; +__s32 fd; +__u32 pad; +}; +#define VFIO_DEVICE_CREATE_DMABUF _IO(VFIO_TYPE, VFIO_BASE + 16) +/* -------- API for Type1 VFIO IOMMU -------- */ /**
Signature · 1 line
2.7.4
Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operations
include/uapi/linux/vfio.h struct vfio_pci_hot_reset { · line 552
Quoted 7 lines
include/uapi/linux/vfio.h +7
-0+struct vfio_vgpu_dmabuf_info { +__u32 argsz; +__u32 flags; +struct vfio_vgpu_plane_info plane_info; +__s32 fd; +__u32 pad; +};
Hmm, now you have argsz and flags twice in vfio_vgpu_dmabuf_info ...
I think we should have something like this:
struct vfio_vgpu_plane_info {
__u64 start;
__u64 drm_format_mod;
__u32 drm_format;
__u32 width;
__u32 height;
__u32 stride;
__u32 size;
__u32 x_pos;
__u32 y_pos;
__u32 padding;
};struct vfio_vgpu_query_plane {
__u32 argsz;
__u32 flags;
struct vfio_vgpu_plane_info plane_info;
__u32 plane_id;
__u32 padding;
};struct vfio_vgpu_create_dmabuf {
__u32 argsz;
__u32 flags;
struct vfio_vgpu_plane_info plane_info;
__u32 plane_id;
__s32 fd;
};_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
RE: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operations
Hi,
Quoted 44 lines
-----Original Message-----
From: Gerd Hoffmann [mailto:[email protected]]
Sent: Monday, May 29, 2017 3:20 PM
To: Chen, Xiaoguang <[email protected]>; [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operationsinclude/uapi/linux/vfio.h struct vfio_pci_hot_reset { · line 552
Quoted 7 lines
include/uapi/linux/vfio.h +7
-0+struct vfio_vgpu_dmabuf_info { +__u32 argsz; +__u32 flags; +struct vfio_vgpu_plane_info plane_info; +__s32 fd; +__u32 pad; +};Hmm, now you have argsz and flags twice in
vfio_vgpu_dmabuf_info...I think we should have something like this:
struct
vfio_vgpu_plane_info{
__u64 start;
__u64drm_format_mod;
__u32drm_format;
__u32 width;
__u32 height;
__u32 stride;
__u32 size;
__u32x_pos;__u32 y_pos; __u32 padding; };struct vfio_vgpu_query_plane { __u32 argsz; __u32 flags; struct vfio_vgpu_plane_info plane_info; __u32 plane_id; __u32 padding; };
Quoted 7 lines
struct vfio_vgpu_create_dmabuf {
__u32 argsz;
__u32 flags;
struct vfio_vgpu_plane_info plane_info;
__u32 plane_id;
__s32 fd;
};Good suggestion will apply in the next version.
Thanks for review :)
Chenxg.
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operations
Quoted 53 lines · Xiaoguang
Hi,
Quoted 44 lines
-----Original Message-----
From: Gerd Hoffmann [mailto:[email protected]]
Sent: Monday, May 29, 2017 3:20 PM
To: Chen, Xiaoguang <[email protected]>; [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operationsinclude/uapi/linux/vfio.h struct vfio_pci_hot_reset { · line 552
Quoted 7 lines
include/uapi/linux/vfio.h +7
-0+struct vfio_vgpu_dmabuf_info { +__u32 argsz; +__u32 flags; +struct vfio_vgpu_plane_info plane_info; +__s32 fd; +__u32 pad; +};Hmm, now you have argsz and flags twice in
vfio_vgpu_dmabuf_info...I think we should have something like this:
struct vfio_vgpu_plane_info { __u64 start; __u64 drm_format_mod; __u32 drm_format; __u32 width; __u32 height; __u32 stride; __u32 size; __u32 x_pos; __u32 y_pos; __u32 padding; };struct vfio_vgpu_query_plane { __u32 argsz; __u32 flags; struct vfio_vgpu_plane_info plane_info; __u32 plane_id; __u32 padding; };Quoted 7 lines
struct vfio_vgpu_create_dmabuf { __u32 argsz; __u32 flags; struct vfio_vgpu_plane_info plane_info; __u32 plane_id; __s32 fd; };
Quoted 3 lines
Good suggestion will apply in the next version.
Thanks for review :)
Can you define what are the expected values of 'flags' would be?
Thanks,
Kirti
Quoted 2 lines
Chenxg.
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
RE: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operations
Hi Kirti,
Quoted 68 lines
-----Original Message-----
From: Kirti Wankhede [mailto:[email protected]]
Sent: Thursday, June 01, 2017 1:23 AM
To: Chen, Xiaoguang <[email protected]>; Gerd Hoffmann <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operationsQuoted 54 lines · Xiaoguang
Hi,
Quoted 52 lines
-----Original Message-----
From: Gerd Hoffmann [mailto:[email protected]]
Sent: Monday, May 29, 2017 3:20 PM
To: Chen, Xiaoguang <[email protected]>; [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operationsinclude/uapi/linux/vfio.h struct vfio_pci_hot_reset { · line 552
Quoted 7 lines
include/uapi/linux/vfio.h +7
-0+struct vfio_vgpu_dmabuf_info { +__u32 argsz; +__u32 flags; +struct vfio_vgpu_plane_info plane_info; +__s32 fd; +__u32 pad; +};Hmm, now you have argsz and flags twice in
vfio_vgpu_dmabuf_info...I think we should have something like this:
struct vfio_vgpu_plane_info { __u64 start; __u64 drm_format_mod; __u32 drm_format; __u32 width; __u32 height; __u32 stride; __u32 size; __u32 x_pos; __u32 y_pos; __u32 padding; };struct vfio_vgpu_query_plane { __u32 argsz; __u32 flags; struct vfio_vgpu_plane_info plane_info; __u32 plane_id; __u32 padding; };struct vfio_vgpu_create_dmabuf { __u32 argsz; __u32 flags; struct vfio_vgpu_plane_info plane_info; __u32 plane_id; __s32 fd; };
Quoted 5 lines
Quoted 3 lines
Good suggestion will apply in the next version.
Thanks for review :)Can you define what are the expected values of 'flags' would be?
Flags is not used in this case. It is defined to follow the rules of vfio ioctls.
Quoted 6 lines
Thanks,
KirtiQuoted 2 lines
Chenxg.
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operations
Quoted 70 lines · Xiaoguang
Hi Kirti,
Quoted 68 lines
-----Original Message-----
From: Kirti Wankhede [mailto:[email protected]]
Sent: Thursday, June 01, 2017 1:23 AM
To: Chen, Xiaoguang <[email protected]>; Gerd Hoffmann <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operationsQuoted 54 lines · Xiaoguang
Hi,
Quoted 52 lines
-----Original Message-----
From: Gerd Hoffmann [mailto:[email protected]]
Sent: Monday, May 29, 2017 3:20 PM
To: Chen, Xiaoguang <[email protected]>; [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operationsinclude/uapi/linux/vfio.h struct vfio_pci_hot_reset { · line 552
Quoted 7 lines
include/uapi/linux/vfio.h +7
-0+struct vfio_vgpu_dmabuf_info { +__u32 argsz; +__u32 flags; +struct vfio_vgpu_plane_info plane_info; +__s32 fd; +__u32 pad; +};Hmm, now you have argsz and flags twice in
vfio_vgpu_dmabuf_info...I think we should have something like this:
struct vfio_vgpu_plane_info { __u64 start; __u64 drm_format_mod; __u32 drm_format; __u32 width; __u32 height; __u32 stride; __u32 size; __u32 x_pos; __u32 y_pos; __u32 padding; };struct vfio_vgpu_query_plane { __u32 argsz; __u32 flags; struct vfio_vgpu_plane_info plane_info; __u32 plane_id; __u32 padding; };struct vfio_vgpu_create_dmabuf { __u32 argsz; __u32 flags; struct vfio_vgpu_plane_info plane_info; __u32 plane_id; __s32 fd; };
Quoted 6 lines
Quoted 5 lines
Quoted 3 lines
Good suggestion will apply in the next version.
Thanks for review :)Can you define what are the expected values of 'flags' would be?
Flags is not used in this case. It is defined to follow the rules of vfio ioctls.
An important note about flags, the vendor driver must validate it. If they don't and the user passes an arbitrary value there, then we have a backwards compatibility issue with ever attempting to use the flags field. The user passing in a flag unknown to the vendor driver should return an -EINVAL response. In this case, we haven't defined any flags, so the vendor driver needs to force the user to pass zero. Thanks,
Alex
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operations
Quoted 78 lines · Alex Williamson
Quoted 75 lines · Xiaoguang
Hi Kirti,
Quoted 73 lines
-----Original Message-----
From: Kirti Wankhede [mailto:[email protected]]
Sent: Thursday, June 01, 2017 1:23 AM
To: Chen, Xiaoguang <[email protected]>; Gerd Hoffmann <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operationsQuoted 54 lines · Xiaoguang
Hi,
Quoted 45 lines
-----Original Message-----
From: Gerd Hoffmann [mailto:[email protected]]
Sent: Monday, May 29, 2017 3:20 PM
To: Chen, Xiaoguang <[email protected]>; [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operationsinclude/uapi/linux/vfio.h struct vfio_pci_hot_reset { · line 552
Quoted 7 lines
include/uapi/linux/vfio.h +7
-0+struct vfio_vgpu_dmabuf_info { +__u32 argsz; +__u32 flags; +struct vfio_vgpu_plane_info plane_info; +__s32 fd; +__u32 pad; +};Hmm, now you have argsz and flags twice in
vfio_vgpu_dmabuf_info...I think we should have something like this:
struct vfio_vgpu_plane_info { __u64 start; __u64 drm_format_mod; __u32 drm_format; __u32 width; __u32 height; __u32 stride; __u32 size; __u32 x_pos; __u32 y_pos; __u32 padding; };struct vfio_vgpu_query_plane { __u32 argsz; __u32 flags; struct vfio_vgpu_plane_info plane_info; __u32 plane_id; __u32 padding; };Quoted 7 lines
struct vfio_vgpu_create_dmabuf { __u32 argsz; __u32 flags; struct vfio_vgpu_plane_info plane_info; __u32 plane_id; __s32 fd; };Quoted 3 lines
Good suggestion will apply in the next version.
Thanks for review :)Can you define what are the expected values of 'flags' would be?
Quoted 8 lines
Quoted 1 line
Flags is not used in this case. It is defined to follow the rules of vfio ioctls.
An important note about flags, the vendor driver must validate it. If they don't and the user passes an arbitrary value there, then we have a backwards compatibility issue with ever attempting to use the flags field. The user passing in a flag unknown to the vendor driver should return an
-EINVALresponse. In this case, we haven't defined any flags, so the vendor driver needs to force the user to pass zero.
There are two ways QEMU can get surface for console:
1. adding a region using region capability
2. dmabuf
In both the above case surface parameters need to be queried from vendor driver are same. The structure would be :
struct vfio_vgpu_surface_info {
__u64 start;
__u32 width;
__u32 height;
__u32 stride;
__u32 size;
__u32 x_pos;
__u32 y_pos;
__u32 padding;
/* Only used when VFIO_VGPU_SURFACE_DMABUF_* flags set */
__u64 drm_format_mod;
__u32 drm_format;
};We can use one ioctl to query surface information from vendor driver, structure would look like:
struct vfio_vgpu_get_surface_info{
__u32 argsz;
__u32 flags;#define VFIO_VGPU_SURFACE_DMABUF_CREATE (1 << 0) /* Create dmabuf */
#define VFIO_VGPU_SURFACE_DMABUF_QUERY (1 << 1) /* Query surface info
for dmabuf */
#define VFIO_VGPU_SURFACE_REGION_QUERY (1 << 2) /* Query surface info
for REGION type */
struct vfio_vgpu_surface_info surface;
__u32 plane_id;
__s32 fd;
};#define VFIO_DEVICE_SURFACE_INFO _IO(VFIO_TYPE, VFIO_BASE + 15)
Vendor driver should return -EINVAL, if that type of query is not supported.
I would like to design this interface to support both type, region cap and dmabuf.
Thanks,
Kirti
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operations
Quoted 13 lines
struct
vfio_vgpu_surface_info{
__u64 start;
__u32 width;
__u32 height;
__u32 stride;
__u32 size;
__u32x_pos;
__u32y_pos;
__u32 padding;
/* Only used when VFIO_VGPU_SURFACE_DMABUF_* flags set */__u64drm_format_mod;
__u32drm_format;
Why for dmabufs only? Shouldn't the region specify the format too? Even in case you are using a fixed one (say DRM_FORMAT_XRGB8888) you can explicitly say so in drm_format (and set drm_format_mod to zero).
cheers,
Gerd
Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operations
Quoted 14 lines · Gerd Hoffmann
Quoted 13 lines
struct vfio_vgpu_surface_info { __u64 start; __u32 width; __u32 height; __u32 stride; __u32 size; __u32 x_pos; __u32 y_pos; __u32 padding; /* Only used when VFIO_VGPU_SURFACE_DMABUF_* flags set */ __u64 drm_format_mod; __u32 drm_format;
Quoted 4 lines
Why for dmabufs only? Shouldn't the region specify the format too? Even in case you are using a fixed one (say
DRM_FORMAT_XRGB8888) you can explicitly say so indrm_format(and setdrm_format_modto zero).
Definitions for PIXMAN formats and DRM formats are different. I think we need a flag to specify the format of surface that vendor driver is going to provide, PIXMAN or DRM.
If surface is provided through region in PIXMAN format, existing functions in QEMU can be used to get format from bpp value, qemu_default_pixman_format(). Similarly, display surface can be updated by QEMU using qemu_create_displaysurface_from() from mmaped region.
Thanks,
Kirti
Quoted 3 lines
cheers,
Gerd
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 4/6] vfio: Define vfio based vgpu's dma-buf operations
Quoted 24 lines · Kirti Wankhede
Quoted 14 lines · Gerd Hoffmann
Quoted 13 lines
struct
vfio_vgpu_surface_info{
__u64 start;
__u32 width;
__u32 height;
__u32 stride;
__u32 size;
__u32x_pos;
__u32y_pos;
__u32 padding;
/* Only used when VFIO_VGPU_SURFACE_DMABUF_* flags set */__u64drm_format_mod;
__u32drm_format;Quoted 7 lines
Why for dmabufs only? Shouldn't the region specify the format too?
Even in case you are using a fixed one (sayDRM_FORMAT_XRGB8888) you
can explicitly say so indrm_format(and setdrm_format_modto zero).
Quoted 3 lines
Definitions for PIXMAN formats and DRM formats are different. I think we need a flag to specify the format of surface that vendor driver is going to provide, PIXMAN or DRM.
No need to put that into the ioctl interface. First, the kernel should not worry about what userspace uses to process the data. Second (most) drm formats can trivially be mapped into pixman formats.
For example: PIXMAN_x8r8g8b8 (little endian) == DRM_FORMAT_XRGB8888
Quoted 5 lines
If surface is provided through region in PIXMAN format, existing functions in QEMU can be used to get format from bpp value,
qemu_default_pixman_format(). Similarly, display surface can be updated
by QEMU usingqemu_create_displaysurface_from()from mmaped region.
A thin wrapper which accepts a struct vfio_vgpu_surface_info and translates that into a qemu_create_displaysurface_from() call should be pretty small.
cheers,
Gerd
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v6 5/6 drm/i915/gvt: Dmabuf support for GVT-g
In reply to Xiaoguang Chendmabuf for GVT-g can be exported to users who can use the dmabuf to show the desktop of vm which use intel vgpu.
Currently we provide query and create new dmabuf operations.
Users of dmabuf can cache some created dmabufs and related information such as the framebuffer's address, size, tiling mode, width, height etc. When refresh the screen first query the currnet vgpu's frambuffer and compare with the cached ones(address, size, tiling, width, height etc) if found one then reuse the found dmabuf to gain performance improvment.
If there is no dmabuf created yet or not found in the cached dmabufs then need to create a new dmabuf. To create a dmabuf first a gem object will be created and the backing storage of this gem object is the vgpu's framebuffer(primary/cursor).
Set caching mode, change tiling mode and set domains of this gem object is not supported.
Then associate this gem object to a dmabuf and export this dmabuf. A file descriptor will be generated for this dmabuf and this file descriptor can be sent to user space to do display.
--- drivers/gpu/drm/i915/gvt/Makefile | 2 +- drivers/gpu/drm/i915/gvt/dmabuf.c | 269 +++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/gvt/dmabuf.h | 37 +++++ drivers/gpu/drm/i915/gvt/gvt.h | 1 + drivers/gpu/drm/i915/i915_gem.c | 26 +++- drivers/gpu/drm/i915/i915_gem_object.h | 9 ++ 6 files changed, 342 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/drm/i915/gvt/dmabuf.c create mode 100644 drivers/gpu/drm/i915/gvt/dmabuf.h
drivers/gpu/drm/i915/gvt/Makefile +1 -1
@@ -2,7 +2,7 @@ GVT_DIR := gvt GVT_SOURCE := gvt.o aperture_gm.o handlers.o vgpu.o trace_points.o firmware.o \ interrupt.o gtt.o cfg_space.o opregion.o mmio.o display.o edid.o \ execlist.o scheduler.o sched_policy.o render.o cmd_parser.o \ - fb_decoder.o + fb_decoder.o dmabuf.o ccflags-y += -I$(src) -I$(src)/$(GVT_DIR) -Wall i915-y += $(addprefix $(GVT_DIR)/, $(GVT_SOURCE))
drivers/gpu/drm/i915/gvt/dmabuf.c new file +269 -0
269 lines not on this page · raw message
drivers/gpu/drm/i915/gvt/dmabuf.h new file +37 -0
@@ -0,0 +1,37 @@ +/* +* Copyright(c) 2017 Intel Corporation. All rights reserved. +* +* Permission is hereby granted, free of charge, to any person obtaining a +* copy of this software and associated documentation files (the "Software"), +* to deal in the Software without restriction, including without limitation +* the rights to use, copy, modify, merge, publish, distribute, sublicense, +* and/or sell copies of the Software, and to permit persons to whom the +* Software is furnished to do so, subject to the following conditions: +* +* The above copyright notice and this permission notice (including the next +* paragraph) shall be included in all copies or substantial portions of the +* Software. +* +* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL +* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +* SOFTWARE. +* +*/ + +#ifndef _GVT_DMABUF_H_ +#define _GVT_DMABUF_H_ + +struct intel_vgpu_fb_info { +struct intel_vgpu *vgpu; +uint32_t fb_addr; +uint32_t fb_size; +}; + +int intel_vgpu_query_plane (struct intel_vgpu *vgpu,void *args); +int intel_vgpu_create_dmabuf (struct intel_vgpu *vgpu,void *args); + +#endif
drivers/gpu/drm/i915/gvt/gvt.h +1 -0
@@ -47,6 +47,7 @@#include "render.h" #include "cmd_parser.h" #include "fb_decoder.h" +#include "dmabuf.h" #define GVT_MAX_VGPU 8
drivers/gpu/drm/i915/i915_gem.c +25 -1
@@ -1609,6 +1609,12 @@ i915_gem_set_domain_ioctl(struct drm_device *dev, void *data,if (!obj)return -ENOENT ; +/* proxy gem object does not support setting domain */ +if (i915_gem_object_is_proxy (obj)) { +i915_gem_object_put (obj); +return -EPERM ; + } +/* Try to flush the object off the GPU without holding the lock. * We will repeat the flush holding the lock in the normal manner * to catch cases where we are gazumped.
@@ -1677,6 +1683,12 @@ i915_gem_sw_finish_ioctl(struct drm_device *dev, void *data,if (!obj)return -ENOENT ; +/* proxy gem obj does not support this operation */ +if (i915_gem_object_is_proxy (obj)) { +i915_gem_object_put (obj); +return -EPERM ; + } +/* Pinned buffers may be scanout, so flush the cache */ i915_gem_object_flush_if_display (obj);i915_gem_object_put (obj);
@@ -1727,7 +1739,7 @@ i915_gem_mmap_ioctl(struct drm_device *dev, void *data,*/ if (!obj->base.filp) {i915_gem_object_put (obj); -return -EINVAL ; +return -EPERM ; } addr = vm_mmap(obj->base.filp, 0, args->size,
@@ -3717,6 +3729,12 @@ int i915_gem_set_caching_ioctl(struct drm_device *dev, void *data,if (!obj)return -ENOENT ; +/* proxy gem obj does not support setting caching mode */ +if (i915_gem_object_is_proxy (obj)) { +i915_gem_object_put (obj); +return -EPERM ; + } +if (obj->cache_level == level) goto out;
@@ -4168,6 +4186,12 @@ i915_gem_madvise_ioctl(struct drm_device *dev, void *data,if (!obj)return -ENOENT ; +/* proxy gem obj does not support changing backding storage */ +if (i915_gem_object_is_proxy (obj)) { +i915_gem_object_put (obj); +return -EPERM ; + } + err =mutex_lock_interruptible (&obj->mm.lock);if (err) goto out;
drivers/gpu/drm/i915/i915_gem_object.h +9 -0
@@ -39,6 +39,7 @@ struct drm_i915_gem_object_ops {unsigned int flags;#define I915_GEM_OBJECT_HAS_STRUCT_PAGE 0x1#define I915_GEM_OBJECT_IS_SHRINKABLE 0x2 +#define I915_GEM_OBJECT_IS_PROXY 0x4/* Interface between the GEM object and its backing storage. * get_pages() is called once prior to the use of the associated set
@@ -184,6 +185,8 @@ struct drm_i915_gem_object { } userptr;unsigned long scratch; + +void *gvt_info; };/** for phys allocated objects */
@@ -286,6 +289,12 @@ i915_gem_object_is_shrinkable(const struct drm_i915_gem_object *obj) }static inline bool +i915_gem_object_is_proxy (const struct drm_i915_gem_object *obj) +{ +return obj->ops->flags &I915_GEM_OBJECT_IS_PROXY ; +} + +static inline bool i915_gem_object_is_active (const struct drm_i915_gem_object *obj) {return obj->active_count;
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 5/6] drm/i915/gvt: Dmabuf support for GVT-g
Quoted 1 line · Xiaoguang Chen
+ if (
plane_id==PLANE_PRIMARY) {
Should be DRM_PLANE_TYPE_PRIMARY (likewise for the cursor).
_______________________________________________
Intel-gfx mailing list [email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
RE: [PATCH v6 5/6] drm/i915/gvt: Dmabuf support for GVT-g
Hi Gerd,
Quoted 12 lines
-----Original Message-----
From: intel-gvt-dev [mailto:[email protected]] On Behalf Of Gerd Hoffmann
Sent: Wednesday, May 31, 2017 8:05 PM
To: Chen, Xiaoguang <[email protected]>; [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 5/6] drm/i915/gvt: Dmabuf support for GVT-g
Quoted 4 lines
Quoted 1 line · Xiaoguang Chen
+ if (
plane_id==PLANE_PRIMARY) {Should be
DRM_PLANE_TYPE_PRIMARY(likewise for the cursor).
OK. I will change in the next version.
Quoted 4 lines
_______________________________________________
intel-gvt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 5/6] drm/i915/gvt: Dmabuf support for GVT-g
In reply to Xiaoguang ChenQuoted 98 lines · Xiaoguang Chen
dmabuf for GVT-g can be exported to users who can use the dmabuf to show the desktop of vm which use intel vgpu.
Currently we provide query and create new dmabuf operations.
Users of dmabuf can cache some created dmabufs and related information such as the framebuffer's address, size, tiling mode, width, height etc. When refresh the screen first query the currnet vgpu's frambuffer and compare with the cached
ones(address, size, tiling, width, height etc)if found one then reuse the found dmabuf to gain performance improvment.If there is no dmabuf created yet or not found in the cached dmabufs then need to create a new dmabuf. To create a dmabuf first a gem object will be created and the backing storage of this gem object is the vgpu's framebuffer(primary/cursor).
Set caching mode, change tiling mode and set domains of this gem object is not supported.
Then associate this gem object to a dmabuf and export this dmabuf. A file descriptor will be generated for this dmabuf and this file descriptor can be sent to user space to do display.Signed-off-by Xiaoguang Chen <[email protected]>--- drivers/gpu/drm/i915/gvt/Makefile | 2 +- drivers/gpu/drm/i915/gvt/dmabuf.c | 269 +++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/gvt/dmabuf.h | 37 +++++ drivers/gpu/drm/i915/gvt/gvt.h | 1 + drivers/gpu/drm/i915/i915_gem.c | 26 +++- drivers/gpu/drm/i915/i915_gem_object.h | 9 ++ 6 files changed, 342 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/drm/i915/gvt/dmabuf.c create mode 100644 drivers/gpu/drm/i915/gvt/dmabuf.hdrivers/gpu/drm/i915/gvt/Makefile +1
-1@@ -2,7 +2,7 @@ GVT_DIR := gvt GVT_SOURCE := gvt.o aperture_gm.o handlers.o vgpu.o trace_points.o firmware.o \ interrupt.o gtt.o cfg_space.o opregion.o mmio.o display.o edid.o \ execlist.o scheduler.o sched_policy.o render.o cmd_parser.o \ - fb_decoder.o + fb_decoder.o dmabuf.o ccflags-y += -I$(src) -I$(src)/$(GVT_DIR) -Wall i915-y += $(addprefix $(GVT_DIR)/, $(GVT_SOURCE))drivers/gpu/drm/i915/gvt/dmabuf.c new file +46
-0@@ -0,0 +1,269 @@ +/* +* Copyright 2017 Intel Corporation. All rights reserved. +* +* Permission is hereby granted, free of charge, to any person obtaining a +* copy of this software and associated documentation files (the "Software"), +* to deal in the Software without restriction, including without limitation +* the rights to use, copy, modify, merge, publish, distribute, sublicense, +* and/or sell copies of the Software, and to permit persons to whom the +* Software is furnished to do so, subject to the following conditions: +* +* The above copyright notice and this permission notice (including the next +* paragraph) shall be included in all copies or substantial portions of the +* Software. +* +* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL +* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING +* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER +* DEALINGS IN THE SOFTWARE. +* +* Authors: +* Zhiyuan Lv <[email protected]> +* +* Contributors: +* Xiaoguang Chen <[email protected]> +*/ + +#include <linux/dma-buf.h> +#include <drm/drmP.h> +#include <linux/vfio.h> + +#include "i915_drv.h" +#include "gvt.h" + +#define GEN8_DECODE_PTE (pte) (pte & GENMASK_ULL(63, 12)) + +static struct sg_table *intel_vgpu_gem_get_pages ( +struct drm_i915_gem_object *obj) +{ +struct drm_i915_private *dev_priv =to_i915 (obj->base.dev); +struct sg_table *st; +struct scatterlist *sg; +int i, ret; +gen8_pte_t __iomem *gtt_entries;
drivers/gpu/drm/i915/gvt/dmabuf.c line 56
Quoted 10 lines
drivers/gpu/drm/i915/gvt/dmabuf.c new file +10
-0+struct intel_vgpu_fb_info *fb_info; + + fb_info = (struct intel_vgpu_fb_info *)obj->gvt_info; +if (WARN_ON (!fb_info)) +return ERR_PTR (-ENODEV ); + + st =kmalloc (sizeof (*st),GFP_KERNEL ); +if (!st) { + ret = -ENOMEM ; +return ERR_PTR (ret);
Tidier.
Quoted 45 lines
drivers/gpu/drm/i915/gvt/dmabuf.c new file +45
-0+ } + + ret =sg_alloc_table (st, fb_info->fb_size,GFP_KERNEL ); +if (ret) { +kfree (st); +return ERR_PTR (ret); + } + gtt_entries = (gen8_pte_t __iomem *)dev_priv->ggtt.gsm + + (fb_info->fb_addr >>PAGE_SHIFT ); +for_each_sg (st->sgl, sg, fb_info->fb_size, i) { + sg->offset =0 ; + sg->length =PAGE_SIZE ; +sg_dma_address (sg) = +GEN8_DECODE_PTE (readq (>t_entries[i])); +sg_dma_len (sg) =PAGE_SIZE ; + } + +return st; +} + +static void intel_vgpu_gem_put_pages (struct drm_i915_gem_object *obj, +struct sg_table *pages) +{ +sg_free_table (pages); +kfree (pages); +} + +static const struct drm_i915_gem_object_ops intel_vgpu_gem_ops = { + .flags =I915_GEM_OBJECT_IS_PROXY , + .get_pages = intel_vgpu_gem_get_pages, + .put_pages = intel_vgpu_gem_put_pages, +}; + +static struct drm_i915_gem_object *intel_vgpu_create_gem (struct drm_device *dev, +struct vfio_vgpu_plane_info *info) +{ +struct drm_i915_private *dev_priv =to_i915 (dev); +struct drm_i915_gem_object *obj; + + obj =i915_gem_object_alloc (dev_priv); +if (obj ==NULL ) +return NULL ; + +drm_gem_private_object_init (dev, &obj->base, + info->size <<PAGE_SHIFT );
drivers/gpu/drm/i915/gvt/dmabuf.c line 111
Quoted 10 lines
drivers/gpu/drm/i915/gvt/dmabuf.c new file +10
-0+i915_gem_object_init (obj, &intel_vgpu_gem_ops); + + obj->base.read_domains =I915_GEM_DOMAIN_GTT ; + obj->base.write_domain =0 ; +/* Change tiling mode from user space is not supported to a GVT-g's +* dma-buf gem object. +* We increase the obj's framebuffer_references to disable this kind +* of operation. +*/ + obj->framebuffer_references++;
If it is only for that, don't. Just use the is_proxy: return -EPERM. So that you don't make the mistake of leaving the counter dangling and the error code is consistent.
What you probably should consider though is setting obj->pin_display. That will fix up coherency along a few more paths.
Quoted 62 lines
drivers/gpu/drm/i915/gvt/dmabuf.c new file +61
-0+if (IS_SKYLAKE (dev_priv)) { +unsigned int tiling_mode =0 ; +unsigned int stride =0 ; + +switch (info->drm_format_mod <<10 ) { +case PLANE_CTL_TILED_LINEAR : + tiling_mode =I915_TILING_NONE ; +break ; +case PLANE_CTL_TILED_X : + tiling_mode =I915_TILING_X ; + stride = info->stride; +break ; +case PLANE_CTL_TILED_Y : + tiling_mode =I915_TILING_Y ; + stride = info->stride; +break ; +default : +gvt_dbg_core ("not supported tiling mode\n" ); + } + obj->tiling_and_stride = tiling_mode | stride; + }else { + obj->tiling_and_stride = info->drm_format_mod ? +I915_TILING_X :0 ; + } + +return obj; +} + +int intel_vgpu_query_plane (struct intel_vgpu *vgpu,void *args) +{ +struct drm_device *dev = &vgpu->gvt->dev_priv->drm; +struct vfio_vgpu_plane_info *info = args; + +return intel_vgpu_get_plane_info (dev, vgpu, info); +} + +int intel_vgpu_create_dmabuf (struct intel_vgpu *vgpu,void *args) +{ +struct dma_buf *dmabuf; +struct drm_i915_gem_object *obj; +struct drm_device *dev = &vgpu->gvt->dev_priv->drm; +struct vfio_vgpu_dmabuf_info *gvt_dmabuf = args; +struct intel_vgpu_fb_info *fb_info; +int ret; + + ret =intel_vgpu_get_plane_info (dev, vgpu, &gvt_dmabuf->plane_info); +if (ret !=0 ) +return ret; + + obj =intel_vgpu_create_gem (dev, &gvt_dmabuf->plane_info); +if (obj ==NULL ) { +gvt_vgpu_err ("create gvt gem obj failed:%d\n" , vgpu->id); +return -ENOMEM ; + } + fb_info =kmalloc (sizeof (*fb_info),GFP_KERNEL ); +if (!fb_info) { +i915_gem_object_put (obj); +gvt_vgpu_err ("allocate intel vgpu fb info failed\n" ); +return -ENOMEM ; + } + fb_info->fb_addr = gvt_dmabuf->plane_info.start;
drivers/gpu/drm/i915/gvt/dmabuf.c line 255
Quoted 10 lines
drivers/gpu/drm/i915/gvt/dmabuf.c new file +10
-0+ fb_info->fb_size = gvt_dmabuf->plane_info.size; + fb_info->vgpu = vgpu; + obj->gvt_info = fb_info; + + dmabuf =i915_gem_prime_export (dev, &obj->base,DRM_CLOEXEC |DRM_RDWR ); + +if (IS_ERR (dmabuf)) { +kfree (fb_info); +i915_gem_object_free (obj); +gvt_vgpu_err ("export dma-buf failed\n" );
Develop a habit for using onion unwind for errors.
Quoted 19 lines
drivers/gpu/drm/i915/gvt/dmabuf.c new file +14
-0+return PTR_ERR (dmabuf); + } + + ret =dma_buf_fd (dmabuf,DRM_CLOEXEC |DRM_RDWR ); +if (ret <0 ) { +kfree (fb_info); +i915_gem_object_free (obj); +gvt_vgpu_err ("create dma-buf fd failed ret:%d\n" , ret); +return ret; + } + gvt_dmabuf->fd = ret; + +return 0 ; +}drivers/gpu/drm/i915/i915_gem.c +0
-0
drivers/gpu/drm/i915/i915_gem.c i915_gem_set_domain_ioctl(struct drm_device *dev, void *data, · line 1615
Quoted 7 lines
drivers/gpu/drm/i915/i915_gem.c +4
-0@@ -1609,6 +1609,12 @@ i915_gem_set_domain_ioctl(struct drm_device *dev, void *data,if (!obj)return -ENOENT ; +/* proxy gem object does not support setting domain */ +if (i915_gem_object_is_proxy (obj)) { +i915_gem_object_put (obj); +return -EPERM ;
Hook into the onion.
Quoted 28 lines
drivers/gpu/drm/i915/i915_gem.c +9
-1+ } +/* Try to flush the object off the GPU without holding the lock. * We will repeat the flush holding the lock in the normal manner * to catch cases where we are gazumped. @@ -1677,6 +1683,12 @@ i915_gem_sw_finish_ioctl(struct drm_device *dev, void *data,if (!obj)return -ENOENT ; +/* proxy gem obj does not support this operation */ +if (i915_gem_object_is_proxy (obj)) { +i915_gem_object_put (obj); +return -EPERM ; + } +/* Pinned buffers may be scanout, so flush the cache */ i915_gem_object_flush_if_display (obj);i915_gem_object_put (obj);@@ -1727,7 +1739,7 @@ i915_gem_mmap_ioctl(struct drm_device *dev, void *data,*/ if (!obj->base.filp) {i915_gem_object_put (obj); -return -EINVAL ; +return -EPERM ; } addr = vm_mmap(obj->base.filp, 0, args->size,
drivers/gpu/drm/i915/i915_gem.c int i915_gem_set_caching_ioctl(struct drm_device *dev, void *data, · line 3735
Quoted 7 lines
drivers/gpu/drm/i915/i915_gem.c +4
-0@@ -3717,6 +3729,12 @@ int i915_gem_set_caching_ioctl(struct drm_device *dev, void *data,if (!obj)return -ENOENT ; +/* proxy gem obj does not support setting caching mode */ +if (i915_gem_object_is_proxy (obj)) { +i915_gem_object_put (obj); +return -EPERM ;
Use the onion.
drivers/gpu/drm/i915/i915_gem.c i915_gem_madvise_ioctl(struct drm_device *dev, void *data, · line 4191
Quoted 12 lines
drivers/gpu/drm/i915/i915_gem.c +5
-0+ } +if (obj->cache_level == level) goto out;@@ -4168,6 +4186,12 @@ i915_gem_madvise_ioctl(struct drm_device *dev, void *data,if (!obj)return -ENOENT ; +/* proxy gem obj does not support changing backding storage */ +if (i915_gem_object_is_proxy (obj)) { +i915_gem_object_put (obj);
More onion.
Quoted 6 lines
drivers/gpu/drm/i915/i915_gem.c +3
-0+return -EPERM ; + } + err =mutex_lock_interruptible (&obj->mm.lock);if (err) goto out;
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v6 6/6 drm/i915/gvt: Adding interface so user space can get the dma-buf
In reply to Xiaoguang ChenUser space should create the management fd for the dma-buf operation first. Then user can query the plane information and create dma-buf if necessary using the management fd.
--- drivers/gpu/drm/i915/gvt/dmabuf.c | 12 ++++ drivers/gpu/drm/i915/gvt/dmabuf.h | 5 ++ drivers/gpu/drm/i915/gvt/gvt.c | 2 + drivers/gpu/drm/i915/gvt/gvt.h | 5 ++ drivers/gpu/drm/i915/gvt/kvmgt.c | 144 ++++++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/gvt/vgpu.c | 1 + 6 files changed, 169 insertions(+)
drivers/gpu/drm/i915/gvt/dmabuf.c +12 -0
@@ -226,6 +226,7 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu, void *args)struct vfio_vgpu_dmabuf_info *gvt_dmabuf = args;struct intel_vgpu_fb_info *fb_info;int ret; +struct intel_vgpu_dmabuf_obj *dmabuf_obj; ret =intel_vgpu_get_plane_info (dev, vgpu, &gvt_dmabuf->plane_info);if (ret !=0 )
@@ -263,6 +264,17 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu, void *args)gvt_vgpu_err ("create dma-buf fd failed ret:%d\n" , ret);return ret; } + dmabuf_obj =kmalloc (sizeof (*dmabuf_obj),GFP_KERNEL ); +if (dmabuf_obj ==NULL ) { +kfree (fb_info); +i915_gem_object_put (obj); +gvt_vgpu_err ("alloc dmabuf_obj failed\n" ); +return -ENOMEM ; + } + dmabuf_obj->obj = obj; +INIT_LIST_HEAD (&dmabuf_obj->list); +list_add_tail (&dmabuf_obj->list, &vgpu->dmabuf_obj_list_head); + gvt_dmabuf->fd = ret;return 0 ;
drivers/gpu/drm/i915/gvt/dmabuf.h +5 -0
@@ -31,6 +31,11 @@ struct intel_vgpu_fb_info {uint32_t fb_size; }; +struct intel_vgpu_dmabuf_obj { +struct drm_i915_gem_object *obj; +struct list_head list; +}; +int intel_vgpu_query_plane (struct intel_vgpu *vgpu,void *args);int intel_vgpu_create_dmabuf (struct intel_vgpu *vgpu,void *args);
drivers/gpu/drm/i915/gvt/gvt.c +2 -0
@@ -54,6 +54,8 @@ static const struct intel_gvt_ops intel_gvt_ops = { .vgpu_reset = intel_gvt_reset_vgpu, .vgpu_activate = intel_gvt_activate_vgpu, .vgpu_deactivate = intel_gvt_deactivate_vgpu, + .vgpu_query_plane = intel_vgpu_query_plane, + .vgpu_create_dmabuf = intel_vgpu_create_dmabuf, };/**
drivers/gpu/drm/i915/gvt/gvt.h +5 -0
@@ -185,8 +185,11 @@ struct intel_vgpu {struct kvm *kvm;struct work_struct release_work;atomic_t released; +struct vfio_device *vfio_device; } vdev;#endif +int dmabuf_mgr_fd; +struct list_head dmabuf_obj_list_head; }; struct intel_gvt_gm {
@@ -467,6 +470,8 @@ struct intel_gvt_ops {void (*vgpu_reset)(struct intel_vgpu *);void (*vgpu_activate)(struct intel_vgpu *);void (*vgpu_deactivate)(struct intel_vgpu *); +int (*vgpu_query_plane)(struct intel_vgpu *vgpu,void *); +int (*vgpu_create_dmabuf)(struct intel_vgpu *vgpu,void *); };
drivers/gpu/drm/i915/gvt/kvmgt.c +144 -0
162 lines not on this page · raw message
drivers/gpu/drm/i915/gvt/vgpu.c +1 -0
@@ -346,6 +346,7 @@ static struct intel_vgpu *__intel_gvt_create_vgpu(struct intel_gvt *gvt, vgpu->gvt = gvt; vgpu->sched_ctl.weight = param->weight;bitmap_zero (vgpu->tlb_handle_pending,I915_NUM_ENGINES ); +INIT_LIST_HEAD (&vgpu->dmabuf_obj_list_head);intel_vgpu_init_cfg_space (vgpu, param->primary);
Signature · 6 lines
2.7.4 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-buf
Quoted 145 lines · On Sat, 27 May 2017 16:38:52 +0800 Xiaoguang Chen <[email protected]>…
User space should create the management fd for the dma-buf operation first. Then user can query the plane information and create dma-buf if necessary using the management fd.
Signed-off-by Xiaoguang Chen <[email protected]>--- drivers/gpu/drm/i915/gvt/dmabuf.c | 12 ++++ drivers/gpu/drm/i915/gvt/dmabuf.h | 5 ++ drivers/gpu/drm/i915/gvt/gvt.c | 2 + drivers/gpu/drm/i915/gvt/gvt.h | 5 ++ drivers/gpu/drm/i915/gvt/kvmgt.c | 144 ++++++++++++++++++++++++++++++++++++++ drivers/gpu/drm/i915/gvt/vgpu.c | 1 + 6 files changed, 169 insertions(+)drivers/gpu/drm/i915/gvt/dmabuf.c +12
-0@@ -226,6 +226,7 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu, void *args)struct vfio_vgpu_dmabuf_info *gvt_dmabuf = args;struct intel_vgpu_fb_info *fb_info;int ret; +struct intel_vgpu_dmabuf_obj *dmabuf_obj; ret =intel_vgpu_get_plane_info (dev, vgpu, &gvt_dmabuf->plane_info);if (ret !=0 )@@ -263,6 +264,17 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu, void *args)gvt_vgpu_err ("create dma-buf fd failed ret:%d\n" , ret);return ret; } + dmabuf_obj =kmalloc (sizeof (*dmabuf_obj),GFP_KERNEL ); +if (dmabuf_obj ==NULL ) { +kfree (fb_info); +i915_gem_object_put (obj); +gvt_vgpu_err ("alloc dmabuf_obj failed\n" ); +return -ENOMEM ; + } + dmabuf_obj->obj = obj; +INIT_LIST_HEAD (&dmabuf_obj->list); +list_add_tail (&dmabuf_obj->list, &vgpu->dmabuf_obj_list_head); + gvt_dmabuf->fd = ret;return 0 ;drivers/gpu/drm/i915/gvt/dmabuf.h +5
-0@@ -31,6 +31,11 @@ struct intel_vgpu_fb_info {uint32_t fb_size; }; +struct intel_vgpu_dmabuf_obj { +struct drm_i915_gem_object *obj; +struct list_head list; +}; +int intel_vgpu_query_plane (struct intel_vgpu *vgpu,void *args);int intel_vgpu_create_dmabuf (struct intel_vgpu *vgpu,void *args);drivers/gpu/drm/i915/gvt/gvt.c +2
-0@@ -54,6 +54,8 @@ static const struct intel_gvt_ops intel_gvt_ops = { .vgpu_reset = intel_gvt_reset_vgpu, .vgpu_activate = intel_gvt_activate_vgpu, .vgpu_deactivate = intel_gvt_deactivate_vgpu, + .vgpu_query_plane = intel_vgpu_query_plane, + .vgpu_create_dmabuf = intel_vgpu_create_dmabuf, };/** drivers/gpu/drm/i915/gvt/gvt.h +5
-0@@ -185,8 +185,11 @@ struct intel_vgpu {struct kvm *kvm;struct work_struct release_work;atomic_t released; +struct vfio_device *vfio_device; } vdev;#endif +int dmabuf_mgr_fd; +struct list_head dmabuf_obj_list_head; }; struct intel_gvt_gm {@@ -467,6 +470,8 @@ struct intel_gvt_ops {void (*vgpu_reset)(struct intel_vgpu *);void (*vgpu_activate)(struct intel_vgpu *);void (*vgpu_deactivate)(struct intel_vgpu *); +int (*vgpu_query_plane)(struct intel_vgpu *vgpu,void *); +int (*vgpu_create_dmabuf)(struct intel_vgpu *vgpu,void *); };drivers/gpu/drm/i915/gvt/kvmgt.c +32
-0@@ -41,6 +41,7 @@#include <linux/kvm_host.h> #include <linux/vfio.h> #include <linux/mdev.h> +#include <linux/anon_inodes.h> #include "i915_drv.h" #include "gvt.h" @@ -524,6 +525,125 @@ static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu)return ret; } +static int kvmgt_get_vfio_device (struct intel_vgpu *vgpu) +{ +struct vfio_device *device; + + device =vfio_device_get_from_dev (mdev_dev (vgpu->vdev.mdev)); +if (device ==NULL ) +return -ENODEV ; + vgpu->vdev.vfio_device = device; + +return 0 ; +} + +static void kvmgt_put_vfio_device (struct intel_vgpu *vgpu) +{ +vfio_device_put (vgpu->vdev.vfio_device); +} + +static int intel_vgpu_dmabuf_mgr_fd_mmap (struct file *file, +struct vm_area_struct *vma) +{ +return -EPERM ; +} + +static int intel_vgpu_dmabuf_mgr_fd_release (struct inode *inode, +struct file *filp) +{ +struct intel_vgpu *vgpu = filp->private_data; +struct intel_vgpu_dmabuf_obj *obj; +struct list_head *pos; + +if (WARN_ON (!vgpu->vdev.vfio_device))
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 568
Quoted 10 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +10
-0+return -ENODEV ; + +list_for_each (pos, &vgpu->dmabuf_obj_list_head) { + obj = container_of(pos, struct intel_vgpu_dmabuf_obj, list); +if (WARN_ON (!obj)) +return -ENODEV ; +kfree (obj->obj->gvt_info); +i915_gem_object_put (obj->obj); +kfree (obj); +kvmgt_put_vfio_device (vgpu);
Can we do this? If I understand, we're releasing all the references and allocations for the dmabuf fds on release of the manager fd. What happens if the user continues trying to access those dmabuf fds after this?
Quoted 44 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +44
-0+ } +kvmgt_put_vfio_device (vgpu); + +return 0 ; +} + +static long intel_vgpu_dmabuf_mgr_fd_ioctl (struct file *filp, +unsigned int ioctl,unsigned long arg) +{ +struct intel_vgpu *vgpu = filp->private_data; +int minsz; +int ret; +struct fd f; + + f =fdget (vgpu->dmabuf_mgr_fd); +if (!f.file) +return -EBADF ; + +if (ioctl ==VFIO_DEVICE_QUERY_PLANE ) { +struct vfio_vgpu_plane_info info; + + minsz = offsetofend(struct vfio_vgpu_plane_info, resv); +if (copy_from_user (&info, (void __user *)arg, minsz)) { +fdput (f); +return -EFAULT ; + } +if (info.argsz < minsz) { +fdput (f); +return -EINVAL ; + } + ret = intel_gvt_ops->vgpu_query_plane (vgpu, &info); +if (ret !=0 ) { +fdput (f); +gvt_vgpu_err ("query plane failed:%d\n" , ret); +return -EINVAL ; + } +fdput (f); +return copy_to_user ((void __user *)arg, &info, minsz) ? + -EFAULT :0 ; + }else if (ioctl ==VFIO_DEVICE_CREATE_DMABUF ) { +struct vfio_vgpu_dmabuf_info dmabuf; + + minsz = offsetofend(struct vfio_vgpu_dmabuf_info, resv); +if (copy_from_user (&dmabuf, (void __user *)arg, minsz)) {
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 622
Quoted 10 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +10
-0+fdput (f); +return -EFAULT ; + } +if (dmabuf.argsz < minsz) { +fdput (f); +return -EINVAL ; + } + ret =kvmgt_get_vfio_device (vgpu); +if (ret !=0 ) +return ret;
Missed an fdput, though I'm not sure I understand the value of the original fdget or the dmabuf_mgr_fd field at all. dmabuf_mgr_fd is only used here, presumably to add a reference to the fd while we're in the ioctl, but we're in the ioctl function of that fd, so I think there are already references elsewhere.
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 628
Quoted 6 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +6
-0+ + ret = intel_gvt_ops->vgpu_create_dmabuf (vgpu, &dmabuf); +if (ret !=0 ) { +kvmgt_put_vfio_device (vgpu); +fdput (f); +return -EINVAL ;
Why not return the errno that vgpu_create_dmabuf provided?
Quoted 35 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +28
-0+ } +fdput (f); +return copy_to_user ((void __user *)arg, &dmabuf, minsz) ? + -EFAULT :0 ; + } + +fdput (f); +gvt_vgpu_err ("unsupported dmabuf operation\n" ); + +return -EINVAL ; +} + +static const struct file_operations intel_vgpu_dmabuf_mgr_fd_ops = { + .release = intel_vgpu_dmabuf_mgr_fd_release, + .unlocked_ioctl = intel_vgpu_dmabuf_mgr_fd_ioctl, + .mmap = intel_vgpu_dmabuf_mgr_fd_mmap, + .llseek = noop_llseek, +};static int intel_vgpu_create (struct kobject *kobj,struct mdev_device *mdev) {struct intel_vgpu *vgpu =NULL ;@@ -1259,6 +1379,30 @@ static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, }else if (cmd ==VFIO_DEVICE_RESET ) { intel_gvt_ops->vgpu_reset (vgpu);return 0 ; + }else if (cmd ==VFIO_DEVICE_GET_FD ) { +int fd; +u32 type; +int ret; + +if (copy_from_user (&type, (void __user *)arg,sizeof (type))) +return -EINVAL ; +if (type !=VFIO_DEVICE_DMABUF_MGR_FD ) +return -EINVAL ; +
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, · line 1401
Quoted 10 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +10
-0+ ret =kvmgt_get_vfio_device (vgpu); +if (ret !=0 ) +return ret; + + fd =anon_inode_getfd ("intel-vgpu-dmabuf-mgr-fd" , + &intel_vgpu_dmabuf_mgr_fd_ops, + vgpu,O_RDWR |O_CLOEXEC ); +if (fd <0 ) { +gvt_vgpu_err ("create dmabuf mgr fd failed\n" ); +return -EINVAL ;
Error path leaks vfio_device reference.
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, · line 1403
Quoted 2 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +2
-0+ } + vgpu->dmabuf_mgr_fd = fd;
As above, unclear value of this field, additionally, what if the user calls VFIO_DEVICE_GET_FD more than once?
Quoted 10 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +2
-0+ +return fd; }return 0 ;drivers/gpu/drm/i915/gvt/vgpu.c +0
-0
drivers/gpu/drm/i915/gvt/vgpu.c static struct intel_vgpu *__intel_gvt_create_vgpu(struct intel_gvt *gvt, · line 352
Quoted 7 lines
drivers/gpu/drm/i915/gvt/vgpu.c +1
-0@@ -346,6 +346,7 @@ static struct intel_vgpu *__intel_gvt_create_vgpu(struct intel_gvt *gvt, vgpu->gvt = gvt; vgpu->sched_ctl.weight = param->weight;bitmap_zero (vgpu->tlb_handle_pending,I915_NUM_ENGINES ); +INIT_LIST_HEAD (&vgpu->dmabuf_obj_list_head);intel_vgpu_init_cfg_space (vgpu, param->primary);
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
RE: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-buf
Hi Alex,
Quoted 171 lines
-----Original Message-----
From: Alex Williamson [mailto:[email protected]]
Sent: Friday, June 02, 2017 2:08 AM
To: Chen, Xiaoguang <[email protected]>
Cc: [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-bufQuoted 11 lines · On Sat, 27 May 2017 16:38:52 +0800 Xiaoguang Chen <[email protected]>…
User space should create the management fd for the dma-buf operation first. Then user can query the plane information and create dma-buf if necessary using the management fd.
Signed-off-by Xiaoguang Chen <[email protected]>--- drivers/gpu/drm/i915/gvt/dmabuf.c | 12 ++++ drivers/gpu/drm/i915/gvt/dmabuf.h | 5 ++ drivers/gpu/drm/i915/gvt/gvt.c | 2 + drivers/gpu/drm/i915/gvt/gvt.h | 5 ++ drivers/gpu/drm/i915/gvt/kvmgt.c | 144++++++++++++++++++++++++++++++++++++++
drivers/gpu/drm/i915/gvt/dmabuf.c int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,
Quoted 9 lines
drivers/gpu/drm/i915/gvt/vgpu.c | 1 + 6 files changed, 169 insertions(+)drivers/gpu/drm/i915/gvt/dmabuf.c +0
-0@@ -226,6 +226,7 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,void *args)
drivers/gpu/drm/i915/gvt/dmabuf.c int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,
Quoted 8 lines
drivers/gpu/drm/i915/gvt/dmabuf.c +1
-0struct vfio_vgpu_dmabuf_info *gvt_dmabuf = args;struct intel_vgpu_fb_info *fb_info;int ret; +struct intel_vgpu_dmabuf_obj *dmabuf_obj; ret =intel_vgpu_get_plane_info (dev, vgpu, &gvt_dmabuf->plane_info);if (ret !=0 )@@ -263,6 +264,17 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,void *args)
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct
Quoted 86 lines
drivers/gpu/drm/i915/gvt/dmabuf.c +11
-0gvt_vgpu_err ("create dma-buf fd failed ret:%d\n" , ret);return ret; } + dmabuf_obj =kmalloc (sizeof (*dmabuf_obj),GFP_KERNEL ); +if (dmabuf_obj ==NULL ) { +kfree (fb_info); +i915_gem_object_put (obj); +gvt_vgpu_err ("alloc dmabuf_obj failed\n" ); +return -ENOMEM ; + } + dmabuf_obj->obj = obj; +INIT_LIST_HEAD (&dmabuf_obj->list); +list_add_tail (&dmabuf_obj->list, &vgpu->dmabuf_obj_list_head); + gvt_dmabuf->fd = ret;return 0 ;drivers/gpu/drm/i915/gvt/dmabuf.h +5
-0@@ -31,6 +31,11 @@ struct intel_vgpu_fb_info {uint32_t fb_size; }; +struct intel_vgpu_dmabuf_obj { +struct drm_i915_gem_object *obj; +struct list_head list; +}; +int intel_vgpu_query_plane (struct intel_vgpu *vgpu,void *args);int intel_vgpu_create_dmabuf (struct intel_vgpu *vgpu,void *args);(quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/gvt.cindex 2032917..dbc3f86 100644drivers/gpu/drm/i915/gvt/gvt.c +2
-0@@ -54,6 +54,8 @@ static const struct intel_gvt_ops intel_gvt_ops = { .vgpu_reset = intel_gvt_reset_vgpu, .vgpu_activate = intel_gvt_activate_vgpu, .vgpu_deactivate = intel_gvt_deactivate_vgpu, + .vgpu_query_plane = intel_vgpu_query_plane, + .vgpu_create_dmabuf = intel_vgpu_create_dmabuf, };/** (quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/gvt.hindex 763a8c5..a855797 100644drivers/gpu/drm/i915/gvt/gvt.h +5
-0@@ -185,8 +185,11 @@ struct intel_vgpu {struct kvm *kvm;struct work_struct release_work;atomic_t released; +struct vfio_device *vfio_device; } vdev;#endif +int dmabuf_mgr_fd; +struct list_head dmabuf_obj_list_head; }; struct intel_gvt_gm {@@ -467,6 +470,8 @@ struct intel_gvt_ops {void (*vgpu_reset)(struct intel_vgpu *);void (*vgpu_activate)(struct intel_vgpu *);void (*vgpu_deactivate)(struct intel_vgpu *); +int (*vgpu_query_plane)(struct intel_vgpu *vgpu,void *); +int (*vgpu_create_dmabuf)(struct intel_vgpu *vgpu,void *); };drivers/gpu/drm/i915/gvt/kvmgt.c +1
-0@@ -41,6 +41,7 @@#include <linux/kvm_host.h> #include <linux/vfio.h> #include <linux/mdev.h> +#include <linux/anon_inodes.h> #include "i915_drv.h" #include "gvt.h" @@ -524,6 +525,125 @@ static int intel_vgpu_reg_init_opregion(struct
intel_vgpu*vgpu)Quoted 38 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +35
-0return ret; } +static int kvmgt_get_vfio_device (struct intel_vgpu *vgpu) { +struct vfio_device *device; + + device =vfio_device_get_from_dev (mdev_dev (vgpu->vdev.mdev)); +if (device ==NULL ) +return -ENODEV ; + vgpu->vdev.vfio_device = device; + +return 0 ; +} + +static void kvmgt_put_vfio_device (struct intel_vgpu *vgpu) { +vfio_device_put (vgpu->vdev.vfio_device); +} + +static int intel_vgpu_dmabuf_mgr_fd_mmap (struct file *file, +struct vm_area_struct *vma) +{ +return -EPERM ; +} + +static int intel_vgpu_dmabuf_mgr_fd_release (struct inode *inode, +struct file *filp) +{ +struct intel_vgpu *vgpu = filp->private_data; +struct intel_vgpu_dmabuf_obj *obj; +struct list_head *pos; + +if (WARN_ON (!vgpu->vdev.vfio_device)) +return -ENODEV ; + +list_for_each (pos, &vgpu->dmabuf_obj_list_head) { + obj = container_of(pos, struct intel_vgpu_dmabuf_obj, list); +if (WARN_ON (!obj)) +return -ENODEV ;
Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 568
Quoted 4 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +4
-0+kfree (obj->obj->gvt_info); +i915_gem_object_put (obj->obj); +kfree (obj); +kvmgt_put_vfio_device (vgpu);Can we do this? If I understand, we're releasing all the references and allocations for the dmabuf fds on release of the manager fd. What happens if the user continues trying to access those dmabuf fds after this?
I think we can do this here.
The dma-buf's release function dma_buf_release() will be called by kernel which means all the created dmabufs will be invalid even we do not release all the references and allocations here.
Quoted 51 lines
Quoted 51 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +50
-0+ } +kvmgt_put_vfio_device (vgpu); + +return 0 ; +} + +static long intel_vgpu_dmabuf_mgr_fd_ioctl (struct file *filp, +unsigned int ioctl,unsigned long arg) { +struct intel_vgpu *vgpu = filp->private_data; +int minsz; +int ret; +struct fd f; + + f =fdget (vgpu->dmabuf_mgr_fd); +if (!f.file) +return -EBADF ; + +if (ioctl ==VFIO_DEVICE_QUERY_PLANE ) { +struct vfio_vgpu_plane_info info; + + minsz = offsetofend(struct vfio_vgpu_plane_info, resv); +if (copy_from_user (&info, (void __user *)arg, minsz)) { +fdput (f); +return -EFAULT ; + } +if (info.argsz < minsz) { +fdput (f); +return -EINVAL ; + } + ret = intel_gvt_ops->vgpu_query_plane (vgpu, &info); +if (ret !=0 ) { +fdput (f); +gvt_vgpu_err ("query plane failed:%d\n" , ret); +return -EINVAL ; + } +fdput (f); +return copy_to_user ((void __user *)arg, &info, minsz) ? + -EFAULT :0 ; + }else if (ioctl ==VFIO_DEVICE_CREATE_DMABUF ) { +struct vfio_vgpu_dmabuf_info dmabuf; + + minsz = offsetofend(struct vfio_vgpu_dmabuf_info, resv); +if (copy_from_user (&dmabuf, (void __user *)arg, minsz)) { +fdput (f); +return -EFAULT ; + } +if (dmabuf.argsz < minsz) { +fdput (f); +return -EINVAL ; + }
Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 622
Quoted 3 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +3
-0+ ret =kvmgt_get_vfio_device (vgpu); +if (ret !=0 ) +return ret;Missed an fdput, though I'm not sure I understand the value of the original fdget or the
dmabuf_mgr_fdfield at all.dmabuf_mgr_fdis only used here, presumably to add a reference to the fd while we're in the ioctl, but we're in the ioctl function of that fd, so I think there are already references elsewhere.
Make sense. Fdget/fdput can be removed.
Quoted 9 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 628
Quoted 7 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +6
-0+ + ret = intel_gvt_ops->vgpu_create_dmabuf (vgpu, &dmabuf); +if (ret !=0 ) { +kvmgt_put_vfio_device (vgpu); +fdput (f); +return -EINVAL ;Why not return the errno that
vgpu_create_dmabufprovided?
Will change to use the returned errno.
Quoted 41 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device
Quoted 23 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +18
-0+ } +fdput (f); +return copy_to_user ((void __user *)arg, &dmabuf, minsz) ? + -EFAULT :0 ; + } + +fdput (f); +gvt_vgpu_err ("unsupported dmabuf operation\n" ); + +return -EINVAL ; +} + +static const struct file_operations intel_vgpu_dmabuf_mgr_fd_ops = { + .release = intel_vgpu_dmabuf_mgr_fd_release, + .unlocked_ioctl = intel_vgpu_dmabuf_mgr_fd_ioctl, + .mmap = intel_vgpu_dmabuf_mgr_fd_mmap, + .llseek = noop_llseek, +};static int intel_vgpu_create (struct kobject *kobj,struct mdev_device *mdev) {struct intel_vgpu *vgpu =NULL ;@@ -1259,6 +1379,30 @@ static long intel_vgpu_ioctl(struct mdev_device*mdev, unsigned int cmd,
Quoted 17 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +14
-0}else if (cmd ==VFIO_DEVICE_RESET ) { intel_gvt_ops->vgpu_reset (vgpu);return 0 ; + }else if (cmd ==VFIO_DEVICE_GET_FD ) { +int fd; +u32 type; +int ret; + +if (copy_from_user (&type, (void __user *)arg,sizeof (type))) +return -EINVAL ; +if (type !=VFIO_DEVICE_DMABUF_MGR_FD ) +return -EINVAL ; + + ret =kvmgt_get_vfio_device (vgpu); +if (ret !=0 ) +return ret; +
Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, · line 1401
Quoted 6 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +6
-0+ fd =anon_inode_getfd ("intel-vgpu-dmabuf-mgr-fd" , + &intel_vgpu_dmabuf_mgr_fd_ops, + vgpu,O_RDWR |O_CLOEXEC ); +if (fd <0 ) { +gvt_vgpu_err ("create dmabuf mgr fd failed\n" ); +return -EINVAL ;Error path leaks
vfio_devicereference.
Will correct in the next version.
Quoted 6 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, · line 1403
Quoted 3 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +2
-0+ } + vgpu->dmabuf_mgr_fd = fd;As above, unclear value of this field, additionally, what if the user calls
VFIO_DEVICE_GET_FDmore than once?
Ah, good question.VFIO_DEVICE_GET_FD should only be called once.
And we should add a check if the vgpu->dmabuf_mgr_fd is not 0 which means VFIO_DEVICE_GET_FD had been called before we should return an error.
Quoted 12 lines
drivers/gpu/drm/i915/gvt/vgpu.c static struct intel_vgpu
Quoted 11 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +2
-0+ +return fd; }return 0 ;(quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/vgpu.cindex 6e3cbd8..af6fc74 100644drivers/gpu/drm/i915/gvt/vgpu.c +0
-0@@ -346,6 +346,7 @@ static struct intel_vgpu*__intel_gvt_create_vgpu(struct
intel_gvt*gvt,
Quoted 7 lines
drivers/gpu/drm/i915/gvt/vgpu.c static struct intel_vgpu *__intel_gvt_create_vgpu(struct intel_gvt *gvt, · line 352
Quoted 7 lines
drivers/gpu/drm/i915/gvt/vgpu.c +1
-0vgpu->gvt = gvt; vgpu->sched_ctl.weight = param->weight;bitmap_zero (vgpu->tlb_handle_pending,I915_NUM_ENGINES ); +INIT_LIST_HEAD (&vgpu->dmabuf_obj_list_head);intel_vgpu_init_cfg_space (vgpu, param->primary);
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-buf
Quoted 181 lines · Xiaoguang
Hi Alex,
Quoted 171 lines
-----Original Message-----
From: Alex Williamson [mailto:[email protected]]
Sent: Friday, June 02, 2017 2:08 AM
To: Chen, Xiaoguang <[email protected]>
Cc: [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-bufQuoted 11 lines · On Sat, 27 May 2017 16:38:52 +0800 Xiaoguang Chen <[email protected]>…
User space should create the management fd for the dma-buf operation first. Then user can query the plane information and create dma-buf if necessary using the management fd.
Signed-off-by Xiaoguang Chen <[email protected]>--- drivers/gpu/drm/i915/gvt/dmabuf.c | 12 ++++ drivers/gpu/drm/i915/gvt/dmabuf.h | 5 ++ drivers/gpu/drm/i915/gvt/gvt.c | 2 + drivers/gpu/drm/i915/gvt/gvt.h | 5 ++ drivers/gpu/drm/i915/gvt/kvmgt.c | 144++++++++++++++++++++++++++++++++++++++
drivers/gpu/drm/i915/gvt/dmabuf.c int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,
Quoted 9 lines
drivers/gpu/drm/i915/gvt/vgpu.c | 1 + 6 files changed, 169 insertions(+)drivers/gpu/drm/i915/gvt/dmabuf.c +0
-0@@ -226,6 +226,7 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,void *args)
drivers/gpu/drm/i915/gvt/dmabuf.c int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,
Quoted 8 lines
drivers/gpu/drm/i915/gvt/dmabuf.c +1
-0struct vfio_vgpu_dmabuf_info *gvt_dmabuf = args;struct intel_vgpu_fb_info *fb_info;int ret; +struct intel_vgpu_dmabuf_obj *dmabuf_obj; ret =intel_vgpu_get_plane_info (dev, vgpu, &gvt_dmabuf->plane_info);if (ret !=0 )@@ -263,6 +264,17 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,void *args)
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct
Quoted 86 lines
drivers/gpu/drm/i915/gvt/dmabuf.c +11
-0gvt_vgpu_err ("create dma-buf fd failed ret:%d\n" , ret);return ret; } + dmabuf_obj =kmalloc (sizeof (*dmabuf_obj),GFP_KERNEL ); +if (dmabuf_obj ==NULL ) { +kfree (fb_info); +i915_gem_object_put (obj); +gvt_vgpu_err ("alloc dmabuf_obj failed\n" ); +return -ENOMEM ; + } + dmabuf_obj->obj = obj; +INIT_LIST_HEAD (&dmabuf_obj->list); +list_add_tail (&dmabuf_obj->list, &vgpu->dmabuf_obj_list_head); + gvt_dmabuf->fd = ret;return 0 ;drivers/gpu/drm/i915/gvt/dmabuf.h +5
-0@@ -31,6 +31,11 @@ struct intel_vgpu_fb_info {uint32_t fb_size; }; +struct intel_vgpu_dmabuf_obj { +struct drm_i915_gem_object *obj; +struct list_head list; +}; +int intel_vgpu_query_plane (struct intel_vgpu *vgpu,void *args);int intel_vgpu_create_dmabuf (struct intel_vgpu *vgpu,void *args);(quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/gvt.cindex 2032917..dbc3f86 100644drivers/gpu/drm/i915/gvt/gvt.c +2
-0@@ -54,6 +54,8 @@ static const struct intel_gvt_ops intel_gvt_ops = { .vgpu_reset = intel_gvt_reset_vgpu, .vgpu_activate = intel_gvt_activate_vgpu, .vgpu_deactivate = intel_gvt_deactivate_vgpu, + .vgpu_query_plane = intel_vgpu_query_plane, + .vgpu_create_dmabuf = intel_vgpu_create_dmabuf, };/** (quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/gvt.hindex 763a8c5..a855797 100644drivers/gpu/drm/i915/gvt/gvt.h +5
-0@@ -185,8 +185,11 @@ struct intel_vgpu {struct kvm *kvm;struct work_struct release_work;atomic_t released; +struct vfio_device *vfio_device; } vdev;#endif +int dmabuf_mgr_fd; +struct list_head dmabuf_obj_list_head; }; struct intel_gvt_gm {@@ -467,6 +470,8 @@ struct intel_gvt_ops {void (*vgpu_reset)(struct intel_vgpu *);void (*vgpu_activate)(struct intel_vgpu *);void (*vgpu_deactivate)(struct intel_vgpu *); +int (*vgpu_query_plane)(struct intel_vgpu *vgpu,void *); +int (*vgpu_create_dmabuf)(struct intel_vgpu *vgpu,void *); };drivers/gpu/drm/i915/gvt/kvmgt.c +1
-0@@ -41,6 +41,7 @@#include <linux/kvm_host.h> #include <linux/vfio.h> #include <linux/mdev.h> +#include <linux/anon_inodes.h> #include "i915_drv.h" #include "gvt.h" @@ -524,6 +525,125 @@ static int intel_vgpu_reg_init_opregion(struct
intel_vgpu*vgpu)Quoted 38 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +35
-0return ret; } +static int kvmgt_get_vfio_device (struct intel_vgpu *vgpu) { +struct vfio_device *device; + + device =vfio_device_get_from_dev (mdev_dev (vgpu->vdev.mdev)); +if (device ==NULL ) +return -ENODEV ; + vgpu->vdev.vfio_device = device; + +return 0 ; +} + +static void kvmgt_put_vfio_device (struct intel_vgpu *vgpu) { +vfio_device_put (vgpu->vdev.vfio_device); +} + +static int intel_vgpu_dmabuf_mgr_fd_mmap (struct file *file, +struct vm_area_struct *vma) +{ +return -EPERM ; +} + +static int intel_vgpu_dmabuf_mgr_fd_release (struct inode *inode, +struct file *filp) +{ +struct intel_vgpu *vgpu = filp->private_data; +struct intel_vgpu_dmabuf_obj *obj; +struct list_head *pos; + +if (WARN_ON (!vgpu->vdev.vfio_device)) +return -ENODEV ; + +list_for_each (pos, &vgpu->dmabuf_obj_list_head) { + obj = container_of(pos, struct intel_vgpu_dmabuf_obj, list); +if (WARN_ON (!obj)) +return -ENODEV ;Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 568
Quoted 4 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +4
-0+kfree (obj->obj->gvt_info); +i915_gem_object_put (obj->obj); +kfree (obj); +kvmgt_put_vfio_device (vgpu);Can we do this? If I understand, we're releasing all the references and allocations for the dmabuf fds on release of the manager fd. What happens if the user continues trying to access those dmabuf fds after this?
Quoted 2 lines
I think we can do this here.
The dma-buf's release functiondma_buf_release()will be called by kernel which means all the created dmabufs will be invalid even we do not release all the references and allocations here.
Are you assuming that the user has closed the dmabuf fds? They could close the manager fd first, should the dmabuf fd continue to work?
Quoted 123 lines
Quoted 50 lines
Quoted 50 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +50
-0+ } +kvmgt_put_vfio_device (vgpu); + +return 0 ; +} + +static long intel_vgpu_dmabuf_mgr_fd_ioctl (struct file *filp, +unsigned int ioctl,unsigned long arg) { +struct intel_vgpu *vgpu = filp->private_data; +int minsz; +int ret; +struct fd f; + + f =fdget (vgpu->dmabuf_mgr_fd); +if (!f.file) +return -EBADF ; + +if (ioctl ==VFIO_DEVICE_QUERY_PLANE ) { +struct vfio_vgpu_plane_info info; + + minsz = offsetofend(struct vfio_vgpu_plane_info, resv); +if (copy_from_user (&info, (void __user *)arg, minsz)) { +fdput (f); +return -EFAULT ; + } +if (info.argsz < minsz) { +fdput (f); +return -EINVAL ; + } + ret = intel_gvt_ops->vgpu_query_plane (vgpu, &info); +if (ret !=0 ) { +fdput (f); +gvt_vgpu_err ("query plane failed:%d\n" , ret); +return -EINVAL ; + } +fdput (f); +return copy_to_user ((void __user *)arg, &info, minsz) ? + -EFAULT :0 ; + }else if (ioctl ==VFIO_DEVICE_CREATE_DMABUF ) { +struct vfio_vgpu_dmabuf_info dmabuf; + + minsz = offsetofend(struct vfio_vgpu_dmabuf_info, resv); +if (copy_from_user (&dmabuf, (void __user *)arg, minsz)) { +fdput (f); +return -EFAULT ; + } +if (dmabuf.argsz < minsz) { +fdput (f); +return -EINVAL ; + }Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 622
Quoted 3 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +3
-0+ ret =kvmgt_get_vfio_device (vgpu); +if (ret !=0 ) +return ret;Missed an fdput, though I'm not sure I understand the value of the original fdget or the
dmabuf_mgr_fdfield at all.dmabuf_mgr_fdis only used here, presumably to add a reference to the fd while we're in the ioctl, but we're in the ioctl function of that fd, so I think there are already references elsewhere.Make sense. Fdget/fdput can be removed.
Quoted 9 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 628
Quoted 7 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +6
-0+ + ret = intel_gvt_ops->vgpu_create_dmabuf (vgpu, &dmabuf); +if (ret !=0 ) { +kvmgt_put_vfio_device (vgpu); +fdput (f); +return -EINVAL ;Why not return the errno that
vgpu_create_dmabufprovided?Will change to use the returned errno.
Quoted 41 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device
Quoted 23 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +18
-0+ } +fdput (f); +return copy_to_user ((void __user *)arg, &dmabuf, minsz) ? + -EFAULT :0 ; + } + +fdput (f); +gvt_vgpu_err ("unsupported dmabuf operation\n" ); + +return -EINVAL ; +} + +static const struct file_operations intel_vgpu_dmabuf_mgr_fd_ops = { + .release = intel_vgpu_dmabuf_mgr_fd_release, + .unlocked_ioctl = intel_vgpu_dmabuf_mgr_fd_ioctl, + .mmap = intel_vgpu_dmabuf_mgr_fd_mmap, + .llseek = noop_llseek, +};static int intel_vgpu_create (struct kobject *kobj,struct mdev_device *mdev) {struct intel_vgpu *vgpu =NULL ;@@ -1259,6 +1379,30 @@ static long intel_vgpu_ioctl(struct mdev_device*mdev, unsigned int cmd,
Quoted 17 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +14
-0}else if (cmd ==VFIO_DEVICE_RESET ) { intel_gvt_ops->vgpu_reset (vgpu);return 0 ; + }else if (cmd ==VFIO_DEVICE_GET_FD ) { +int fd; +u32 type; +int ret; + +if (copy_from_user (&type, (void __user *)arg,sizeof (type))) +return -EINVAL ; +if (type !=VFIO_DEVICE_DMABUF_MGR_FD ) +return -EINVAL ; + + ret =kvmgt_get_vfio_device (vgpu); +if (ret !=0 ) +return ret; +Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, · line 1401
Quoted 6 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +6
-0+ fd =anon_inode_getfd ("intel-vgpu-dmabuf-mgr-fd" , + &intel_vgpu_dmabuf_mgr_fd_ops, + vgpu,O_RDWR |O_CLOEXEC ); +if (fd <0 ) { +gvt_vgpu_err ("create dmabuf mgr fd failed\n" ); +return -EINVAL ;Error path leaks
vfio_devicereference.Will correct in the next version.
Quoted 1 line
Quoted 8 lines
Quoted 5 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, · line 1403
Quoted 2 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +2
-0+ } + vgpu->dmabuf_mgr_fd = fd;As above, unclear value of this field, additionally, what if the user calls
VFIO_DEVICE_GET_FDmore than once?Ah, good question.
VFIO_DEVICE_GET_FDshould only be called once.
And we should add a check if thevgpu->dmabuf_mgr_fdis not 0 which meansVFIO_DEVICE_GET_FDhad been called before we should return an error.
Except we no longer need that fd and we should probably use an atomic 'opened' so it's not racy. Thanks,
Alex
Quoted 11 lines
Quoted 11 lines
drivers/gpu/drm/i915/gvt/vgpu.c static struct intel_vgpu
Quoted 10 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +2
-0+ +return fd; }return 0 ;(quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/vgpu.cindex 6e3cbd8..af6fc74 100644drivers/gpu/drm/i915/gvt/vgpu.c +0
-0@@ -346,6 +346,7 @@ static struct intel_vgpu*__intel_gvt_create_vgpu(struct
intel_gvt*gvt,
Quoted 8 lines
Quoted 7 lines
drivers/gpu/drm/i915/gvt/vgpu.c static struct intel_vgpu *__intel_gvt_create_vgpu(struct intel_gvt *gvt, · line 352
Quoted 7 lines
drivers/gpu/drm/i915/gvt/vgpu.c +1
-0vgpu->gvt = gvt; vgpu->sched_ctl.weight = param->weight;bitmap_zero (vgpu->tlb_handle_pending,I915_NUM_ENGINES ); +INIT_LIST_HEAD (&vgpu->dmabuf_obj_list_head);intel_vgpu_init_cfg_space (vgpu, param->primary);
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
RE: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-buf
Quoted 201 lines
-----Original Message-----
From: Alex Williamson [mailto:[email protected]]
Sent: Friday, June 02, 2017 11:35 AM
To: Chen, Xiaoguang <[email protected]>
Cc: [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-bufQuoted 184 lines · Xiaoguang
Hi Alex,
Quoted 182 lines
-----Original Message-----
From: Alex Williamson [mailto:[email protected]]
Sent: Friday, June 02, 2017 2:08 AM
To: Chen, Xiaoguang <[email protected]>
Cc: [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-bufQuoted 11 lines · On Sat, 27 May 2017 16:38:52 +0800 Xiaoguang Chen <[email protected]>…
User space should create the management fd for the dma-buf operation first. Then user can query the plane information and create dma-buf if necessary using the management fd.
Signed-off-by Xiaoguang Chen <[email protected]>--- drivers/gpu/drm/i915/gvt/dmabuf.c | 12 ++++ drivers/gpu/drm/i915/gvt/dmabuf.h | 5 ++ drivers/gpu/drm/i915/gvt/gvt.c | 2 + drivers/gpu/drm/i915/gvt/gvt.h | 5 ++ drivers/gpu/drm/i915/gvt/kvmgt.c | 144++++++++++++++++++++++++++++++++++++++
drivers/gpu/drm/i915/gvt/dmabuf.c int intel_vgpu_create_dmabuf(struct intel_vgpu · line 226
Quoted 10 lines
drivers/gpu/drm/i915/gvt/vgpu.c | 1 + 6 files changed, 169 insertions(+)drivers/gpu/drm/i915/gvt/dmabuf.c +0
-0@@ -226,6 +226,7 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,void *args)
drivers/gpu/drm/i915/gvt/dmabuf.c int intel_vgpu_create_dmabuf(struct intel_vgpu · line 264
Quoted 9 lines
drivers/gpu/drm/i915/gvt/dmabuf.c +1
-0struct vfio_vgpu_dmabuf_info *gvt_dmabuf = args;struct intel_vgpu_fb_info *fb_info;int ret; +struct intel_vgpu_dmabuf_obj *dmabuf_obj; ret =intel_vgpu_get_plane_info (dev, vgpu, &gvt_dmabuf->plane_info);drivers/gpu/drm/i915/gvt/dmabuf.c +0
-0if (ret !=0 )@@ -263,6 +264,17 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,void *args)
Quoted 86 lines
drivers/gpu/drm/i915/gvt/dmabuf.c +11
-0gvt_vgpu_err ("create dma-buf fd failed ret:%d\n" , ret);return ret; } + dmabuf_obj =kmalloc (sizeof (*dmabuf_obj),GFP_KERNEL ); +if (dmabuf_obj ==NULL ) { +kfree (fb_info); +i915_gem_object_put (obj); +gvt_vgpu_err ("alloc dmabuf_obj failed\n" ); +return -ENOMEM ; + } + dmabuf_obj->obj = obj; +INIT_LIST_HEAD (&dmabuf_obj->list); +list_add_tail (&dmabuf_obj->list, &vgpu->dmabuf_obj_list_head); + gvt_dmabuf->fd = ret;drivers/gpu/drm/i915/gvt/dmabuf.c +0
-0return 0 ;drivers/gpu/drm/i915/gvt/dmabuf.h +5
-0@@ -31,6 +31,11 @@ struct intel_vgpu_fb_info {uint32_t fb_size; }; +struct intel_vgpu_dmabuf_obj { +struct drm_i915_gem_object *obj; +struct list_head list; +}; +int intel_vgpu_query_plane (struct intel_vgpu *vgpu,void *args);int intel_vgpu_create_dmabuf (struct intel_vgpu *vgpu,void *args);(quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/gvt.cindex 2032917..dbc3f86 100644drivers/gpu/drm/i915/gvt/gvt.c +2
-0@@ -54,6 +54,8 @@ static const struct intel_gvt_ops intel_gvt_ops = { .vgpu_reset = intel_gvt_reset_vgpu, .vgpu_activate = intel_gvt_activate_vgpu, .vgpu_deactivate = intel_gvt_deactivate_vgpu, + .vgpu_query_plane = intel_vgpu_query_plane, + .vgpu_create_dmabuf = intel_vgpu_create_dmabuf, };/** (quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/gvt.hindex 763a8c5..a855797 100644drivers/gpu/drm/i915/gvt/gvt.h +5
-0@@ -185,8 +185,11 @@ struct intel_vgpu {struct kvm *kvm;struct work_struct release_work;atomic_t released; +struct vfio_device *vfio_device; } vdev;#endif +int dmabuf_mgr_fd; +struct list_head dmabuf_obj_list_head; }; struct intel_gvt_gm {@@ -467,6 +470,8 @@ struct intel_gvt_ops {void (*vgpu_reset)(struct intel_vgpu *);void (*vgpu_activate)(struct intel_vgpu *);void (*vgpu_deactivate)(struct intel_vgpu *); +int (*vgpu_query_plane)(struct intel_vgpu *vgpu,void *); +int (*vgpu_create_dmabuf)(struct intel_vgpu *vgpu,void *); };drivers/gpu/drm/i915/gvt/kvmgt.c +1
-0@@ -41,6 +41,7 @@#include <linux/kvm_host.h> #include <linux/vfio.h> #include <linux/mdev.h> +#include <linux/anon_inodes.h> #include "i915_drv.h" #include "gvt.h" @@ -524,6 +525,125 @@ static intQuoted 1 line
intel_vgpu_reg_init_opregion(struct
intel_vgpu*vgpu)Quoted 32 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +29
-0return ret; } +static int kvmgt_get_vfio_device (struct intel_vgpu *vgpu) { +struct vfio_device *device; + + device =vfio_device_get_from_dev (mdev_dev (vgpu->vdev.mdev)); +if (device ==NULL ) +return -ENODEV ; + vgpu->vdev.vfio_device = device; + +return 0 ; +} + +static void kvmgt_put_vfio_device (struct intel_vgpu *vgpu) { +vfio_device_put (vgpu->vdev.vfio_device); +} + +static int intel_vgpu_dmabuf_mgr_fd_mmap (struct file *file, +struct vm_area_struct *vma) +{ +return -EPERM ; +} + +static int intel_vgpu_dmabuf_mgr_fd_release (struct inode *inode, +struct file *filp) +{ +struct intel_vgpu *vgpu = filp->private_data; +struct intel_vgpu_dmabuf_obj *obj; +struct list_head *pos; + +if (WARN_ON (!vgpu->vdev.vfio_device))drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 568
Quoted 10 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +10
-0+return -ENODEV ; + +list_for_each (pos, &vgpu->dmabuf_obj_list_head) { + obj = container_of(pos, struct intel_vgpu_dmabuf_obj, list); +if (WARN_ON (!obj)) +return -ENODEV ; +kfree (obj->obj->gvt_info); +i915_gem_object_put (obj->obj); +kfree (obj); +kvmgt_put_vfio_device (vgpu);Can we do this? If I understand, we're releasing all the references and allocations for the dmabuf fds on release of the manager fd. What happens if the user continues trying to access those dmabuf fds after
Quoted 8 lines
this?
Quoted 2 lines
I think we can do this here.
The dma-buf's release functiondma_buf_release()will be called by kernel whichmeans all the created dmabufs will be invalid even we do not release all the references and allocations here.
Are you assuming that the user has closed the dmabuf fds? They could close the manager fd first, should the dmabuf fd continue to work?
If guest vm was shutdown it is ok system will release the allocated fds including the management fd and dmabuf fds. But if user call the close() to close the management fd deliberately there are problems in current implementation.
Usually vendor of dma-buf defines its own dma_buf_ops(map, unmap, release.....) so vendor can release the reference and allocations in the release callback. The calling sequence is: dma-buf framework's release()->vendor's dma-buf release(i915's in our case).
But in our case we did not create the dma-buf from the scratch but calling an existing i915 function i915_gem_prime_export() to create a dma-buf which use the i915's dma-buf-ops. In order to use this function we must create a gem object first(the reference count of the gem object is now 1!!!).
When i915's dma-buf's release() callback is called it will try to free the gem object associated with the dma-buf if its ref count is 0. But in our case the ref count is 1 so no free callback is called so we can not release allocations there. So we have to release our dma-buf releated allocations in the management fd's release callback which means the dma-bufs' life cycle must the same with the management fd.
The reason we call i915_gem_prime_export() to create a dma-buf is we do not need to change the i915's dma-buf framework.
So: 1) we maintain current implementation that the dma-bufs have the same lifecycle with the management fd. User can not close the management fd. Or
2) we create the dma-buf from scratch which need to change the dma-buf infrastructure of i915.
Chenxg
Quoted 135 lines
Quoted 51 lines
Quoted 51 lines
Quoted 51 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +50
-0+ } +kvmgt_put_vfio_device (vgpu); + +return 0 ; +} + +static long intel_vgpu_dmabuf_mgr_fd_ioctl (struct file *filp, +unsigned int ioctl,unsigned long arg) { +struct intel_vgpu *vgpu = filp->private_data; +int minsz; +int ret; +struct fd f; + + f =fdget (vgpu->dmabuf_mgr_fd); +if (!f.file) +return -EBADF ; + +if (ioctl ==VFIO_DEVICE_QUERY_PLANE ) { +struct vfio_vgpu_plane_info info; + + minsz = offsetofend(struct vfio_vgpu_plane_info, resv); +if (copy_from_user (&info, (void __user *)arg, minsz)) { +fdput (f); +return -EFAULT ; + } +if (info.argsz < minsz) { +fdput (f); +return -EINVAL ; + } + ret = intel_gvt_ops->vgpu_query_plane (vgpu, &info); +if (ret !=0 ) { +fdput (f); +gvt_vgpu_err ("query plane failed:%d\n" , ret); +return -EINVAL ; + } +fdput (f); +return copy_to_user ((void __user *)arg, &info, minsz) ? + -EFAULT :0 ; + }else if (ioctl ==VFIO_DEVICE_CREATE_DMABUF ) { +struct vfio_vgpu_dmabuf_info dmabuf; + + minsz = offsetofend(struct vfio_vgpu_dmabuf_info, resv); +if (copy_from_user (&dmabuf, (void __user *)arg, minsz)) { +fdput (f); +return -EFAULT ; + } +if (dmabuf.argsz < minsz) { +fdput (f); +return -EINVAL ; + }Quoted 8 lines
Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 622
Quoted 3 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +3
-0+ ret =kvmgt_get_vfio_device (vgpu); +if (ret !=0 ) +return ret;Missed an fdput, though I'm not sure I understand the value of the original fdget or the
dmabuf_mgr_fdfield at all.dmabuf_mgr_fdis only used here, presumably to add a reference to the fd while we're in the ioctl, but we're in the ioctl function of that fd, so I think there arealready references elsewhere.
Quoted 67 lines
Make sense. Fdget/fdput can be removed.
Quoted 9 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 628
Quoted 7 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +6
-0+ + ret = intel_gvt_ops->vgpu_create_dmabuf (vgpu, &dmabuf); +if (ret !=0 ) { +kvmgt_put_vfio_device (vgpu); +fdput (f); +return -EINVAL ;Why not return the errno that
vgpu_create_dmabufprovided?Will change to use the returned errno.
Quoted 43 lines
Quoted 24 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +18
-0+ } +fdput (f); +return copy_to_user ((void __user *)arg, &dmabuf, minsz) ? + -EFAULT :0 ; + } + +fdput (f); +gvt_vgpu_err ("unsupported dmabuf operation\n" ); + +return -EINVAL ; +} + +static const struct file_operations intel_vgpu_dmabuf_mgr_fd_ops = { + .release = intel_vgpu_dmabuf_mgr_fd_release, + .unlocked_ioctl = intel_vgpu_dmabuf_mgr_fd_ioctl, + .mmap = intel_vgpu_dmabuf_mgr_fd_mmap, + .llseek = noop_llseek, +}; static int intel_vgpu_create(struct kobject *kobj, struct
mdev_device
*mdev) {drivers/gpu/drm/i915/gvt/kvmgt.c +0
-0struct intel_vgpu *vgpu =NULL ;@@ -1259,6 +1379,30 @@ static long intel_vgpu_ioctl(structQuoted 1 line
mdev_device*mdev, unsigned int cmd,
Quoted 17 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +14
-0}else if (cmd ==VFIO_DEVICE_RESET ) { intel_gvt_ops->vgpu_reset (vgpu);return 0 ; + }else if (cmd ==VFIO_DEVICE_GET_FD ) { +int fd; +u32 type; +int ret; + +if (copy_from_user (&type, (void __user *)arg,sizeof (type))) +return -EINVAL ; +if (type !=VFIO_DEVICE_DMABUF_MGR_FD ) +return -EINVAL ; + + ret =kvmgt_get_vfio_device (vgpu); +if (ret !=0 ) +return ret; +Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, · line 1401
Quoted 6 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +6
-0+ fd =anon_inode_getfd ("intel-vgpu-dmabuf-mgr-fd" , + &intel_vgpu_dmabuf_mgr_fd_ops, + vgpu,O_RDWR |O_CLOEXEC ); +if (fd <0 ) { +gvt_vgpu_err ("create dmabuf mgr fd failed\n" ); +return -EINVAL ;Error path leaks
vfio_devicereference.Will correct in the next version.
Quoted 1 line
Quoted 8 lines
Quoted 5 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, · line 1403
Quoted 2 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +2
-0+ } + vgpu->dmabuf_mgr_fd = fd;As above, unclear value of this field, additionally, what if the user calls
VFIO_DEVICE_GET_FDmore than once?Ah, good question.
VFIO_DEVICE_GET_FDshould only be called once.
And we should add a check if thevgpu->dmabuf_mgr_fdis not 0 which means
Quoted 26 lines
VFIO_DEVICE_GET_FDhad been called before we should return an error.Except we no longer need that fd and we should probably use an atomic 'opened' so it's not racy. Thanks,
Alex
Quoted 19 lines
Quoted 18 lines
drivers/gpu/drm/i915/gvt/vgpu.c static struct intel_vgpu
Quoted 10 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +2
-0+ +return fd; }return 0 ;(quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/vgpu.cindex 6e3cbd8..af6fc74 100644drivers/gpu/drm/i915/gvt/vgpu.c +0
-0@@ -346,6 +346,7 @@ static struct intel_vgpu*__intel_gvt_create_vgpu(struct
intel_gvt*gvt,Quoted 7 lines
drivers/gpu/drm/i915/gvt/vgpu.c +1
-0vgpu->gvt = gvt; vgpu->sched_ctl.weight = param->weight;bitmap_zero (vgpu->tlb_handle_pending,I915_NUM_ENGINES ); +INIT_LIST_HEAD (&vgpu->dmabuf_obj_list_head);intel_vgpu_init_cfg_space (vgpu, param->primary);
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-buf
Quoted 216 lines · Xiaoguang
Quoted 199 lines
-----Original Message-----
From: Alex Williamson [mailto:[email protected]]
Sent: Friday, June 02, 2017 11:35 AM
To: Chen, Xiaoguang <[email protected]>
Cc: [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-bufQuoted 184 lines · Xiaoguang
Hi Alex,
Quoted 182 lines
-----Original Message-----
From: Alex Williamson [mailto:[email protected]]
Sent: Friday, June 02, 2017 2:08 AM
To: Chen, Xiaoguang <[email protected]>
Cc: [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-bufQuoted 11 lines · On Sat, 27 May 2017 16:38:52 +0800 Xiaoguang Chen <[email protected]>…
User space should create the management fd for the dma-buf operation first. Then user can query the plane information and create dma-buf if necessary using the management fd.
Signed-off-by Xiaoguang Chen <[email protected]>--- drivers/gpu/drm/i915/gvt/dmabuf.c | 12 ++++ drivers/gpu/drm/i915/gvt/dmabuf.h | 5 ++ drivers/gpu/drm/i915/gvt/gvt.c | 2 + drivers/gpu/drm/i915/gvt/gvt.h | 5 ++ drivers/gpu/drm/i915/gvt/kvmgt.c | 144++++++++++++++++++++++++++++++++++++++
drivers/gpu/drm/i915/gvt/dmabuf.c int intel_vgpu_create_dmabuf(struct intel_vgpu · line 226
Quoted 10 lines
drivers/gpu/drm/i915/gvt/vgpu.c | 1 + 6 files changed, 169 insertions(+)drivers/gpu/drm/i915/gvt/dmabuf.c +0
-0@@ -226,6 +226,7 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,void *args)
drivers/gpu/drm/i915/gvt/dmabuf.c int intel_vgpu_create_dmabuf(struct intel_vgpu · line 264
Quoted 9 lines
drivers/gpu/drm/i915/gvt/dmabuf.c +1
-0struct vfio_vgpu_dmabuf_info *gvt_dmabuf = args;struct intel_vgpu_fb_info *fb_info;int ret; +struct intel_vgpu_dmabuf_obj *dmabuf_obj; ret =intel_vgpu_get_plane_info (dev, vgpu, &gvt_dmabuf->plane_info);drivers/gpu/drm/i915/gvt/dmabuf.c +0
-0if (ret !=0 )@@ -263,6 +264,17 @@ int intel_vgpu_create_dmabuf(struct intel_vgpu *vgpu,void *args)
Quoted 86 lines
drivers/gpu/drm/i915/gvt/dmabuf.c +11
-0gvt_vgpu_err ("create dma-buf fd failed ret:%d\n" , ret);return ret; } + dmabuf_obj =kmalloc (sizeof (*dmabuf_obj),GFP_KERNEL ); +if (dmabuf_obj ==NULL ) { +kfree (fb_info); +i915_gem_object_put (obj); +gvt_vgpu_err ("alloc dmabuf_obj failed\n" ); +return -ENOMEM ; + } + dmabuf_obj->obj = obj; +INIT_LIST_HEAD (&dmabuf_obj->list); +list_add_tail (&dmabuf_obj->list, &vgpu->dmabuf_obj_list_head); + gvt_dmabuf->fd = ret;drivers/gpu/drm/i915/gvt/dmabuf.c +0
-0return 0 ;drivers/gpu/drm/i915/gvt/dmabuf.h +5
-0@@ -31,6 +31,11 @@ struct intel_vgpu_fb_info {uint32_t fb_size; }; +struct intel_vgpu_dmabuf_obj { +struct drm_i915_gem_object *obj; +struct list_head list; +}; +int intel_vgpu_query_plane (struct intel_vgpu *vgpu,void *args);int intel_vgpu_create_dmabuf (struct intel_vgpu *vgpu,void *args);(quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/gvt.cindex 2032917..dbc3f86 100644drivers/gpu/drm/i915/gvt/gvt.c +2
-0@@ -54,6 +54,8 @@ static const struct intel_gvt_ops intel_gvt_ops = { .vgpu_reset = intel_gvt_reset_vgpu, .vgpu_activate = intel_gvt_activate_vgpu, .vgpu_deactivate = intel_gvt_deactivate_vgpu, + .vgpu_query_plane = intel_vgpu_query_plane, + .vgpu_create_dmabuf = intel_vgpu_create_dmabuf, };/** (quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/gvt.hindex 763a8c5..a855797 100644drivers/gpu/drm/i915/gvt/gvt.h +5
-0@@ -185,8 +185,11 @@ struct intel_vgpu {struct kvm *kvm;struct work_struct release_work;atomic_t released; +struct vfio_device *vfio_device; } vdev;#endif +int dmabuf_mgr_fd; +struct list_head dmabuf_obj_list_head; }; struct intel_gvt_gm {@@ -467,6 +470,8 @@ struct intel_gvt_ops {void (*vgpu_reset)(struct intel_vgpu *);void (*vgpu_activate)(struct intel_vgpu *);void (*vgpu_deactivate)(struct intel_vgpu *); +int (*vgpu_query_plane)(struct intel_vgpu *vgpu,void *); +int (*vgpu_create_dmabuf)(struct intel_vgpu *vgpu,void *); };drivers/gpu/drm/i915/gvt/kvmgt.c +1
-0@@ -41,6 +41,7 @@#include <linux/kvm_host.h> #include <linux/vfio.h> #include <linux/mdev.h> +#include <linux/anon_inodes.h> #include "i915_drv.h" #include "gvt.h" @@ -524,6 +525,125 @@ static intQuoted 1 line
intel_vgpu_reg_init_opregion(struct
intel_vgpu*vgpu)Quoted 32 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +29
-0return ret; } +static int kvmgt_get_vfio_device (struct intel_vgpu *vgpu) { +struct vfio_device *device; + + device =vfio_device_get_from_dev (mdev_dev (vgpu->vdev.mdev)); +if (device ==NULL ) +return -ENODEV ; + vgpu->vdev.vfio_device = device; + +return 0 ; +} + +static void kvmgt_put_vfio_device (struct intel_vgpu *vgpu) { +vfio_device_put (vgpu->vdev.vfio_device); +} + +static int intel_vgpu_dmabuf_mgr_fd_mmap (struct file *file, +struct vm_area_struct *vma) +{ +return -EPERM ; +} + +static int intel_vgpu_dmabuf_mgr_fd_release (struct inode *inode, +struct file *filp) +{ +struct intel_vgpu *vgpu = filp->private_data; +struct intel_vgpu_dmabuf_obj *obj; +struct list_head *pos; + +if (WARN_ON (!vgpu->vdev.vfio_device))drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 568
Quoted 10 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +10
-0+return -ENODEV ; + +list_for_each (pos, &vgpu->dmabuf_obj_list_head) { + obj = container_of(pos, struct intel_vgpu_dmabuf_obj, list); +if (WARN_ON (!obj)) +return -ENODEV ; +kfree (obj->obj->gvt_info); +i915_gem_object_put (obj->obj); +kfree (obj); +kvmgt_put_vfio_device (vgpu);Can we do this? If I understand, we're releasing all the references and allocations for the dmabuf fds on release of the manager fd. What happens if the user continues trying to access those dmabuf fds after
Quoted 8 lines
this?
Quoted 2 lines
I think we can do this here.
The dma-buf's release functiondma_buf_release()will be called by kernel whichmeans all the created dmabufs will be invalid even we do not release all the references and allocations here.
Are you assuming that the user has closed the dmabuf fds? They could close the manager fd first, should the dmabuf fd continue to work?
If guest vm was shutdown it is ok system will release the allocated fds including the management fd and dmabuf fds. But if user call the
close()to close the management fd deliberately there are problems in current implementation.Usually vendor of dma-buf defines its own
dma_buf_ops(map, unmap, release.....)so vendor can release the reference and allocations in the release callback. The calling sequence is: dma-buf framework's release()->vendor's dma-buf release(i915's in our case).But in our case we did not create the dma-buf from the scratch but calling an existing i915 function
i915_gem_prime_export()to create a dma-buf which use the i915's dma-buf-ops. In order to use this function we must create a gem object first(the reference count of the gem object is now 1!!!).
Quoted 7 lines
When i915's dma-buf's
release()callback is called it will try to free the gem object associated with the dma-buf if its ref count is 0. But in our case the ref count is 1 so no free callback is called so we can not release allocations there. So we have to release our dma-buf releated allocations in the management fd's release callback which means the dma-bufs' life cycle must the same with the management fd.The reason we call
i915_gem_prime_export()to create a dma-buf is we do not need to change the i915's dma-buf framework.So: 1) we maintain current implementation that the dma-bufs have the same lifecycle with the management fd. User can not close the management fd. Or
2) we create the dma-buf from scratch which need to change the dma-buf infrastructure of i915.
We cannot simply say that the user isn't allowed to release them in that order. If they do, how does it break, including what might mmaps into those dmabufs provide them access to after the underlying object is removed. If the policy is that the management fd cannot be released until the dmabufs are closed, then that needs to be actively enforced. Otherwise it needs to be supported. Requiring changes to dmabuf handling in the i915 code isn't an excuse IMO. Thanks,
Alex
Quoted 152 lines
Quoted 152 lines
Quoted 50 lines
Quoted 50 lines
Quoted 50 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +50
-0+ } +kvmgt_put_vfio_device (vgpu); + +return 0 ; +} + +static long intel_vgpu_dmabuf_mgr_fd_ioctl (struct file *filp, +unsigned int ioctl,unsigned long arg) { +struct intel_vgpu *vgpu = filp->private_data; +int minsz; +int ret; +struct fd f; + + f =fdget (vgpu->dmabuf_mgr_fd); +if (!f.file) +return -EBADF ; + +if (ioctl ==VFIO_DEVICE_QUERY_PLANE ) { +struct vfio_vgpu_plane_info info; + + minsz = offsetofend(struct vfio_vgpu_plane_info, resv); +if (copy_from_user (&info, (void __user *)arg, minsz)) { +fdput (f); +return -EFAULT ; + } +if (info.argsz < minsz) { +fdput (f); +return -EINVAL ; + } + ret = intel_gvt_ops->vgpu_query_plane (vgpu, &info); +if (ret !=0 ) { +fdput (f); +gvt_vgpu_err ("query plane failed:%d\n" , ret); +return -EINVAL ; + } +fdput (f); +return copy_to_user ((void __user *)arg, &info, minsz) ? + -EFAULT :0 ; + }else if (ioctl ==VFIO_DEVICE_CREATE_DMABUF ) { +struct vfio_vgpu_dmabuf_info dmabuf; + + minsz = offsetofend(struct vfio_vgpu_dmabuf_info, resv); +if (copy_from_user (&dmabuf, (void __user *)arg, minsz)) { +fdput (f); +return -EFAULT ; + } +if (dmabuf.argsz < minsz) { +fdput (f); +return -EINVAL ; + }Quoted 8 lines
Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 622
Quoted 3 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +3
-0+ ret =kvmgt_get_vfio_device (vgpu); +if (ret !=0 ) +return ret;Missed an fdput, though I'm not sure I understand the value of the original fdget or the
dmabuf_mgr_fdfield at all.dmabuf_mgr_fdis only used here, presumably to add a reference to the fd while we're in the ioctl, but we're in the ioctl function of that fd, so I think there arealready references elsewhere.
Quoted 67 lines
Make sense. Fdget/fdput can be removed.
Quoted 9 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static int intel_vgpu_reg_init_opregion(struct intel_vgpu *vgpu) · line 628
Quoted 7 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +6
-0+ + ret = intel_gvt_ops->vgpu_create_dmabuf (vgpu, &dmabuf); +if (ret !=0 ) { +kvmgt_put_vfio_device (vgpu); +fdput (f); +return -EINVAL ;Why not return the errno that
vgpu_create_dmabufprovided?Will change to use the returned errno.
Quoted 43 lines
Quoted 24 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +18
-0+ } +fdput (f); +return copy_to_user ((void __user *)arg, &dmabuf, minsz) ? + -EFAULT :0 ; + } + +fdput (f); +gvt_vgpu_err ("unsupported dmabuf operation\n" ); + +return -EINVAL ; +} + +static const struct file_operations intel_vgpu_dmabuf_mgr_fd_ops = { + .release = intel_vgpu_dmabuf_mgr_fd_release, + .unlocked_ioctl = intel_vgpu_dmabuf_mgr_fd_ioctl, + .mmap = intel_vgpu_dmabuf_mgr_fd_mmap, + .llseek = noop_llseek, +}; static int intel_vgpu_create(struct kobject *kobj, struct
mdev_device
*mdev) {drivers/gpu/drm/i915/gvt/kvmgt.c +0
-0struct intel_vgpu *vgpu =NULL ;@@ -1259,6 +1379,30 @@ static long intel_vgpu_ioctl(structQuoted 1 line
mdev_device*mdev, unsigned int cmd,
Quoted 17 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +14
-0}else if (cmd ==VFIO_DEVICE_RESET ) { intel_gvt_ops->vgpu_reset (vgpu);return 0 ; + }else if (cmd ==VFIO_DEVICE_GET_FD ) { +int fd; +u32 type; +int ret; + +if (copy_from_user (&type, (void __user *)arg,sizeof (type))) +return -EINVAL ; +if (type !=VFIO_DEVICE_DMABUF_MGR_FD ) +return -EINVAL ; + + ret =kvmgt_get_vfio_device (vgpu); +if (ret !=0 ) +return ret; +Quoted 8 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, · line 1401
Quoted 6 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +6
-0+ fd =anon_inode_getfd ("intel-vgpu-dmabuf-mgr-fd" , + &intel_vgpu_dmabuf_mgr_fd_ops, + vgpu,O_RDWR |O_CLOEXEC ); +if (fd <0 ) { +gvt_vgpu_err ("create dmabuf mgr fd failed\n" ); +return -EINVAL ;Error path leaks
vfio_devicereference.Will correct in the next version.
Quoted 1 line
Quoted 8 lines
Quoted 5 lines
drivers/gpu/drm/i915/gvt/kvmgt.c static long intel_vgpu_ioctl(struct mdev_device *mdev, unsigned int cmd, · line 1403
Quoted 2 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +2
-0+ } + vgpu->dmabuf_mgr_fd = fd;As above, unclear value of this field, additionally, what if the user calls
VFIO_DEVICE_GET_FDmore than once?Ah, good question.
VFIO_DEVICE_GET_FDshould only be called once.
And we should add a check if thevgpu->dmabuf_mgr_fdis not 0 which means
VFIO_DEVICE_GET_FDhad been called before we should return an error.Except we no longer need that fd and we should probably use an atomic 'opened' so it's not racy. Thanks,
Alex
Quoted 11 lines
Quoted 11 lines
drivers/gpu/drm/i915/gvt/vgpu.c static struct intel_vgpu
Quoted 10 lines
drivers/gpu/drm/i915/gvt/kvmgt.c +2
-0+ +return fd; }return 0 ;(quoted diff) +0
-0
b/drivers/gpu/drm/i915/gvt/vgpu.cindex 6e3cbd8..af6fc74 100644drivers/gpu/drm/i915/gvt/vgpu.c +0
-0@@ -346,6 +346,7 @@ static struct intel_vgpu*__intel_gvt_create_vgpu(struct
intel_gvt*gvt,
Quoted 9 lines
Quoted 8 lines
Quoted 8 lines
Quoted 7 lines
drivers/gpu/drm/i915/gvt/vgpu.c static struct intel_vgpu *__intel_gvt_create_vgpu(struct intel_gvt *gvt, · line 352
Quoted 7 lines
drivers/gpu/drm/i915/gvt/vgpu.c +1
-0vgpu->gvt = gvt; vgpu->sched_ctl.weight = param->weight;bitmap_zero (vgpu->tlb_handle_pending,I915_NUM_ENGINES ); +INIT_LIST_HEAD (&vgpu->dmabuf_obj_list_head);intel_vgpu_init_cfg_space (vgpu, param->primary);
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-buf
Hi,
Quoted 4 lines
Quoted 4 lines
When i915's dma-buf's
release()callback is called it will try to free the gem object associated with the dma-buf if its ref count is
0. But in our case the ref count is 1 so no free callback is called so we can not release allocations there.
Why the ref count is one? Who holds a reference and why? Maybe it should be the other way around, i.e. the dmabuf holds a reference on the vgpu instance backing it, i.e. you can't delete the vgpu while dma-bufs exist?
Quoted 2 lines
We cannot simply say that the user isn't allowed to release them in that order.
Yep, not going to fly. Can happen even unintentionally because we can pass around dmabufs to other processes. Example: qemu passes dmabuf to spice-client, then qemu crashes. mgmt fd is closed before dmabuf fd then. The kernel must be able to handle that.
cheers,
Gerd
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
RE: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-buf
Hi,
Quoted 13 lines
-----Original Message-----
From: intel-gvt-dev [mailto:[email protected]] On Behalf Of Gerd Hoffmann
Sent: Friday, June 02, 2017 11:24 PM
To: Alex Williamson <[email protected]>; Chen, Xiaoguang <[email protected]>
Cc: Tian, Kevin <[email protected]>; [email protected]; linux- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; [email protected]; Wang, Zhi A <[email protected]>
Subject: Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-buf
Quoted 8 lines
Hi,
Quoted 4 lines
Quoted 4 lines
When i915's dma-buf's
release()callback is called it will try to free the gem object associated with the dma-buf if its ref count is
0. But in our case the ref count is 1 so no free callback is called so we can not release allocations there.Why the ref count is one?
The gem object is created by us while creating the dma-buf(the ref count of the gem object is initialized to 1).
Later when user import the dma-buf the ref count of the gem object associate with the dma-buf will increased.
When user finished using the dma-buf it will decrease the ref count.
But the ref count of the gem object will become 1 when all the user finished using the dma-buf because we create the gem object(the test also showing this result).
Typically user only export a dma-buf(no gem object yet) then when user import the dma-buf then a gem object will be created. But in our case we do not implement the dma-buf from scratch but calling the i915_gem_prime_export() where a gem object is an input parameter.
Chenxg
Quoted 12 lines
Who holds a reference and why?
Maybe it should be the other way around, i.e. the dmabuf holds a reference on the vgpu instance backing it, i.e. you can't delete the vgpu while dma-bufs exist?Quoted 2 lines
We cannot simply say that the user isn't allowed to release them in that order.
Yep, not going to fly. Can happen even unintentionally because we can pass around dmabufs to other processes. Example: qemu passes dmabuf to spice- client, then qemu crashes. mgmt fd is closed before dmabuf fd then. The kernel must be able to handle that.
Quoted 6 lines
cheers,
Gerd
_______________________________________________
intel-gvt-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v6 6/6] drm/i915/gvt: Adding interface so user space can get the dma-buf
Hi,
Quoted 6 lines
Quoted 1 line
Why the ref count is one?
The gem object is created by us while creating the dma-buf(the ref count of the gem object is initialized to 1).
Later when user import the dma-buf the ref count of the gem object associate with the dma-buf will increased.
Creating the dma-buf should increase the gem object reference count too. So you should be able to unref the gem object after creating the dma-buf. That way the dma-buf is the only instance holding a reference to the gem object, and when the dma-buf goes away (due to userspace closing all file handles referring to it) the gem object will be released too because the refcount goes down to zero then.
cheers,
Gerd
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.BAT: failure for drm/i915/gvt: dma-buf support for GVT-g (rev6)
In reply to Xiaoguang Chen== Series Details ==
== Series Details ==
Series: drm/i915/gvt: dma-buf support for GVT-g (rev6)
URL : https://patchwork.freedesktop.org/series/23686/
State : failure
== Summary ==
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/bounds.h
CHK include/generated/timeconst.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
CHK scripts/mod/devicetable-offsets.h
CHK include/generated/compile.h
CHK kernel/config_data.h
CC [M] drivers/gpu/drm/i915/i915_drv.o
In file included from drivers/gpu/drm/i915/i915_vma.h:34:0,
from drivers/gpu/drm/i915/intel_uc.h:31,
from drivers/gpu/drm/i915/i915_drv.h:61,
from drivers/gpu/drm/i915/i915_drv.c:49:drivers/gpu/drm/i915/i915_gem_object.h:40:1: error: expected specifier-qualifier-list before ‘<<’ token
<<<<<<< 391b5aa3660577581466b0d4594e1a61fae843bd
^drivers/gpu/drm/i915/i915_gem_object.h:40:9: error: invalid suffix "b5aa3660577581466b0d4594e1a61fae843bd" on integer constant
<<<<<<< 391b5aa3660577581466b0d4594e1a61fae843bd
^
drivers/gpu/drm/i915/i915_gem_object.h:44:0: error: "I915_GEM_OBJECT_HAS_STRUCT_PAGE" redefined [-Werror]
#define I915_GEM_OBJECT_HAS_STRUCT_PAGE 0x1
^drivers/gpu/drm/i915/i915_gem_object.h:41:0: note: this is the location of the previous definition
#define I915_GEM_OBJECT_HAS_STRUCT_PAGE BIT(0)
^drivers/gpu/drm/i915/i915_gem_object.h:45:0: error: "I915_GEM_OBJECT_IS_SHRINKABLE" redefined [-Werror]
#define I915_GEM_OBJECT_IS_SHRINKABLE 0x2
^drivers/gpu/drm/i915/i915_gem_object.h:42:0: note: this is the location of the previous definition
#define I915_GEM_OBJECT_IS_SHRINKABLE BIT(1)
^
cc1: all warnings being treated as errorsscripts/Makefile.build:302: recipe for target 'drivers/gpu/drm/i915/i915_drv.o' failed make[4]: *** [drivers/gpu/drm/i915/i915_drv.o] Error 1scripts/Makefile.build:561: recipe for target 'drivers/gpu/drm/i915' failed
make[3]: *** [drivers/gpu/drm/i915] Error 2scripts/Makefile.build:561: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2scripts/Makefile.build:561: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1016: recipe for target 'drivers' failed
make: *** [drivers] Error 2
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Hi,
Quoted 7 lines
This patch set adds the dma-buf support for intel GVT-g. dma-buf is a uniform mechanism to share DMA buffers across different devices and sub-systems.
dma-buf for intel GVT-g is mainly used to share the vgpu's framebuffer
to other users or sub-systems so they can use the dma-buf to show the desktop of a vm which uses intel vgpu.
Which branch is this based on?
Applying to gvt-stable-4.11 doesn't work. Applying to drm-intel-next doesn't work either ...
cheers,
Gerd
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Hi Gerd,
It is based on 4.12.0-rc1
Quoted 20 lines
-----Original Message-----
From: Gerd Hoffmann [mailto:[email protected]]
Sent: Tuesday, May 30, 2017 6:24 PM
To: Chen, Xiaoguang <[email protected]>; [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 0/6] drm/i915/gvt: Dma-buf support for GVT-gHi,
Quoted 6 lines
This patch set adds the dma-buf support for intel GVT-g. dma-buf is a uniform mechanism to share DMA buffers across different devices and sub-systems.
dma-buf for intel GVT-g is mainly used to share the vgpu's framebuffer to other users or sub-systems so they can use the dma-buf to show the desktop of a vm which uses intel vgpu.
Quoted 6 lines
Which branch is this based on?
Applying to gvt-stable-4.11 doesn't work. Applying to drm-intel-next doesn't work either ...cheers,
Gerd
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 3 lines · Xiaoguang
Hi Gerd,
It is based on 4.12.0-rc1
Applies, good.
But then fails to build:
error: ‘struct vfio_vgpu_dmabuf_info’ has no member named ‘resv’
gvt/kvmgt.c:611:11: note: in expansion of macro ‘offsetofend’ minsz = offsetofend(struct vfio_vgpu_dmabuf_info, resv);
/me wonders how this was tested ...
cheers,
Gerd
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Hi Gerd,
I found this problem once I sent the patches :(
I checked the uapi definitions and found it is usually called pad to do the aligning. So I changed the 'resv' to 'pad' in the patch but forgot to update it in the last patch and did not test after the "small" change. Next time I will test even when the change is very small.
I will change this in the next version.
Sorry for the mistake.
Quoted 21 lines
-----Original Message-----
From: Gerd Hoffmann [mailto:[email protected]]
Sent: Wednesday, May 31, 2017 4:59 PM
To: Chen, Xiaoguang <[email protected]>; [email protected]; [email protected]; intel- [email protected]; [email protected]; [email protected]; Lv, Zhiyuan <[email protected]>; intel-gvt- [email protected]; Wang, Zhi A <[email protected]>; Tian, Kevin <[email protected]>
Subject: Re: [PATCH v6 0/6] drm/i915/gvt: Dma-buf support for GVT-gQuoted 3 lines · Xiaoguang
Hi Gerd,
It is based on 4.12.0-rc1
Applies, good.
But then fails to build:error: ‘struct vfio_vgpu_dmabuf_info’ has no member named ‘resv’
Quoted 7 lines
gvt/kvmgt.c:611:11: note: in expansion of macro ‘offsetofend’ minsz =offsetofend(struct vfio_vgpu_dmabuf_info, resv);/me wonders how this was tested ...
cheers,
Gerd
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx