Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Clifton <pcjc2@cam.ac.uk>
To: intel-gfx@lists.freedesktop.org
Subject: High-resolution intel_gpu_top output
Date: Fri, 29 Oct 2010 18:31:44 +0100	[thread overview]
Message-ID: <1288373504.27413.8.camel@pcjc2lap> (raw)

[-- Attachment #1: Type: text/plain, Size: 1804 bytes --]

Hi guys,

Would a utility to produce views such as the attached help debug
performance bottlenecks?

I took intel_gpu_top, ripped out all the bargraph and sorting code, then
taught it to spit out a CSV file.

For the graph below, I took data for a fraction of a second, sampling
with no delays (just IO delays in the redirected printf), with 50
samples per data-point working out a percentage figure.

For my benchmark application, I inserted a delay of approx 10ms into the
benchmark loop, so frames could easily be identified in the output
trace.

The pdf attached shows a zoomed in portion of rendering time of one
particular frame. I'll note that outside this view, there are some short
stalls in the frame which probably indicates my app could do better at
keeping the GPU busy with data.

What I'm seeing, is:

 a pretty busy / stalled render cache      (not always at 100%),
 a pretty busy / stalled windowizer (iz)   (not always at 100%),
 a pretty busy / stalled GS unit           (nearly always 100%)
 a pretty busy / stalled CLIP unit         (nearly always 100%)
 a fully busy / stalled CS unit            (almost always 100%)

Regarding the other units, I'd _really_ love if someone at Intel could
identify the meanings / functions of the other less well known acronym
identified flags in the instdone registers. What is "DM" for instance?

Sadly Openoffice is awful at graphing this large quantity of data, so is
really slow. If anyone wants the data-file, the tool's source-code or OO
Spreadsheet, let me know and I'll send them.

Regards

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)

[-- Attachment #2: gpu_top2.pdf --]
[-- Type: application/pdf, Size: 41680 bytes --]

[-- Attachment #3: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2010-10-29 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 17:31 Peter Clifton [this message]
     [not found] ` <1288393688.1156.15.camel@pcjc2lap>
2010-10-29 23:17   ` High-resolution intel_gpu_top output Peter Clifton

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=1288373504.27413.8.camel@pcjc2lap \
    --to=pcjc2@cam.ac.uk \
    --cc=intel-gfx@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