From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Dong, Zhanjun" <zhanjun.dong@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v18 1/6] drm/xe/guc: Prepare GuC register list and update ADS size for error capture
Date: Mon, 9 Sep 2024 18:23:35 +0000 [thread overview]
Message-ID: <e0e0374734fe7066f132928cdf1dd378ff862291.camel@intel.com> (raw)
In-Reply-To: <20240906222006.279581-2-zhanjun.dong@intel.com>
On Fri, 2024-09-06 at 15:20 -0700, Zhanjun Dong wrote:
> Add referenced registers defines and list of registers.
> Update GuC ADS size allocation to include space for
> the lists of error state capture register descriptors.
>
> Then, populate GuC ADS with the lists of registers we want
> GuC to report back to host on engine reset events. This list
> should include global, engine-class and engine-instance
> registers for every engine-class type on the current hardware.
>
> Ensure we allocate a persistent storage for the register lists
> that are populated into ADS so that we don't need to allocate
> memory during GT resets when GuC is reloaded and ADS population
> happens again.
>
> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
next prev parent reply other threads:[~2024-09-09 18:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 22:20 [PATCH v18 0/6] drm/xe/guc: Add GuC based register capture for error capture Zhanjun Dong
2024-09-06 22:20 ` [PATCH v18 1/6] drm/xe/guc: Prepare GuC register list and update ADS size " Zhanjun Dong
2024-09-09 18:23 ` Teres Alexis, Alan Previn [this message]
2024-09-06 22:20 ` [PATCH v18 2/6] drm/xe/guc: Add XE_LP steered register lists Zhanjun Dong
2024-09-09 18:27 ` Teres Alexis, Alan Previn
2024-09-06 22:20 ` [PATCH v18 3/6] drm/xe/guc: Add capture size check in GuC log buffer Zhanjun Dong
2024-09-06 22:20 ` [PATCH v18 4/6] drm/xe/guc: Extract GuC error capture lists Zhanjun Dong
2024-09-06 22:20 ` [PATCH v18 5/6] drm/xe/guc: Plumb GuC-capture into dev coredump Zhanjun Dong
2024-09-09 23:23 ` Teres Alexis, Alan Previn
2024-09-11 20:07 ` Dong, Zhanjun
2024-09-06 22:20 ` [PATCH v18 6/6] drm/xe/guc: Save manual engine capture into capture list Zhanjun Dong
2024-09-09 23:58 ` Teres Alexis, Alan Previn
2024-09-07 2:18 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add GuC based register capture for error capture (rev18) Patchwork
2024-09-07 2:18 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-07 2:19 ` ✓ CI.KUnit: success " Patchwork
2024-09-07 2:31 ` ✓ CI.Build: " Patchwork
2024-09-07 2:33 ` ✓ CI.Hooks: " Patchwork
2024-09-07 2:35 ` ✓ CI.checksparse: " Patchwork
2024-09-07 3:05 ` ✓ CI.BAT: " Patchwork
2024-09-09 16:37 ` ✗ CI.FULL: failure " Patchwork
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=e0e0374734fe7066f132928cdf1dd378ff862291.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=zhanjun.dong@intel.com \
/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