Re: [PATCH i-g-t 2/2] tools/intel_error_decode: Correctly name the GuC CT buffer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 25 Apr 2023 13:19:26 -0700, John.C.Harrison@xxxxxxxxx wrote:
>
> From: John Harrison <John.C.Harrison@xxxxxxxxx>
>
> 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@xxxxxxxxx>

>
> Signed-off-by: John Harrison <John.C.Harrison@xxxxxxxxx>
> ---
>  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
>



[Index of Archives]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux