From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 0/2] Resurrect GuC Relay Logging
Date: Tue, 6 Dec 2022 02:10:52 +0000 [thread overview]
Message-ID: <194726c19078bea070c09ecc70726d11647c2fad.camel@intel.com> (raw)
In-Reply-To: <20220509212128.1844629-1-alan.previn.teres.alexis@intel.com>
Alan: As i attempt to revive this series, i need to add 1 or 2 patches to allow guc log relay logging to work with
different gt's.
On Mon, 2022-05-09 at 14:21 -0700, Alan Previn wrote:
> This series brings GuC relay logging back to life by
> re-aligning the (previously implicit, now query-able)
> guc-log-relay subbuffer-specs, debugfs file handle names
> and usages between intel_guc_logger tool and i915.
>
> This series depends on fixes and updates on the
> kernel side via this series:
> https://patchwork.freedesktop.org/series/103767/
>
>
Alan:[snip]
prev parent reply other threads:[~2022-12-06 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 21:21 [igt-dev] [PATCH i-g-t 0/2] Resurrect GuC Relay Logging Alan Previn
2022-05-09 21:21 ` [igt-dev] [PATCH i-g-t 1/2] tools/intel_guc_logger: Re-enable basic functionality Alan Previn
2022-07-19 21:35 ` Teres Alexis, Alan Previn
2022-05-09 21:21 ` [igt-dev] [PATCH i-g-t 2/2] tools/intel_guc_logger: Refactor intel_guc_logger globals into structs Alan Previn
2022-05-09 22:12 ` [igt-dev] ✓ Fi.CI.BAT: success for Resurrect GuC Relay Logging Patchwork
2022-05-10 10:14 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-12-06 2:10 ` Teres Alexis, Alan Previn [this message]
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=194726c19078bea070c09ecc70726d11647c2fad.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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