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 4/8] drm/i915: Insert commands for capturing timestamps in the ring
Date: Wed, 5 Aug 2015 09:54:47 +0000 [thread overview]
Message-ID: <1438768630.22294.1.camel@sourabgu-desktop> (raw)
In-Reply-To: <20150805093022.GG10387@nuc-i3427.alporthouse.com>
On Wed, 2015-08-05 at 09:30 +0000, Chris Wilson wrote:
> On Wed, Aug 05, 2015 at 11:25:40AM +0530, sourab.gupta@intel.com wrote:
> > From: Sourab Gupta <sourab.gupta@intel.com>
> >
> > This patch adds the routines through which one can insert commands in the
> > ringbuf for capturing timestamps, which are used to insert these commands
> > around the batchbuffer.
> >
> > While inserting the commands, we keep a reference of associated request.
> > This will be released when we are forwarding the samples to userspace
> > (or when the event is being destroyed).
> > Also, an active reference of the destination buffer is taken here, so that
> > we can be assured that the buffer is freed up only after GPU is done with
> > it, even if the local reference of the buffer is released.
> >
> > v2: Changes (as suggested by Chris):
> > - Passing in 'request' struct for emit report function
> > - Removed multiple calls to i915_gem_obj_to_ggtt(). Keeping hold of
> > pinned vma from start and using when required.
> > - Better nomenclature, and error handling.
> >
> > @@ -919,6 +993,7 @@ static int init_gen_pmu_buffer(struct perf_event *event)
> > dev_priv->gen_pmu.buffer.obj = bo;
> > dev_priv->gen_pmu.buffer.gtt_offset =
> > i915_gem_obj_ggtt_offset(bo);
> > + dev_priv->gen_pmu.buffer.vma = i915_gem_obj_to_ggtt(bo);
> > dev_priv->gen_pmu.buffer.addr = vmap_oa_buffer(bo);
> > INIT_LIST_HEAD(&dev_priv->gen_pmu.node_list);
>
> Still calling i915_gem_obj_to_ggtt(bo) twice! With pmu_buffer.vma you
> can drop pmu_buffer.gtt_offset and never be confused again.
> -Chris
>
Sorry, I'll have the one pertaining to gtt offset removed, and derive
the gtt offset field from the vma only.
_______________________________________________
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:54 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
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 [this message]
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 4/8] drm/i915: Insert commands for capturing timestamps in the ring 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=1438768630.22294.1.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