From: "André Almeida" <andrealmeid@igalia.com>
To: Raag Jadav <raag.jadav@intel.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 2/4] drm/doc: Document device wedged event
Date: Tue, 17 Dec 2024 08:57:24 -0300 [thread overview]
Message-ID: <314af6e1-82e5-405f-aa2c-21708207e7d8@igalia.com> (raw)
In-Reply-To: <Z2E5ZbRym80khid2@black.fi.intel.com>
Em 17/12/2024 05:42, Raag Jadav escreveu:
> On Thu, Dec 12, 2024 at 03:50:29PM -0300, André Almeida wrote:
>> Em 28/11/2024 12:37, Raag Jadav escreveu:
>>> Add documentation for device wedged event in a new 'Device wedging'
>>> chapter. The describes basic definitions, prerequisites and consumer
>>> expectations along with an example.
>>>
>>> v8: Improve documentation (Christian, Rodrigo)
>>> v9: Add prerequisites section (Christian)
>>> v10: Clarify mmap cleanup and consumer prerequisites (Christian, Aravind)
>>>
>>> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
>>> Reviewed-by: Christian König <christian.koenig@amd.com>
>>> ---
>>> Documentation/gpu/drm-uapi.rst | 112 ++++++++++++++++++++++++++++++++-
>>> 1 file changed, 109 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/Documentation/gpu/drm-uapi.rst b/Documentation/gpu/drm-uapi.rst
>>> index b75cc9a70d1f..da2927cde53d 100644
>>> --- a/Documentation/gpu/drm-uapi.rst
>>> +++ b/Documentation/gpu/drm-uapi.rst
>>> @@ -371,9 +371,115 @@ Reporting causes of resets
>>
>> I think it's a good idea to add a note about "device wedged event" in the
>> section "Device reset > Kernel Mode Driver" since the idea is to explain
>> what should kernel developer add to their kernel drivers to be used when a
>> device resets.
>
> Wouldn't that be just a repetition of below? Also, I'm not sure if it's a hard
> requirement.
>
Right, it can get repetitive indeed, no need to apply this suggestion then.
next prev parent reply other threads:[~2024-12-17 11:57 UTC|newest]
Thread overview: 34+ 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
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 [this message]
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-29 0:07 ` ✗ Xe.CI.Full: failure " 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=314af6e1-82e5-405f-aa2c-21708207e7d8@igalia.com \
--to=andrealmeid@igalia.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--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=raag.jadav@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox