From: Dave Gordon <david.s.gordon@intel.com>
To: Jaeyong Yoo <jaeyong.yoo@samsung.com>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org
Subject: Re: Debugging registers (INSTPS, CSCMDOP, CSCMDVLD, ...)
Date: Mon, 19 Jan 2015 13:31:35 +0000 [thread overview]
Message-ID: <54BD0737.3060207@intel.com> (raw)
In-Reply-To: <004c01d03096$436d2b40$ca4781c0$%yoo@samsung.com>
On 15/01/15 07:38, Jaeyong Yoo wrote:
> Hello Daniel and other maintainers,
>
> While I'm working on drm memory allocator with myself, I've encountered render ring hang.
> And I am noticed that I can diagnose the command streamer's status with the following registers:
>
> INSTPS: 0x2070
> CSCMDOP: 0x220c
> CSCMDVLD: 0x2210
> INSTDONE_1: 206C
>
> I can see the general description of such registers in the following PDF.
> http://www.x.org/docs/intel/VOL_1_graphics_core.pdf
>
> But, sadly, this document does not provide a field description for implementation specific registers.
> I appreciate if you point me to such information in Haswell architecture?
>
> Best regards,
> JY
> _________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Hi,
that link you provided looks pretty ancient -- the document is dated Jan
2008! There's a lot of much more recent documentation at
* https://01.org/linuxgraphics/documentation
including some Haswell-specific files at:
*
https://01.org/linuxgraphics/documentation/2013-intel-core-processor-family
If you are trying to diagnose a GPU hang, these may be useful:
* https://01.org/linuxgraphics/documentation/how-get-gpu-error-state
* https://01.org/linuxgraphics/documentation/intel-gpu-dump-tool-guide
Hope this helps,
.Dave.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-01-19 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 12:26 Question regarding forcewake in i915 유재용
2015-01-06 15:19 ` Dave Gordon
2015-01-07 8:13 ` Jaeyong Yoo
2015-01-12 17:47 ` Dave Gordon
2015-01-15 7:38 ` Debugging registers (INSTPS, CSCMDOP, CSCMDVLD, ...) Jaeyong Yoo
2015-01-19 12:52 ` Dave Gordon
2015-01-19 13:31 ` Dave Gordon [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=54BD0737.3060207@intel.com \
--to=david.s.gordon@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jaeyong.yoo@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox