intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Murthy, Arun R" <arun.r.murthy@intel.com>
To: Louis Chauvet <louis.chauvet@bootlin.com>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>, <xaver.hugl@kde.org>,
	<harry.wentland@amd.com>, <uma.shankar@intel.com>
Cc: <dri-devel@lists.freedesktop.org>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v5 4/5] drm/atomic: Return user readable error in atomic_ioctl
Date: Thu, 9 Oct 2025 09:30:19 +0530	[thread overview]
Message-ID: <b3849b27-a93e-4821-8b0e-2a32bbdcbde7@intel.com> (raw)
In-Reply-To: <75d34fe4-a820-4a2c-a73d-b4ce8e8e872f@bootlin.com>

On 01-10-2025 20:17, Louis Chauvet wrote:
>
>
> Le 16/09/2025 à 09:18, Arun R Murthy a écrit :
>> Add user readable error codes for failure cases in drm_atomic_ioctl() so
>> that user can decode the error code and take corrective measurements.
>>
>> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
>> ---
>>   drivers/gpu/drm/drm_atomic_uapi.c | 71 
>> ++++++++++++++++++++++++++++-----------
>>   1 file changed, 52 insertions(+), 19 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_atomic_uapi.c 
>> b/drivers/gpu/drm/drm_atomic_uapi.c
>> index 
>> 3ef478e717bec917d1b8803c72bbcc8d6409d745..3d4e9709e8e289cf302413e171b1336812d65c1c 
>> 100644
>> --- a/drivers/gpu/drm/drm_atomic_uapi.c
>> +++ b/drivers/gpu/drm/drm_atomic_uapi.c
>> @@ -1036,6 +1036,11 @@ int drm_atomic_set_property(struct 
>> drm_atomic_state *state,
>>               ret = drm_atomic_connector_get_property(connector, 
>> connector_state,
>>                                   prop, &old_val);
>>               ret = drm_atomic_check_prop_changes(ret, old_val, 
>> prop_value, prop);
>> +            if (ret) {
>> + drm_mode_atomic_add_error_msg(&state->error_code,
>> + DRM_MODE_ATOMIC_ASYNC_PROP_CHANGED,
>> +                                  "property change not allowed in 
>> async flip");
>> +            }
>>               break;
>>           }
>>   @@ -1058,6 +1063,11 @@ int drm_atomic_set_property(struct 
>> drm_atomic_state *state,
>>               ret = drm_atomic_crtc_get_property(crtc, crtc_state,
>>                                  prop, &old_val);
>>               ret = drm_atomic_check_prop_changes(ret, old_val, 
>> prop_value, prop);
>> +            if (ret) {
>> + drm_mode_atomic_add_error_msg(&state->error_code,
>> + DRM_MODE_ATOMIC_ASYNC_PROP_CHANGED,
>> +                                  "property change not allowed in 
>> async flip");
>> +            }
>>               break;
>>           }
>>   @@ -1096,9 +1106,10 @@ int drm_atomic_set_property(struct 
>> drm_atomic_state *state,
>>                       ret = plane_funcs->atomic_async_check(plane, 
>> state, true);
>>                     if (ret) {
>> -                    drm_dbg_atomic(prop->dev,
>> -                               "[PLANE:%d:%s] does not support async 
>> flips\n",
>> -                               obj->id, plane->name);
>> + drm_mode_atomic_add_error_msg(&state->error_code,
>> + DRM_MODE_ATOMIC_ASYNC_NOT_SUPP_PLANE,
>> +                                      "[PLANE:%d:%s] does not 
>> support async flip",
>> +                                      obj->id, plane->name);
>>                       break;
>
> Thanks for this series, it is a nice contribution!
>
> I am not sure about this change, drm_dbg will be in debug logs, but 
> drm_mode_atomic_add_error_msg do a drm_err, is it expected?
> This is also the case for other drm_mode_atomic_add_error_msg calls in 
> this patch and the next one.
>
Thanks for pointing out, this was a miss from my side.
Will get it changed to debug prints.

Thanks and Regards,
Arun R Murthy
-------------------

>>                   }
>>               }
>> @@ -1393,6 +1404,7 @@ int drm_mode_atomic_ioctl(struct drm_device *dev,
>>       struct drm_atomic_state *state;
>>       struct drm_modeset_acquire_ctx ctx;
>>       struct drm_out_fence_state *fence_state;
>> +    struct drm_mode_atomic_err_code __user *error_code_ptr;
>>       int ret = 0;
>>       unsigned int i, j, num_fences = 0;
>>       bool async_flip = false;
>> @@ -1401,6 +1413,14 @@ int drm_mode_atomic_ioctl(struct drm_device *dev,
>>       if (!drm_core_check_feature(dev, DRIVER_ATOMIC))
>>           return -EOPNOTSUPP;
>>   +    if (!arg->reserved)
>> +        drm_dbg_atomic(dev,
>> +                   "memory not allocated for drm_atomic error 
>> reporting\n");
>> +    else
>> +        /* update the error code if any error to allow user handling 
>> it */
>> +        error_code_ptr = (struct drm_mode_atomic_err_code __user *)
>> +                 (unsigned long)arg->reserved;
>> +
>>       state = drm_atomic_state_alloc(dev);
>>       if (!state)
>>           return -ENOMEM;
>> @@ -1409,31 +1429,35 @@ int drm_mode_atomic_ioctl(struct drm_device 
>> *dev,
>>       state->acquire_ctx = &ctx;
>>       state->allow_modeset = !!(arg->flags & 
>> DRM_MODE_ATOMIC_ALLOW_MODESET);
>>   +    memset(&state->error_code, 0, sizeof(struct 
>> drm_mode_atomic_err_code));
>> +
>>       /* disallow for userspace that has not enabled atomic cap (even
>>        * though this may be a bit overkill, since legacy userspace
>>        * wouldn't know how to call this ioctl)
>>        */
>>       if (!file_priv->atomic) {
>> -        drm_dbg_atomic(dev,
>> -                   "commit failed: atomic cap not enabled\n");
>> -        return -EINVAL;
>> + drm_mode_atomic_add_error_msg(&state->error_code,
>> +                          DRM_MODE_ATOMIC_INVALID_API_USAGE,
>> +                          "DRM_ATOMIC capability not enabled");
>> +        ret = -EINVAL;
>> +        goto out;
>>       }
>>         if (arg->flags & ~DRM_MODE_ATOMIC_FLAGS) {
>> -        drm_dbg_atomic(dev, "commit failed: invalid flag\n");
>> -        return -EINVAL;
>> -    }
>> -
>> -    if (arg->reserved) {
>> -        drm_dbg_atomic(dev, "commit failed: reserved field set\n");
>> -        return -EINVAL;
>> + drm_mode_atomic_add_error_msg(&state->error_code,
>> +                          DRM_MODE_ATOMIC_INVALID_API_USAGE,
>> +                          "invalid flag");
>> +        ret = -EINVAL;
>> +        goto out;
>>       }
>>         if (arg->flags & DRM_MODE_PAGE_FLIP_ASYNC) {
>>           if (!dev->mode_config.async_page_flip) {
>> -            drm_dbg_atomic(dev,
>> -                       "commit failed: DRM_MODE_PAGE_FLIP_ASYNC not 
>> supported\n");
>> -            return -EINVAL;
>> + drm_mode_atomic_add_error_msg(&state->error_code,
>> + DRM_MODE_ATOMIC_INVALID_API_USAGE,
>> +                              "DRM_MODE_PAGE_FLIP_ASYNC not 
>> supported with ATOMIC ioctl");
>> +            ret = -EINVAL;
>> +            goto out;
>>           }
>>             async_flip = true;
>> @@ -1442,9 +1466,11 @@ int drm_mode_atomic_ioctl(struct drm_device *dev,
>>       /* can't test and expect an event at the same time. */
>>       if ((arg->flags & DRM_MODE_ATOMIC_TEST_ONLY) &&
>>               (arg->flags & DRM_MODE_PAGE_FLIP_EVENT)) {
>> -        drm_dbg_atomic(dev,
>> -                   "commit failed: page-flip event requested with 
>> test-only commit\n");
>> -        return -EINVAL;
>> + drm_mode_atomic_add_error_msg(&state->error_code,
>> +                          DRM_MODE_ATOMIC_INVALID_API_USAGE,
>> +                          "page-flip event requested with test-only 
>> commit");
>> +        ret = -EINVAL;
>> +        goto out;
>>       }
>>     retry:
>> @@ -1543,6 +1569,13 @@ int drm_mode_atomic_ioctl(struct drm_device *dev,
>>       }
>>     out:
>> +    /* update the error code if any error to allow user handling it */
>> +    if (ret < 0 && arg->reserved) {
>> +        if (copy_to_user(error_code_ptr, &state->error_code,
>> +                 sizeof(state->error_code)))
>> +            return -EFAULT;
>> +    }
>> +
>>       if (num_fences)
>>           complete_signaling(dev, state, fence_state, num_fences, !ret);
>>
>

  reply	other threads:[~2025-10-09  4:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16  7:18 [PATCH v5 0/5] User readable error codes on atomic_ioctl failure Arun R Murthy
2025-09-16  7:18 ` [PATCH v5 1/5] drm: Define user readable error codes for atomic ioctl Arun R Murthy
2025-09-16  7:18 ` [PATCH v5 2/5] drm/atomic: Add error_code element in atomic_state Arun R Murthy
2025-09-16  7:18 ` [PATCH v5 3/5] drm/atomic: Allocate atomic_state at the beginning of atomic_ioctl Arun R Murthy
2025-09-16  7:18 ` [PATCH v5 4/5] drm/atomic: Return user readable error in atomic_ioctl Arun R Murthy
2025-10-01 14:47   ` Louis Chauvet
2025-10-09  4:00     ` Murthy, Arun R [this message]
2025-09-16  7:18 ` [PATCH v5 5/5] drm/i915/display: Error codes for async flip failures Arun R Murthy
2025-09-16  8:41 ` ✓ i915.CI.BAT: success for User readable error codes on atomic_ioctl failure (rev4) Patchwork
2025-09-16 10:37 ` ✗ i915.CI.Full: failure " Patchwork
2025-09-30  4:03 ` [PATCH v5 0/5] User readable error codes on atomic_ioctl failure Murthy, Arun R

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b3849b27-a93e-4821-8b0e-2a32bbdcbde7@intel.com \
    --to=arun.r.murthy@intel.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=harry.wentland@amd.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=louis.chauvet@bootlin.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=tursulin@ursulin.net \
    --cc=tzimmermann@suse.de \
    --cc=uma.shankar@intel.com \
    --cc=xaver.hugl@kde.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).