[Intel-gfx] [PATCH v6 2/6] drm/i915/gvt: OpRegion support for GVT-g

Chen, Xiaoguang xiaoguang.chen at intel.com
Wed May 31 06:44:20 UTC 2017



>-----Original Message-----
>From: Zhenyu Wang [mailto:zhenyuw at linux.intel.com]
>Sent: Wednesday, May 31, 2017 2:30 PM
>To: Chen, Xiaoguang <xiaoguang.chen at intel.com>
>Cc: Tian, Kevin <kevin.tian at intel.com>; intel-gfx at lists.freedesktop.org; linux-
>kernel at vger.kernel.org; chris at chris-wilson.co.uk; alex.williamson at redhat.com;
>kraxel at redhat.com; Niu, Bing <bing.niu at intel.com>; intel-gvt-
>dev at lists.freedesktop.org; Wang, Zhi A <zhi.a.wang at intel.com>; Lv, Zhiyuan
><zhiyuan.lv at intel.com>
>Subject: Re: [PATCH v6 2/6] drm/i915/gvt: OpRegion support for GVT-g
>
>On 2017.05.31 06:22:28 +0000, Chen, Xiaoguang wrote:
>> >> @@ -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.
>> 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.
Then we must add a new entry in intel_gvt_mpt interface something like "create_opregion".

>
>--
>Open Source Technology Center, Intel ltd.
>
>$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827


More information about the Intel-gfx mailing list