From: Raag Jadav <raag.jadav@intel.com>
To: "André Almeida" <andrealmeid@igalia.com>
Cc: airlied@gmail.com, simona@ffwll.ch, lucas.demarchi@intel.com,
rodrigo.vivi@intel.com, jani.nikula@linux.intel.com,
andriy.shevchenko@linux.intel.com, lina@asahilina.net,
michal.wajdeczko@intel.com, christian.koenig@amd.com,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, himal.prasad.ghimiray@intel.com,
aravind.iddamsetty@linux.intel.com, anshuman.gupta@intel.com,
alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org,
kernel-dev@igalia.com
Subject: Re: [PATCH v10 1/4] drm: Introduce device wedged event
Date: Fri, 13 Dec 2024 15:51:41 +0200 [thread overview]
Message-ID: <Z1w77fAac2vOaIEd@black.fi.intel.com> (raw)
In-Reply-To: <9557db3c-0837-4dfb-ba69-84dbaf13f082@igalia.com>
On Thu, Dec 12, 2024 at 03:31:01PM -0300, André Almeida wrote:
> Hi Raag,
>
> Thank you for your patch.
>
> Em 28/11/2024 12:37, Raag Jadav escreveu:
>
> [...]
>
> > +int drm_dev_wedged_event(struct drm_device *dev, unsigned long method)
> > +{
> > + const char *recovery = NULL;
> > + unsigned int len, opt;
> > + /* Event string length up to 28+ characters with available methods */
> > + char event_string[32];
> > + char *envp[] = { event_string, NULL };
> > +
> > + len = scnprintf(event_string, sizeof(event_string), "%s", "WEDGED=");
> > +
> > + for_each_set_bit(opt, &method, BITS_PER_TYPE(method)) {
> > + recovery = drm_get_wedge_recovery(opt);
> > + if (drm_WARN(dev, !recovery, "device wedged, invalid recovery method %u\n", opt))
> > + break;
> > +
> > + len += scnprintf(event_string + len, sizeof(event_string), "%s,", recovery);
> > + }
> > +
> > + if (recovery)
> > + /* Get rid of trailing comma */
> > + event_string[len - 1] = '\0';
> > + else
> > + /* Caller is unsure about recovery, do the best we can at this point. */
> > + snprintf(event_string, sizeof(event_string), "%s", "WEDGED=unknown");
> > +
> > + drm_info(dev, "device wedged, needs recovery\n");
>
> As documented in the commit message "No explicit device recovery is expected
> from the consumer in this case", I think this should be like this:
>
> if (method != DRM_WEDGE_RECOVERY_NONE)
> drm_info(dev, "device wedged, needs recovery\n");
>
> and maybe a note like this:
>
> else
> drm_info(dev, "device reseted, but managed to recover\n");
Or perhaps
drm_info(dev, "device wedged, but recovered through reset\n");
> Either way, this patch is:
>
> Reviewed-by: André Almeida <andrealmeid@igalia.com>
Thanks for the review.
Raag
next prev parent reply other threads:[~2024-12-16 8:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 15:37 [PATCH v10 0/4] Introduce DRM device wedged event Raag Jadav
2024-11-28 15:37 ` [PATCH v10 1/4] drm: Introduce " Raag Jadav
2024-11-29 13:40 ` André Almeida
2024-12-02 8:07 ` Raag Jadav
2024-12-03 5:00 ` Raag Jadav
2024-12-03 10:18 ` Christian König
2024-12-04 11:17 ` Raag Jadav
2024-12-11 17:14 ` Maxime Ripard
2024-12-12 10:37 ` Raag Jadav
2024-12-16 16:07 ` Maxime Ripard
2024-12-12 18:31 ` André Almeida
2024-12-13 13:51 ` Raag Jadav [this message]
2024-11-28 15:37 ` [PATCH v10 2/4] drm/doc: Document " Raag Jadav
2024-12-12 18:50 ` André Almeida
2024-12-17 8:42 ` Raag Jadav
2024-12-17 11:57 ` André Almeida
2025-01-21 1:14 ` Xaver Hugl
2025-01-22 5:22 ` Raag Jadav
2025-01-27 10:23 ` Pekka Paalanen
2025-01-28 9:37 ` Raag Jadav
2025-01-28 11:38 ` Pekka Paalanen
2025-01-29 7:04 ` Raag Jadav
2024-11-28 15:37 ` [PATCH v10 3/4] drm/xe: Use " Raag Jadav
2024-11-28 15:37 ` [PATCH v10 4/4] drm/i915: " Raag Jadav
2024-11-28 15:52 ` ✓ CI.Patch_applied: success for Introduce DRM device wedged event (rev8) Patchwork
2024-11-28 15:52 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-28 15:53 ` ✓ CI.KUnit: success " Patchwork
2024-11-28 16:11 ` ✓ CI.Build: " Patchwork
2024-11-28 16:13 ` ✓ CI.Hooks: " Patchwork
2024-11-28 16:15 ` ✗ CI.checksparse: warning " Patchwork
2024-11-28 16:33 ` ✓ Xe.CI.BAT: success " Patchwork
2024-11-28 17:45 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-11-28 17:45 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-28 17:59 ` ✗ i915.CI.BAT: failure " Patchwork
2024-11-29 0:07 ` ✗ Xe.CI.Full: " Patchwork
2025-01-21 0:59 ` [PATCH v10 0/4] Introduce DRM device wedged event Xaver Hugl
2025-01-22 4:48 ` Raag Jadav
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=Z1w77fAac2vOaIEd@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrealmeid@igalia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=aravind.iddamsetty@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kernel-dev@igalia.com \
--cc=lina@asahilina.net \
--cc=lucas.demarchi@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.