From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: John.C.Harrison@Intel.com
Cc: IGT-Dev@Lists.FreeDesktop.Org, Intel-GFX@Lists.FreeDesktop.Org
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t 2/2] tools/intel_error_decode: Correctly name the GuC CT buffer
Date: Wed, 26 Apr 2023 14:49:40 -0700 [thread overview]
Message-ID: <875y9i9uvf.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230425201926.99086-3-John.C.Harrison@Intel.com>
On Tue, 25 Apr 2023 13:19:26 -0700, John.C.Harrison@Intel.com wrote:
>
> From: John Harrison <John.C.Harrison@Intel.com>
>
> The buffer decoding code doesn't cope well with unknown buffers. So
> add an entry for the GuC CTB so that it gets decoded correctly.
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> ---
> tools/intel_error_decode.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/intel_error_decode.c b/tools/intel_error_decode.c
> index 99680bedc785..451608826be3 100644
> --- a/tools/intel_error_decode.c
> +++ b/tools/intel_error_decode.c
> @@ -617,6 +617,7 @@ read_data_file(FILE *file)
> { "user", "user", 0 },
> { "semaphores", "semaphores", 0 },
> { "guc log buffer", "GuC log", 0 },
> + { "guc ct buffer", "GuC CTB", 0 },
> { },
> }, *b;
> char *new_ring_name;
> --
> 2.39.1
>
WARNING: multiple messages have this Message-ID (diff)
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: John.C.Harrison@Intel.com
Cc: IGT-Dev@Lists.FreeDesktop.Org, Intel-GFX@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH i-g-t 2/2] tools/intel_error_decode: Correctly name the GuC CT buffer
Date: Wed, 26 Apr 2023 14:49:40 -0700 [thread overview]
Message-ID: <875y9i9uvf.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230425201926.99086-3-John.C.Harrison@Intel.com>
On Tue, 25 Apr 2023 13:19:26 -0700, John.C.Harrison@Intel.com wrote:
>
> From: John Harrison <John.C.Harrison@Intel.com>
>
> The buffer decoding code doesn't cope well with unknown buffers. So
> add an entry for the GuC CTB so that it gets decoded correctly.
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> ---
> tools/intel_error_decode.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/intel_error_decode.c b/tools/intel_error_decode.c
> index 99680bedc785..451608826be3 100644
> --- a/tools/intel_error_decode.c
> +++ b/tools/intel_error_decode.c
> @@ -617,6 +617,7 @@ read_data_file(FILE *file)
> { "user", "user", 0 },
> { "semaphores", "semaphores", 0 },
> { "guc log buffer", "GuC log", 0 },
> + { "guc ct buffer", "GuC CTB", 0 },
> { },
> }, *b;
> char *new_ring_name;
> --
> 2.39.1
>
next prev parent reply other threads:[~2023-04-26 21:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 20:19 [Intel-gfx] [PATCH i-g-t 0/2] Update intel_error_decode for Gen12 John.C.Harrison
2023-04-25 20:19 ` [Intel-gfx] [PATCH i-g-t 1/2] lib/intel_decode: Decode Gen12 ring/batch instructions correctly John.C.Harrison
2023-04-26 21:51 ` [igt-dev] " Dixit, Ashutosh
2023-04-26 21:51 ` Dixit, Ashutosh
2023-05-01 19:44 ` [igt-dev] " John Harrison
2023-05-01 19:44 ` John Harrison
2023-05-01 20:01 ` [igt-dev] " Dixit, Ashutosh
2023-05-01 20:01 ` Dixit, Ashutosh
2023-04-25 20:19 ` [Intel-gfx] [PATCH i-g-t 2/2] tools/intel_error_decode: Correctly name the GuC CT buffer John.C.Harrison
2023-04-26 21:49 ` Dixit, Ashutosh [this message]
2023-04-26 21:49 ` Dixit, Ashutosh
2023-04-25 22:25 ` [igt-dev] ✗ Fi.CI.BAT: failure for Update intel_error_decode for Gen12 Patchwork
2023-05-01 20:46 ` [igt-dev] ✓ Fi.CI.BAT: success for Update intel_error_decode for Gen12 (rev2) Patchwork
2023-05-01 22:12 ` [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=875y9i9uvf.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=IGT-Dev@Lists.FreeDesktop.Org \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.