From: "Gupta, Sourab" <sourab.gupta@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Wu, Jabin" <jabin.wu@intel.com>,
"Woo, Insoo" <insoo.woo@intel.com>
Subject: Re: [RFC 1/8] drm/i915: Add a new PMU for handling non-OA counter data profiling requests
Date: Wed, 5 Aug 2015 09:49:39 +0000 [thread overview]
Message-ID: <1438768320.13551.40.camel@sourabgu-desktop> (raw)
In-Reply-To: <1438768070.13551.38.camel@sourabgu-desktop>
On Wed, 2015-08-05 at 15:17 +0530, sourab gupta wrote:
> On Wed, 2015-08-05 at 09:38 +0000, Chris Wilson wrote:
> > On Wed, Aug 05, 2015 at 11:25:37AM +0530, sourab.gupta@intel.com wrote:
> > > From: Sourab Gupta <sourab.gupta@intel.com>
> > >
> > > The current perf PMU driver is specific for collection of OA counter
> > > statistics (which may be done in a periodic or asynchronous way). Since
> > > this enables us (and limits us) to render ring, we have no means for
> > > collection of data pertaining to other rings.
> > >
> > > To overcome this limitation, we need to have a new PMU driver which enables
> > > data collection for other rings also (in a non-OA specific mode).
> > > This patch adds a new perf PMU to i915 device private, for handling
> > > profiling requests for non-OA counter data.This data may encompass
> > > timestamps, mmio register values, etc. for the relevant ring.
> > > The new perf PMU will serve these purposes, without constraining itself to
> > > type of data being dumped (which may restrict the user to specific ring
> > > like in case of OA counters).
> > >
> > > The patch introduces this PMU driver alongwith its associated callbacks.
> > >
> > > Signed-off-by: Sourab Gupta <sourab.gupta@intel.com>
> > > ---
> > > drivers/gpu/drm/i915/i915_dma.c | 2 +
> > > drivers/gpu/drm/i915/i915_drv.h | 19 ++++
> > > drivers/gpu/drm/i915/i915_oa_perf.c | 215 ++++++++++++++++++++++++++++++++++++
> >
> > You have to admit it is a bit odd for the object to be called
> > i915_oa_pmu/i915_gen_pmu and the file i915_oa_perf.c
> > -Chris
> >
>
> Well, yes.. If the nomenclature of i915_gen_pmu is agreed upon, I can
> have a new file named as i915_gen_pmu.c which will hold the routines for
> this pmu, leaving oa pmu stuff behind in i915_oa_pmu.c
Sorry, I meant to say 'oa pmu stuff behind in i915_oa_perf.c'. Does
i915_gen_pmu.c sound fine?
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-05 9:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 5:55 [RFC 0/8] Introduce framework for forwarding generic non-OA performance sourab.gupta
2015-08-05 5:55 ` [RFC 1/8] drm/i915: Add a new PMU for handling non-OA counter data profiling requests sourab.gupta
2015-08-05 9:22 ` Chris Wilson
2015-08-05 9:40 ` Gupta, Sourab
2015-08-05 9:38 ` Chris Wilson
2015-08-05 9:45 ` Gupta, Sourab
2015-08-05 9:49 ` Gupta, Sourab [this message]
2015-08-05 11:08 ` Chris Wilson
2015-08-05 9:56 ` Chris Wilson
2015-08-05 5:55 ` [RFC 2/8] drm/i915: Add mechanism for forwarding the timestamp data through perf sourab.gupta
2015-08-05 9:55 ` Chris Wilson
2015-08-05 5:55 ` [RFC 3/8] drm/i915: Handle event stop and destroy for GPU commands submitted sourab.gupta
2015-08-05 5:55 ` [RFC 4/8] drm/i915: Insert commands for capturing timestamps in the ring sourab.gupta
2015-08-05 9:30 ` Chris Wilson
2015-08-05 9:54 ` Gupta, Sourab
2015-08-05 5:55 ` [RFC 5/8] drm/i915: Add support for forwarding ring id in sample metadata through perf sourab.gupta
2015-08-05 9:26 ` Chris Wilson
2015-08-05 5:55 ` [RFC 6/8] drm/i915: Add support for forwarding pid in timestamp " sourab.gupta
2015-08-05 5:55 ` [RFC 7/8] drm/i915: Add support for forwarding execbuffer tags in timestamp sample metadata sourab.gupta
2015-08-05 9:17 ` Chris Wilson
2015-08-05 9:29 ` Daniel Vetter
2015-08-05 13:59 ` Robert Bragg
2015-08-05 15:25 ` Daniel Vetter
2015-08-05 16:48 ` Robert Bragg
2015-08-05 5:55 ` [RFC 8/8] drm/i915: Support for retrieving MMIO register values alongwith timestamps through perf sourab.gupta
2015-08-05 10:03 ` Chris Wilson
2015-08-05 10:18 ` Gupta, Sourab
2015-08-05 10:30 ` Chris Wilson
2015-08-05 14:22 ` Gupta, Sourab
2015-08-05 20:19 ` Robert Bragg
-- strict thread matches above, loose matches on Subject: below --
2015-07-15 8:51 [RFC 0/8] Introduce framework for forwarding generic non-OA performance sourab.gupta
2015-07-15 8:51 ` [RFC 1/8] drm/i915: Add a new PMU for handling non-OA counter data profiling requests sourab.gupta
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=1438768320.13551.40.camel@sourabgu-desktop \
--to=sourab.gupta@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=chris@chris-wilson.co.uk \
--cc=insoo.woo@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jabin.wu@intel.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