Date: Wed, 18 Mar 2020 00:57:35 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: maintainer-feedback requested: [Bug 244877] graphics/mesa-dri: Fixing vulkan by switching to unsynchronized userptr ioctls Message-ID: <bug-244877-7141-idalVySqp9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-244877-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-244877-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-x11 mailing li= st <x11@FreeBSD.org> for maintainer-feedback: Bug 244877: graphics/mesa-dri: Fixing vulkan by switching to unsynchronized userptr ioctls https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244877 --- Description --- This is the userspace portion of a change which fixes the Vulkan graphics A= PI on older Intel machines: https://github.com/FreeBSDDesktop/kms-drm/pull/205 The above PR fixes the unsychronized DRM_IOCTL_I915_GEM_USERPTR which is us= ed by intel's vulkan code. For the fix to be used the ioctl needs to have the I915_USERPTR_UNSYNCHRONIZED flag enabled: struct drm_i915_gem_userptr userptr =3D { .user_ptr =3D (__u64)((unsigned long) mem), .user_size =3D size, - .flags =3D 0, + .flags =3D I915_USERPTR_UNSYNCHRONIZED, }; int ret =3D anv_ioctl(device->fd, DRM_IOCTL_I915_GEM_USERPTR, &userptr); I've needed both the PR and this change for some daily vulkan development to work. It seems that maybe all the mesa stuff is going to be overhauled soon? So m= aybe this isn't the ideal time to merge this. Please let me know if there is anything I can help with!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-244877-7141-idalVySqp9>