From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: John Harrison <john.c.harrison@intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Badal Nilawar <badal.nilawar@intel.com>,
<intel-xe@lists.freedesktop.org>, <anshuman.gupta@intel.com>
Subject: Re: [CI 00/12] Debug g2h timeout issue
Date: Thu, 26 Sep 2024 14:55:04 -0400 [thread overview]
Message-ID: <ZvWuCCBBJIFuQNFj@intel.com> (raw)
In-Reply-To: <d3db53f4-e061-4b4a-b90b-93687ad2fdfb@intel.com>
On Mon, Sep 23, 2024 at 12:45:18PM -0700, John Harrison wrote:
> On 9/20/2024 07:48, Jani Nikula wrote:
> > On Fri, 20 Sep 2024, Badal Nilawar <badal.nilawar@intel.com> wrote:
> > > Do not review
> > Explanation would go here.
> >
> > [CI] Usually means everything's reviewed, and this is just a resend for
> > CI. And there's no need to resend multiple times for that. Patchwork has
> > a "test again" button.
> >
> > Finally, the patches are missing your Signed-off-by.
> >
> > BR,
> > Jani.
> I think the intention here is to just get extra CI runs with more debug
> output to debug a failure that is only happening inside CI and cannot be
> reproduced locally. Although it is generally simpler/clearer to just squash
> the patches down into a single "Add extra debug for CI failures" patch
> rather than re-submitting an entire series.
>
> Of course, the ideal would be to actually get all this extremely useful
> stuff merged and then it wouldn't need to be reposted over and over to get
> more CI results with it enabled.
yeap, the lack of try-bot in xe side. But yes, next time please squash them all...
>
> John.
>
>
> >
> > > John Harrison (10):
> > > drm/xe/guc: Remove spurious line feed in debug print
> > > drm/xe/devcoredump: Use drm_puts and already cached local variables
> > > drm/xe/devcoredump: Improve section headings and add tile info
> > > drm/xe/devcoredump: Add ASCII85 dump helper function
> > > drm/xe/guc: Copy GuC log prior to dumping
> > > drm/xe/guc: Use a two stage dump for GuC logs and add more info
> > > drm/xe/guc: Dead CT helper
> > > drm/xe/guc: Dump entire CTB on errors
> > > drm/xe/guc: Add GuC log to devcoredump captures
> > > drm/xe/guc: Add a helper function for dumping GuC log to dmesg
> > >
> > > Michal Wajdeczko (1):
> > > drm/print: Introduce drm_line_printer
> > >
> > > bnilawar (1):
> > > [For CI] Debug prints/logs to debug G2H timeout issue
> > >
> > > drivers/gpu/drm/drm_print.c | 14 +
> > > .../drm/xe/abi/guc_communication_ctb_abi.h | 1 +
> > > drivers/gpu/drm/xe/regs/xe_guc_regs.h | 1 +
> > > drivers/gpu/drm/xe/xe_devcoredump.c | 144 +++++-
> > > drivers/gpu/drm/xe/xe_devcoredump.h | 6 +
> > > drivers/gpu/drm/xe/xe_devcoredump_types.h | 13 +-
> > > drivers/gpu/drm/xe/xe_device.c | 1 +
> > > drivers/gpu/drm/xe/xe_guc.c | 6 +-
> > > drivers/gpu/drm/xe/xe_guc_ct.c | 416 ++++++++++++++----
> > > drivers/gpu/drm/xe/xe_guc_ct.h | 10 +-
> > > drivers/gpu/drm/xe/xe_guc_ct_types.h | 29 +-
> > > drivers/gpu/drm/xe/xe_guc_log.c | 208 ++++++++-
> > > drivers/gpu/drm/xe/xe_guc_log.h | 5 +
> > > drivers/gpu/drm/xe/xe_guc_log_types.h | 27 ++
> > > drivers/gpu/drm/xe/xe_guc_submit.c | 2 +-
> > > drivers/gpu/drm/xe/xe_hw_engine.c | 1 -
> > > include/drm/drm_print.h | 64 +++
> > > 17 files changed, 804 insertions(+), 144 deletions(-)
>
next prev parent reply other threads:[~2024-09-26 18:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 14:29 [CI 00/12] Debug g2h timeout issue Badal Nilawar
2024-09-20 14:29 ` [CI 01/12] drm/xe/guc: Remove spurious line feed in debug print Badal Nilawar
2024-09-20 14:29 ` [CI 02/12] drm/xe/devcoredump: Use drm_puts and already cached local variables Badal Nilawar
2024-09-20 14:29 ` [CI 03/12] drm/xe/devcoredump: Improve section headings and add tile info Badal Nilawar
2024-09-20 14:29 ` [CI 04/12] drm/xe/devcoredump: Add ASCII85 dump helper function Badal Nilawar
2024-09-20 14:29 ` [CI 05/12] drm/xe/guc: Copy GuC log prior to dumping Badal Nilawar
2024-09-20 14:29 ` [CI 06/12] drm/xe/guc: Use a two stage dump for GuC logs and add more info Badal Nilawar
2024-09-20 14:29 ` [CI 07/12] drm/print: Introduce drm_line_printer Badal Nilawar
2024-09-20 14:29 ` [CI 08/12] drm/xe/guc: Dead CT helper Badal Nilawar
2024-09-20 14:29 ` [CI 09/12] drm/xe/guc: Dump entire CTB on errors Badal Nilawar
2024-09-20 14:29 ` [CI 10/12] drm/xe/guc: Add GuC log to devcoredump captures Badal Nilawar
2024-09-20 14:29 ` [CI 11/12] drm/xe/guc: Add a helper function for dumping GuC log to dmesg Badal Nilawar
2024-09-20 14:29 ` [CI 12/12] [For CI] Debug prints/logs to debug G2H timeout issue Badal Nilawar
2024-09-23 17:09 ` John Harrison
2024-09-20 14:48 ` [CI 00/12] Debug g2h " Jani Nikula
2024-09-23 19:45 ` John Harrison
2024-09-26 18:55 ` Rodrigo Vivi [this message]
2024-09-27 17:50 ` Nilawar, Badal
2024-09-20 15:24 ` ✓ CI.Patch_applied: success for " Patchwork
2024-09-20 15:24 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-20 15:25 ` ✓ CI.KUnit: success " Patchwork
2024-09-20 15:37 ` ✓ CI.Build: " Patchwork
2024-09-20 15:39 ` ✓ CI.Hooks: " Patchwork
2024-09-20 15:41 ` ✗ CI.checksparse: warning " Patchwork
2024-09-20 16:10 ` ✓ CI.BAT: success " Patchwork
2024-09-20 21:21 ` ✓ CI.FULL: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-09-20 14:06 [[CI] 00/12] " bnilawar
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=ZvWuCCBBJIFuQNFj@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=john.c.harrison@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