From: Michel Thierry <michel.thierry@intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/3] tools/intel_error_decode: Add gen8+ fault data encodings
Date: Wed, 25 Mar 2015 16:47:12 +0000 [thread overview]
Message-ID: <5512E690.9020600@intel.com> (raw)
In-Reply-To: <1427290932-5156-3-git-send-email-mika.kuoppala@intel.com>
On 3/25/2015 1:42 PM, Mika Kuoppala wrote:
> These two registers contains the 48bit fault address.
>
> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
> ---
> tools/intel_error_decode.c | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git a/tools/intel_error_decode.c b/tools/intel_error_decode.c
> index 553307f..7c32fc3 100644
> --- a/tools/intel_error_decode.c
> +++ b/tools/intel_error_decode.c
> @@ -401,6 +401,19 @@ print_fault_reg(unsigned devid, uint32_t reg)
> printf(" Address 0x%08x\n", reg & ~((1 << 12)-1));
> }
The code above is different in v2 of the previous patch, so it won't
apply cleanly...
>
> +static void
> +print_fault_data(unsigned devid, uint32_t data1, uint32_t data0)
> +{
> + uint64_t address;
> +
> + if (intel_gen(devid) < 8)
> + return;
> +
> + address = ((uint64_t)(data0) << 12) | ((uint64_t)data1 & 0xf) << 44;
> + printf(" Address 0x%016" PRIx64 " %s\n", address,
> + data1 & (1 << 4) ? "GGTT" : "PPGTT");
> +}
> +
> #define MAX_RINGS 10 /* I really hope this never... */
> uint32_t head[MAX_RINGS];
> int head_ndx = 0;
> @@ -482,7 +495,7 @@ read_data_file(FILE *file)
>
> matched = sscanf(line, "%08x : %08x", &offset, &value);
> if (matched != 2) {
> - unsigned int reg;
> + unsigned int reg, reg2;
>
> /* display reg section is after the ringbuffers, don't mix them */
> decode(decode_ctx, is_batch, ring_name, gtt_offset,
> @@ -545,6 +558,10 @@ read_data_file(FILE *file)
> if (matched == 1 && reg)
> print_fault_reg(devid, reg);
>
> + matched = sscanf(line, " FAULT_TLB_DATA: 0x%08x 0x%08x\n", ®, ®2);
> + if (matched == 2)
> + print_fault_data(devid, reg, reg2);
> +
> continue;
> }
>
> --
> 1.9.1
>
Anyway,
Reviewed-by: Michel Thierry <michel.thierry@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-25 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 13:42 [PATCH 1/3] tools/intel_error_decode: Add ERROR decodings for gen8 Mika Kuoppala
2015-03-25 13:42 ` [PATCH 2/3] tools/intel_error_decode: Add decodings for FAULT_REG Mika Kuoppala
2015-03-25 16:13 ` Mika Kuoppala
2015-03-25 16:46 ` Michel Thierry
2015-03-25 13:42 ` [PATCH 3/3] tools/intel_error_decode: Add gen8+ fault data encodings Mika Kuoppala
2015-03-25 16:47 ` Michel Thierry [this message]
2015-03-25 16:46 ` [PATCH 1/3] tools/intel_error_decode: Add ERROR decodings for gen8 Michel Thierry
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=5512E690.9020600@intel.com \
--to=michel.thierry@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.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.