From: Ingo Molnar <mingo@kernel.org>
To: Robert Bragg <robert@sixbynine.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Chris Wilson <chris@chris-wilson.co.uk>,
Rob Clark <robdclark@gmail.com>,
Samuel Pitoiset <samuel.pitoiset@gmail.com>,
Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [RFC PATCH 0/3] Expose gpu counters via perf pmu driver
Date: Thu, 23 Oct 2014 07:58:25 +0200 [thread overview]
Message-ID: <20141023055825.GA4559@gmail.com> (raw)
In-Reply-To: <1413991731-20628-1-git-send-email-robert@sixbynine.org>
* Robert Bragg <robert@sixbynine.org> wrote:
> [...]
>
> I'd be interested to hear whether is sounds reasonable to
> others for us to expose gpu device metrics via a perf pmu and
> whether adding the PERF_PMU_CAP_IS_DEVICE flag as in my
> following patch could be acceptable.
I think it's perfectly reasonable, it's one of the interesting
kernel features I hoped for years would be implemented for perf.
> [...]
>
> In addition I also explicitly black list numerous attributes
> and PERF_SAMPLE_ flags that I don't think make sense for a
> device pmu. This could be handled in the pmu driver but it
> seemed better to do in events/core, avoiding duplication in
> case we later have multiple device pmus.
Btw., if the GPU is able to dump (part of) its current execution
status, you could in theory even do instruction profiling and
in-GPU profiling (symbol resolution, maybe even annotation, etc.)
with close to standard perf tooling - which I think is currently
mostly the domain of proprietary tools.
Thanks,
Ingo
next prev parent reply other threads:[~2014-10-23 5:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 15:28 [RFC PATCH 0/3] Expose gpu counters via perf pmu driver Robert Bragg
2014-10-22 15:28 ` [RFC PATCH 1/3] perf: export perf_event_overflow Robert Bragg
2014-10-22 15:28 ` [RFC PATCH 2/3] perf: Add PERF_PMU_CAP_IS_DEVICE flag Robert Bragg
2014-10-22 15:28 ` [RFC PATCH 3/3] i915: Expose PMU for Observation Architecture Robert Bragg
2014-10-23 7:47 ` Chris Wilson
2014-10-24 2:33 ` Robert Bragg
2014-10-24 6:56 ` Chris Wilson
2014-10-23 5:58 ` Ingo Molnar [this message]
2014-10-24 13:39 ` [RFC PATCH 0/3] Expose gpu counters via perf pmu driver Robert Bragg
2014-10-30 19:08 ` Peter Zijlstra
2014-11-03 21:47 ` Robert Bragg
2014-11-05 12:33 ` Peter Zijlstra
2014-11-06 0:37 ` Robert Bragg
2014-11-10 11:13 ` Ingo Molnar
2014-11-12 23:33 ` Robert Bragg
2014-11-16 9:27 ` Ingo Molnar
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=20141023055825.GA4559@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=bskeggs@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=robdclark@gmail.com \
--cc=robert@sixbynine.org \
--cc=samuel.pitoiset@gmail.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;
as well as URLs for NNTP newsgroup(s).