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 v8 3/6] drm/xe/guc: Add capture size check in GuC log buffer
Date: Wed, 8 May 2024 22:57:44 +0000 [thread overview]
Message-ID: <1e1e4d700e6b3cb3f96871c529d1d94413cae468.camel@intel.com> (raw)
In-Reply-To: <20240507014736.1057093-4-zhanjun.dong@intel.com>
On Mon, 2024-05-06 at 18:47 -0700, Zhanjun Dong wrote:
> The capture-nodes is included in GuC log buffer, add the size check
> for capture region in the whole GuC log buffer.
> Check the worst size of register capture aginst error capture region
> size.
>
alan:snip
> +
> +#define GUC_LOG_DEFAULT_CRASH_BUFFER_SIZE CRASH_BUFFER_SIZE
> +#define GUC_LOG_DEFAULT_DEBUG_BUFFER_SIZE DEBUG_BUFFER_SIZE
> +#define GUC_LOG_DEFAULT_CAPTURE_BUFFER_SIZE CAPTURE_BUFFER_SIZE
> +
nit: actually not sure why we need the define on the left, since the
usage could just use the ones its sourced from on the right.
alan: as per offline conversation, we beilieve the default size needs t
to larger to accomodate back to back worst case capture sizes.
So as per offline, we need to increase that to at least 32K? (or 128K
with spare)
next prev parent reply other threads:[~2024-05-08 22:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 1:47 [PATCH v8 0/6] drm/xe/guc: Add GuC based register capture for error capture Zhanjun Dong
2024-05-07 1:47 ` [PATCH v8 1/6] drm/xe/guc: Prepare GuC register list and update ADS size " Zhanjun Dong
2024-05-10 18:43 ` Teres Alexis, Alan Previn
2024-05-14 22:44 ` Dong, Zhanjun
2024-05-10 18:58 ` Teres Alexis, Alan Previn
2024-05-07 1:47 ` [PATCH v8 2/6] drm/xe/guc: Add XE_LP steered register lists Zhanjun Dong
2024-05-11 0:17 ` Teres Alexis, Alan Previn
2024-05-14 23:00 ` Dong, Zhanjun
2024-05-07 1:47 ` [PATCH v8 3/6] drm/xe/guc: Add capture size check in GuC log buffer Zhanjun Dong
2024-05-08 22:57 ` Teres Alexis, Alan Previn [this message]
2024-05-15 21:39 ` Dong, Zhanjun
2024-05-07 1:47 ` [PATCH v8 4/6] drm/xe/guc: Extract GuC error capture lists Zhanjun Dong
2024-05-11 1:43 ` Teres Alexis, Alan Previn
2024-05-15 21:45 ` Dong, Zhanjun
2024-05-15 21:55 ` Dong, Zhanjun
2024-05-07 1:47 ` [PATCH v8 5/6] drm/xe/guc: Pre-allocate output nodes for extraction Zhanjun Dong
2024-05-11 18:07 ` Teres Alexis, Alan Previn
2024-05-07 1:47 ` [PATCH v8 6/6] drm/xe/guc: Plumb GuC-capture into dev coredump Zhanjun Dong
2024-05-11 20:25 ` Teres Alexis, Alan Previn
2024-05-07 4:17 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add GuC based register capture for error capture (rev8) Patchwork
2024-05-07 4:18 ` ✗ CI.checkpatch: warning " Patchwork
2024-05-07 4:19 ` ✓ CI.KUnit: success " Patchwork
2024-05-07 4:31 ` ✓ CI.Build: " Patchwork
2024-05-07 4:41 ` ✗ CI.Hooks: failure " Patchwork
2024-05-07 4:49 ` ✓ CI.checksparse: success " Patchwork
2024-05-07 5:24 ` ✗ CI.BAT: failure " Patchwork
2024-05-07 9:35 ` ✗ CI.FULL: " 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=1e1e4d700e6b3cb3f96871c529d1d94413cae468.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