Date: Wed, 18 Mar 2020 04:40:53 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 244877] graphics/mesa-dri: Fix vulkan by switching to unsynchronized userptr ioctls Message-ID: <bug-244877-7141-iXaBeQ7Jgp@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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244877 --- Comment #3 from Jan Beich <jbeich@FreeBSD.org> --- When I915_USERPTR_UNSYNCHRONIZED fails it maybe nice to advise user to run = as root e.g., if (geteuid() !=3D 0) { fprintf(stderr, "%s", "ioctl(I915_GEM_USERPTR) failed. Try running as r= oot but expect poor stability.\n"); } where "poor stability" alludes to markj@ comment in https://github.com/FreeBSDDesktop/kms-drm/issues/197#issuecomment-289590556 That definition only allows unsynchronized userptr objects, and such objects can probably be used to trigger nasty system behaviour since there's nothing preventing the process from unmapping pages bound to a GEM userptr object. However, I915_USERPTR_UNSYNCHRONIZED seems to work fine in compute-runtime, media-driver and xf86-video-intel. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-244877-7141-iXaBeQ7Jgp>