public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
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 v2 03/11] tools/intel_guc_logger: Add GT-ID selection for intel_guc_logger
Date: Tue, 14 Mar 2023 21:54:06 +0000	[thread overview]
Message-ID: <82e7c0edc082a06cb96fab14eac07287ea12d4dd.camel@intel.com> (raw)
In-Reply-To: <20221206085849.271505-4-alan.previn.teres.alexis@intel.com>

On Tue, 2022-12-06 at 00:58 -0800, Alan Previn wrote:
> With the introduction of MTL and multi-tile products, add a new
> cmd line param for users to select which GT to collect GuC relay
> logs from.
> 
alan:snip
> @@ -538,9 +569,10 @@ static void process_command_line(int argc, char **argv, struct global_t *data)
>  		"  -t --testduration=sec  max duration in seconds for which the logger should run\n"
>  		"  -p --polltimeout=ms    polling timeout in ms, -1 == indefinite wait for the new data\n"
>  		"  -s --size=MB           max size of output file in MBs after which logging will be stopped\n"
> -		"  -d --discard           discard the old/boot-time logs before entering into the capture loop\n";
> +		"  -d --discard           discard the old/boot-time logs before entering into the capture loop\n"
> +		"  -i --gt_id             GT-ID of GuC to capture from, defaults to capture from gt0\n";
>  
> -	igt_simple_init_parse_opts(&argc, argv, "v:o:b:t:p:s:d", long_options,
> +	igt_simple_init_parse_opts(&argc, argv, "v:o:b:t:p:s:d:i", long_options,
alan: when retesting with MTL with both gt's, i realize above is a typo bug ... should have been "v:o:b:t:p:s:di:" ('i' needs the param).

alan:snip


  reply	other threads:[~2023-03-14 21:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  8:58 [igt-dev] [PATCH i-g-t v2 00/11] Resurrect GuC Relay Logging Alan Previn
2022-12-06  8:58 ` [igt-dev] [PATCH i-g-t v2 01/11] tools/intel_guc_logger: Re-enable basic functionality Alan Previn
2023-01-20 20:26   ` [igt-dev] [i-g-t, v2, " Dong, Zhanjun
2023-03-14 21:46     ` Teres Alexis, Alan Previn
2022-12-06  8:58 ` [igt-dev] [PATCH i-g-t v2 02/11] tools/intel_guc_logger: Refactor intel_guc_logger globals into structs Alan Previn
2023-02-01  0:04   ` [igt-dev] [i-g-t, v2, " Dong, Zhanjun
2023-03-14 21:47     ` Teres Alexis, Alan Previn
2022-12-06  8:58 ` [igt-dev] [PATCH i-g-t v2 03/11] tools/intel_guc_logger: Add GT-ID selection for intel_guc_logger Alan Previn
2023-03-14 21:54   ` Teres Alexis, Alan Previn [this message]
2022-12-06  8:58 ` [igt-dev] [PATCH i-g-t v2 04/11] tools/intel_guc_logger: Add helper function for flusher code Alan Previn
2022-12-06  8:58 ` [igt-dev] [PATCH i-g-t v2 05/11] tools/intel_guc_logger: Add GuC Log header structure definition Alan Previn
2022-12-06  8:58 ` [igt-dev] [PATCH i-g-t v2 06/11] tools/intel_guc_logger: Concatenate log samples into a contiguous file Alan Previn
2022-12-06  8:58 ` [igt-dev] [PATCH i-g-t v2 07/11] tools/intel_guc_logger: Add overflow awareness Alan Previn
2022-12-06  8:58 ` [igt-dev] [PATCH i-g-t v2 08/11] tools/intel_guc_logger: Limit relay logging output file to 4GB Alan Previn
2022-12-06  8:58 ` [igt-dev] [PATCH i-g-t v2 09/11] tools/intel_guc_logger: By default don't change GuC log verbosity Alan Previn
2022-12-06  8:58 ` [igt-dev] [PATCH i-g-t v2 10/11] tools/intel_guc_logger: On exit, save any leftover GuC log data Alan Previn
2022-12-06  8:58 ` [igt-dev] [PATCH i-g-t v2 11/11] tools/intel_guc_logger: Add useful debug messages Alan Previn
2022-12-06  9:41 ` [igt-dev] ✓ Fi.CI.BAT: success for Resurrect GuC Relay Logging (rev2) Patchwork
2022-12-06 11:27 ` [igt-dev] ✓ Fi.CI.IGT: " 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=82e7c0edc082a06cb96fab14eac07287ea12d4dd.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