From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: <dri-devel@lists.freedesktop.org>
Cc: daniel.vetter@ffwll.ch, intel-xe@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PATCH 2/4] drm/doc/rfc: Mark Dev_coredump as completed.
Date: Tue, 29 Aug 2023 12:30:02 -0400 [thread overview]
Message-ID: <20230829163005.54067-2-rodrigo.vivi@intel.com> (raw)
In-Reply-To: <20230829163005.54067-1-rodrigo.vivi@intel.com>
Xe is already using devcoredump infrastructure as the primary
error state and all the changes needed for user space error
replay and other useful logs are getting added into xe_devcoredump.
Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/blob/drm-xe-next/drivers/gpu/drm/xe/xe_devcoredump.c
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
---
Documentation/gpu/rfc/xe.rst | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/Documentation/gpu/rfc/xe.rst b/Documentation/gpu/rfc/xe.rst
index 3d2181bf3dad..bf60c5c82d0e 100644
--- a/Documentation/gpu/rfc/xe.rst
+++ b/Documentation/gpu/rfc/xe.rst
@@ -67,8 +67,8 @@ platforms.
When the time comes for Xe, the protection will be lifted on Xe and kept in i915.
-Xe – Pre-Merge Goals
-====================
+Xe – Pre-Merge Goals - Work-in-Progress
+=======================================
Drm_scheduler
-------------
@@ -206,6 +206,14 @@ This item ties into the GPUVA, VM_BIND, and even long-running compute support.
As a key measurable result, we need to have a community consensus documented in
this document and the Xe driver prepared for the changes, if necessary.
+Xe – uAPI high level overview
+=============================
+
+...Warning: To be done in follow up patches after/when/where the main consensus in various items are individually reached.
+
+Xe – Pre-Merge Goals - Completed
+================================
+
Dev_coredump
------------
@@ -222,8 +230,3 @@ Later, when we are in-tree, the goal is to collaborate with devcoredump
infrastructure with overall possible improvements, like multiple file support
for better organization of the dumps, snapshot support, dmesg extra print,
and whatever may make sense and help the overall infrastructure.
-
-Xe – uAPI high level overview
-=============================
-
-...Warning: To be done in follow up patches after/when/where the main consensus in various items are individually reached.
--
2.41.0
next prev parent reply other threads:[~2023-08-29 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 16:30 [PATCH 1/4] drm/doc/rfc: No STAGING out of drivers/staging Rodrigo Vivi
2023-08-29 16:30 ` Rodrigo Vivi [this message]
2023-08-29 16:30 ` [PATCH 3/4] drm/doc/rfc: Mark DRM_VM_BIND as complete Rodrigo Vivi
2023-08-31 19:10 ` Rodrigo Vivi
2023-09-04 21:32 ` Danilo Krummrich
2023-09-06 17:57 ` Rodrigo Vivi
2023-08-29 16:30 ` [PATCH 4/4] drm/doc/rfc: Mark GPU VA " Rodrigo Vivi
2023-08-31 19:17 ` Rodrigo Vivi
2023-09-04 21:39 ` Danilo Krummrich
2023-09-06 18:03 ` Rodrigo Vivi
2023-08-29 17:35 ` [Intel-xe] [PATCH 1/4] drm/doc/rfc: No STAGING out of drivers/staging Lucas De Marchi
2023-08-31 8:31 ` Daniel Vetter
2023-08-31 19:08 ` Rodrigo Vivi
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=20230829163005.54067-2-rodrigo.vivi@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.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