public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	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, louis.chauvet@bootlin.com,
	naveen1.kumar@intel.com, ramya.krishna.yella@intel.com,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org,
	Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH v10 0/7] User readable error codes on atomic_ioctl failure
Date: Tue, 24 Feb 2026 09:07:12 +0200	[thread overview]
Message-ID: <aZ1OIDsVfFvyHUK5@intel.com> (raw)
In-Reply-To: <1a4462b8-def9-4474-8382-6e99b7c8276d@intel.com>

On Mon, Feb 23, 2026 at 03:37:39PM +0530, Murthy, Arun R wrote:
> Any other comments/feedback on this?

Having random strings as uabi seems like a bad idea.
How would you make sure those are never changed?

> 
> Thanks and Regards,
> Arun R Murthy
> -------------------
> 
> On 23-02-2026 14:45, Arun R Murthy wrote:
> > EDITME: Imported from f20260210-atomic-v9-5-525c88fd2402@intel.com
> >          Please review before sending.
> >
> > The series focuses on providing a user readable error value on a failure
> > in drm_atomic_ioctl(). Usually -EINVAL is returned in most of the error
> > cases and it is difficult for the user to decode the error and get to
> > know the real cause for the error. If user gets to know the reason for
> > the error then corrective measurements can be taken up.
> >
> > User will have to check for the capability
> > DRM_CAP_ATOMIC_ERROR_REPORTING before using this feature so as to ensure
> > that the driver supports failure reporting.
> >
> > TODO: driver specific error codes are to be added and will be done in
> > the follow-up patches.
> >
> > TODO: Once the series is merged the element 'reserved' used for sending
> > the failure code in struct drm_mode_atomic is to changed to err_code.
> >
> > The IGT related changes are pushed for review @
> > https://patchwork.freedesktop.org/series/153330/
> >
> > [RFC] changes for libdrm pushed for review @
> > https://gitlab.freedesktop.org/mesa/libdrm/-/merge_requests/450
> >
> >      To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> >      To: suraj.kandpal@intel.com>
> >      To: Maxime Ripard <mripard@kernel.org>
> >      To: Thomas Zimmermann <tzimmermann@suse.de>
> >      To: David Airlie <airlied@gmail.com>
> >      To: Simona Vetter <simona@ffwll.ch>
> >      To: Jani Nikula <jani.nikula@linux.intel.com>
> >      To: Rodrigo Vivi <rodrigo.vivi@intel.com>
> >      To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> >      To: Tvrtko Ursulin <tursulin@ursulin.net>
> >      To: xaver.hugl@kde.org
> >      To: harry.wentland@amd.com
> >      To: uma.shankar@intel.com
> >      To: louis.chauvet@bootlin.com
> >      To: naveen1.kumar@intel.com
> >      To: ramya.krishna.yella@intel.com
> >      Cc: dri-devel@lists.freedesktop.org
> >      Cc: intel-gfx@lists.freedesktop.org
> >      Cc: intel-xe@lists.freedesktop.org
> >      Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> >
> > Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> > ---
> > Changes in v9:
> > - EDITME: describe what is new in this series revision.
> > - EDITME: use bulletpoints and terse descriptions.
> > - Link to v8: https://lore.kernel.org/r/20260129-atomic-v8-0-4cb7b0faa051@intel.com
> >
> > ---
> > Arun R Murthy (7):
> >        drm: Define user readable error codes for atomic ioctl
> >        drm/atomic: Add error_code element in atomic_state
> >        drm/atomic: Call complete_signaling only if prepare_signaling is done
> >        drm/atomic: Allocate atomic_state at the beginning of atomic_ioctl
> >        drm/atomic: Return user readable error in atomic_ioctl
> >        drm/i915/display: Error codes for async flip failures
> >        drm: Introduce DRM_CAP_ATOMIC_ERROR_REPORTING
> >
> >   drivers/gpu/drm/drm_atomic.c                 | 31 ++++++++++
> >   drivers/gpu/drm/drm_atomic_uapi.c            | 89 ++++++++++++++++++++--------
> >   drivers/gpu/drm/drm_ioctl.c                  |  3 +
> >   drivers/gpu/drm/i915/display/intel_display.c | 25 ++++----
> >   include/drm/drm_atomic.h                     | 10 ++++
> >   include/uapi/drm/drm.h                       |  7 +++
> >   include/uapi/drm/drm_mode.h                  | 37 ++++++++++++
> >   7 files changed, 165 insertions(+), 37 deletions(-)
> > ---
> > base-commit: cec43d5c2696af219fc2ef71dd7e93db48c80f66
> > change-id: 20250728-atomic-c9713fd357e4
> >
> > Best regards,

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2026-02-24  7:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23  9:15 [PATCH v10 0/7] User readable error codes on atomic_ioctl failure Arun R Murthy
2026-02-23  9:15 ` [PATCH v10 1/7] drm: Define user readable error codes for atomic ioctl Arun R Murthy
2026-02-23  9:16 ` [PATCH v10 2/7] drm/atomic: Add error_code element in atomic_state Arun R Murthy
2026-02-23  9:16 ` [PATCH v10 3/7] drm/atomic: Call complete_signaling only if prepare_signaling is done Arun R Murthy
2026-02-23  9:16 ` [PATCH v10 4/7] drm/atomic: Allocate atomic_state at the beginning of atomic_ioctl Arun R Murthy
2026-02-23  9:16 ` [PATCH v10 5/7] drm/atomic: Return user readable error in atomic_ioctl Arun R Murthy
2026-02-23  9:16 ` [PATCH v10 6/7] drm/i915/display: Error codes for async flip failures Arun R Murthy
2026-02-23  9:16 ` [PATCH v10 7/7] drm: Introduce DRM_CAP_ATOMIC_ERROR_REPORTING Arun R Murthy
2026-02-23 10:07 ` [PATCH v10 0/7] User readable error codes on atomic_ioctl failure Murthy, Arun R
2026-02-24  7:07   ` Ville Syrjälä [this message]
2026-02-24  7:16     ` Murthy, Arun R
2026-02-24  8:46       ` Ville Syrjälä
2026-02-24  8:54         ` Murthy, Arun R
2026-02-24  9:03           ` Ville Syrjälä
2026-02-24  9:28         ` Jani Nikula
2026-02-24  9:31           ` Murthy, Arun R
2026-02-24 12:07             ` Jani Nikula
2026-03-18 15:26               ` Xaver Hugl
2026-02-23 11:09 ` ✗ i915.CI.BAT: failure for User readable error codes on atomic_ioctl failure (rev9) Patchwork
2026-03-18 15:05 ` [PATCH v10 0/7] User readable error codes on atomic_ioctl failure Xaver Hugl
2026-03-23  6:07   ` Murthy, Arun R
2026-03-23 21:19     ` Xaver Hugl
2026-03-24  4:46       ` 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=aZ1OIDsVfFvyHUK5@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=arun.r.murthy@intel.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=naveen1.kumar@intel.com \
    --cc=ramya.krishna.yella@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=suraj.kandpal@intel.com \
    --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