From: Peter Clifton <pcjc2@cam.ac.uk>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: Corruption in glxgears with Compiz
Date: Sat, 23 Oct 2010 19:33:45 +0100 [thread overview]
Message-ID: <1287858825.4513.3.camel@pcjc2lap> (raw)
In-Reply-To: <5b55a1$ietjas@fmsmga002.fm.intel.com>
On Sat, 2010-10-23 at 18:48 +0100, Chris Wilson wrote:
> We're always eager to improve our code to get the most of our admittedly
> lack-luster GPUs. Even suggests on what tools would be useful or
> improvements we could make to improve profiling/development are most
> welcome.
One thing I was wondering about, was intel_gpu_top. It reports unit
usage based on busy / done registers in the chip. I wondered what would
happen if we polled those registers and graphed them in time... whether
it would show any hints as to which units were waiting on each other,
and where any gaps are.
It would need to be graphical probably, and it would need to be
synchronised in some way to the application / frames being processed, so
all in all, it is rather hard to imagine how it would work with perhaps
unrelated GPU activity going on for other things such as the compositor
and toolkit redrawing.
I sometimes wonder if it is just memory bandwidth constraining things..
perhaps I need to look to the chipset docs and see if there are any
performance diagnostic regs there as well.
--
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)
next prev parent reply other threads:[~2010-10-23 18:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 12:53 Corruption in glxgears with Compiz Peter Clifton
2010-10-22 13:39 ` Chris Wilson
2010-10-22 14:04 ` Alexey Fisher
2010-10-22 19:10 ` Peter Clifton
2010-10-22 19:29 ` Chris Wilson
2010-10-22 19:38 ` Peter Clifton
2010-10-22 20:41 ` Peter Clifton
2010-10-23 3:35 ` Peter Clifton
2010-10-23 4:07 ` Peter Clifton
2010-10-23 8:23 ` Alexey Fisher
2010-10-23 9:10 ` Chris Wilson
2010-10-23 9:43 ` Alexey Fisher
2010-10-23 10:07 ` Chris Wilson
2010-10-23 11:42 ` Peter Clifton
2010-10-23 17:48 ` Chris Wilson
2010-10-23 18:33 ` Peter Clifton [this message]
2010-10-24 23:06 ` Peter Clifton
2010-10-22 19:13 ` 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=1287858825.4513.3.camel@pcjc2lap \
--to=pcjc2@cam.ac.uk \
--cc=chris@chris-wilson.co.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 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.