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 v15 3/5] drm/xe/guc: Add capture size check in GuC log buffer
Date: Thu, 8 Aug 2024 19:05:15 +0000 [thread overview]
Message-ID: <f595c8370110e71082801f3a08bf6c0e254819b6.camel@intel.com> (raw)
In-Reply-To: <20240806145704.165231-4-zhanjun.dong@intel.com>
alan: everything looks good to me except for one unused function per below.
I'll give you a conditional-rb please ensure remove that on the next rev.
Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
...alan
On Tue, 2024-08-06 at 07:57 -0700, Zhanjun Dong wrote:
> Capture-nodes generated by GuC are placed in the GuC capture ring
> buffer which is a sub-region of the larger Guc-Log-buffer.
> Add capture output size check before allocating the shared buffer.
>
>
alan:snip
> diff --git a/drivers/gpu/drm/xe/xe_guc_log.c b/drivers/gpu/drm/xe/xe_guc_log.c
> index a37ee3419428..250696df92cc 100644
> --- a/drivers/gpu/drm/xe/xe_guc_log.c
> +++ b/drivers/gpu/drm/xe/xe_guc_log.c
> @@ -12,6 +12,11 @@
> #include "xe_map.h"
> #include "xe_module.h"
>
> +static inline struct xe_guc *log_to_guc(struct xe_guc_log *log)
> +{
> + return container_of(log, struct xe_guc, log);
> +}
alan: (conditional-rb) please remove this function since i dont see it being used anywhere in the entire series.
alan:snip
> #endif
next prev parent reply other threads:[~2024-08-08 19:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 14:56 [PATCH v15 0/5] drm/xe/guc: Add GuC based register capture for error capture Zhanjun Dong
2024-08-06 14:57 ` [PATCH v15 1/5] drm/xe/guc: Prepare GuC register list and update ADS size " Zhanjun Dong
2024-08-08 22:58 ` Teres Alexis, Alan Previn
2024-08-06 14:57 ` [PATCH v15 2/5] drm/xe/guc: Add XE_LP steered register lists Zhanjun Dong
2024-08-06 14:57 ` [PATCH v15 3/5] drm/xe/guc: Add capture size check in GuC log buffer Zhanjun Dong
2024-08-08 19:05 ` Teres Alexis, Alan Previn [this message]
2024-08-06 14:57 ` [PATCH v15 4/5] drm/xe/guc: Extract GuC error capture lists Zhanjun Dong
2024-08-06 14:57 ` [PATCH v15 5/5] drm/xe/guc: Plumb GuC-capture into dev coredump Zhanjun Dong
2024-08-06 15:02 ` ✓ CI.Patch_applied: success for drm/xe/guc: Add GuC based register capture for error capture (rev15) Patchwork
2024-08-06 15:03 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-06 15:04 ` ✓ CI.KUnit: success " Patchwork
2024-08-06 15:16 ` ✓ CI.Build: " Patchwork
2024-08-06 15:20 ` ✓ CI.Hooks: " Patchwork
2024-08-06 15:22 ` ✓ CI.checksparse: " Patchwork
2024-08-06 15:42 ` ✓ CI.BAT: " Patchwork
2024-08-06 17: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=f595c8370110e71082801f3a08bf6c0e254819b6.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