drm: Print the pid when debug logging an ioctl error.
Subsystems (2)
PATCH 1/1 drm: Print the pid when debug logging an ioctl error.
When we debug print what ioctl we're calling into, we include the pid. If you have multiple processes rendering simulataneously, the error return also needs the pid so you can see which of the ioctl calls was the one to fail.
--- drivers/gpu/drm/drm_ioctl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/drm_ioctl.c +1 -1
@@ -842,7 +842,7 @@ long drm_ioctl(struct file *filp,if (kdata != stack_kdata)kfree (kdata);if (retcode) -DRM_DEBUG ("ret = %d\n" , retcode); +DRM_DEBUG ("pid=%d, ret = %d\n" ,task_pid_nr (current), retcode);return retcode; }EXPORT_SYMBOL (drm_ioctl);
Signature · 6 lines
2.15.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Quoted 6 lines · Eric Anholt
When we debug print what ioctl we're calling into, we include the pid. If you have multiple processes rendering simulataneously, the error return also needs the pid so you can see which of the ioctl calls was the one to fail.
Signed-off-by Eric Anholt <[email protected]>
Quoted 24 lines
--- drivers/gpu/drm/drm_ioctl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/gpu/drm/drm_ioctl.c +1
-1@@ -842,7 +842,7 @@ long drm_ioctl(struct file *filp,if (kdata != stack_kdata)kfree (kdata);if (retcode) -DRM_DEBUG ("ret = %d\n" , retcode); +DRM_DEBUG ("pid=%d, ret = %d\n" ,task_pid_nr (current), retcode);return retcode; }EXPORT_SYMBOL (drm_ioctl);Signature · 6 lines
2.15.0 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Quoted 9 lines · Daniel Vetter
Quoted 6 lines · Eric Anholt
When we debug print what ioctl we're calling into, we include the pid. If you have multiple processes rendering simulataneously, the error return also needs the pid so you can see which of the ioctl calls was the one to fail.
Signed-off-by Eric Anholt <[email protected]>Reviewed-by Daniel Vetter <[email protected]>
Pushed. Thanks!
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel