From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"sashiko-reviews@lists.linux.dev"
<sashiko-reviews@lists.linux.dev>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v10 3/3] drm/xe/guc: Add dump_cache to optimize GuC CT/Log compression flow
Date: Tue, 13 Oct 2026 21:18:43 +0000 [thread overview]
Message-ID: <c07dd84dd81bf3a645fd2a6ef860bef944d1ca7e.camel@intel.com> (raw)
In-Reply-To: <as6HwRY4HvjFPB7N@intel.com>
On Tue, 2026-10-13 at 15:34 -0400, Rodrigo Vivi wrote:
> On Tue, Oct 06, 2026 at 06:04:57PM +0000, sashiko-bot@kernel.org wrote:
> > Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> > - [High] locking: Sleeping in atomic context when freeing vmalloc'd dump cache under spinlock
>
> perhaps worth splitting this series and resending patches 1 and 2 for merging
> them? while refactoring this one?
>
alan: depending on the direction, we might need a fixup on patch2. apologies for the delay... will fix this ASAP.
next prev parent reply other threads:[~2026-10-13 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 17:51 [PATCH v10 0/3] drm/xe/guc: Compress GuC log and CTB dump with zstd Alan Previn
2026-10-06 17:51 ` [PATCH v10 1/3] drm/xe: Remove extra newlines from LRC snapshot dump Alan Previn
2026-10-06 17:51 ` [PATCH v10 2/3] drm/xe/guc: Compress GuC log and CTB dump with zstd Alan Previn
2026-10-06 17:51 ` [PATCH v10 3/3] drm/xe/guc: Add dump_cache to optimize GuC CT/Log compression flow Alan Previn
2026-10-06 18:04 ` sashiko-bot
2026-10-13 19:34 ` Rodrigo Vivi
2026-10-13 21:18 ` Teres Alexis, Alan Previn [this message]
2026-10-06 17:57 ` ✗ CI.checkpatch: warning for drm/xe/guc: Compress GuC log and CTB dump with zstd (rev6) Patchwork
2026-10-06 17:59 ` ✓ CI.KUnit: success " Patchwork
2026-10-06 18:16 ` ✗ CI.checksparse: warning " Patchwork
2026-10-06 18:39 ` ✓ Xe.CI.BAT: success " Patchwork
2026-10-06 23:46 ` ✗ Xe.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=c07dd84dd81bf3a645fd2a6ef860bef944d1ca7e.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=sashiko-reviews@lists.linux.dev \
/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