Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Peter Clifton <pcjc2@cam.ac.uk>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: INSTDONE instrumentation (patch in progress)
Date: Sun, 31 Oct 2010 08:10:46 +0000	[thread overview]
Message-ID: <b9dded$gui02n@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1288491846.2886.12.camel@pcjc2lap>

On Sun, 31 Oct 2010 02:24:06 +0000, Peter Clifton <pcjc2@cam.ac.uk> wrote:
> Hi guys,
> 
> I thought I'd attach this, as it is now gone 2AM and I doubt I'm going
> to finish it "tonight". I was hoping to elicit some initial review to
> suggest whether the design was sane or not.

Been here, done something similar and ripped it out. What we want to do is
integrate an additional set of sampling with perf. The last time I looked,
it required a few extra lines to perf-core to allow devices to register
their own counters, and then you get the advantage of a reasonable
interface (plus the integration with CPU profiling and timecharts etc).
 
> I'd originally imagined tying the profiling lifetime to the execution /
> completion of individual batch-buffers, but for now I'd like to get it
> partly working like this, and perhaps develop some user-space program to
> view the results and see if they make sense.

You can use the current trace points to get timings for
submit + complete + retire. What's missing here is being able to mark
individual batch buffers for profiling. I think adding a new TIMING_FENCE
ioctl (it could just be a fence ;-) that capture various stats at the
point of submission and completion and then fired off an event (to be read
on the /dev/dri/card0 fd) would be the more flexible solution.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31  2:24 INSTDONE instrumentation (patch in progress) Peter Clifton
2010-10-31  8:10 ` Chris Wilson [this message]
2010-10-31 15:04   ` 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='b9dded$gui02n@orsmga002.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=pcjc2@cam.ac.uk \
    /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