From: Ben Widawsky <ben@bwidawsk.net>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 6/6] drm/i915: Convert the register access tracepoint to be conditional
Date: Sun, 14 Jul 2013 13:28:11 -0700 [thread overview]
Message-ID: <20130714202810.GD24025@bwidawsk.net> (raw)
In-Reply-To: <1373648907-28774-6-git-send-email-chris@chris-wilson.co.uk>
On Fri, Jul 12, 2013 at 06:08:27PM +0100, Chris Wilson wrote:
> The TRACE_EVENT_CONDITION is supposed to generate more efficient code
> than if (cond) trace(), which is what we are currently using inside the
> register access functions.
>
> v2: Rebase onto uncore
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
One thing I've thought about this is a trace_on_once, or trace_on_poll
would be cool for polled reads. Obviously we can post-process it, but we
always risk losing events if we fill up too much of the ringbuffer with
stuff we don't care about.
In any case, I very much like the condition added to the trace itself,
and reading probably the same docs as you agree it should be faster.
Looking over our code. It looks like I missed trace events when writing
the PTEs in i915_gem_gtt.c. Can you get around to fixing those up?
[snip]
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-07-14 20:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 17:08 [PATCH 1/6] drm/i915: Colocate all GT access routines in the same file Chris Wilson
2013-07-12 17:08 ` [PATCH 2/6] drm/i915: Use a private interface for register access within GT Chris Wilson
2013-07-14 19:48 ` Ben Widawsky
2013-07-16 16:18 ` Chris Wilson
2013-07-12 17:08 ` [PATCH 3/6] drm/i915: Use the common register access functions for NOTRACE variants Chris Wilson
2013-07-12 17:08 ` [PATCH 4/6] drm/i915: Serialize all register access Chris Wilson
2013-07-14 20:23 ` Ben Widawsky
2013-07-16 16:16 ` Chris Wilson
2013-07-12 17:08 ` [PATCH 5/6] drm/i915: Squash gen lookup through multiple indirections inside GT access Chris Wilson
2013-07-12 17:08 ` [PATCH 6/6] drm/i915: Convert the register access tracepoint to be conditional Chris Wilson
2013-07-14 20:28 ` Ben Widawsky [this message]
2013-07-16 16:09 ` Chris Wilson
2013-07-12 17:56 ` [PATCH 1/6] drm/i915: Colocate all GT access routines in the same file Ben Widawsky
2013-07-12 19:21 ` Chris Wilson
2013-07-14 19:42 ` Ben Widawsky
2013-07-14 20:37 ` Chris Wilson
2013-07-15 19:04 ` Paulo Zanoni
-- strict thread matches above, loose matches on Subject: below --
2013-07-19 19:36 [PATCH 1/6] drm/i915: Serialize almost all register access Chris Wilson
2013-07-19 19:36 ` [PATCH 6/6] drm/i915: Convert the register access tracepoint to be conditional Chris Wilson
2013-07-25 8:48 ` Daniel Vetter
2013-07-16 19:02 [PATCH 1/6] drm/i915: Colocate all GT access routines in the same file Chris Wilson
2013-07-16 19:02 ` [PATCH 6/6] drm/i915: Convert the register access tracepoint to be conditional Chris Wilson
2013-07-12 14:59 [PATCH 1/6] drm/i915: Colocate all GT access routines in the same file Chris Wilson
2013-07-12 14:59 ` [PATCH 6/6] drm/i915: Convert the register access tracepoint to be conditional Chris Wilson
2013-07-12 14:02 [PATCH 1/6] drm/i915: Colocate all GT access routines in the same file Chris Wilson
2013-07-12 14:02 ` [PATCH 6/6] drm/i915: Convert the register access tracepoint to be conditional Chris Wilson
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=20130714202810.GD24025@bwidawsk.net \
--to=ben@bwidawsk.net \
--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.