From: Robert Bragg <robert@sixbynine.org>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v2 0/5] drm/i915/perf: Improve handling of OA tail race
Date: Fri, 27 Jan 2017 09:42:00 -0800 [thread overview]
Message-ID: <20170127174205.15325-1-robert@sixbynine.org> (raw)
Folds in Matthew Auld's feedback; thanks.
Robert Bragg (5):
drm/i915/perf: fix gen7_append_oa_reports comment
drm/i915/perf: avoid poll, read, EAGAIN busy loops
drm/i915/perf: avoid read back of head register
drm/i915/perf: no head/tail ref in gen7_oa_read
drm/i915/perf: improve tail race workaround
drivers/gpu/drm/i915/i915_drv.h | 71 +++++++-
drivers/gpu/drm/i915/i915_perf.c | 344 ++++++++++++++++++++++++---------------
2 files changed, 281 insertions(+), 134 deletions(-)
--
2.11.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2017-01-27 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 17:42 Robert Bragg [this message]
2017-01-27 17:42 ` [PATCH v2 1/5] drm/i915/perf: fix gen7_append_oa_reports comment Robert Bragg
2017-01-27 17:42 ` [PATCH v2 2/5] drm/i915/perf: avoid poll, read, EAGAIN busy loops Robert Bragg
2017-01-27 17:42 ` [PATCH v2 3/5] drm/i915/perf: avoid read back of head register Robert Bragg
2017-01-27 17:42 ` [PATCH v2 4/5] drm/i915/perf: no head/tail ref in gen7_oa_read Robert Bragg
2017-01-27 17:42 ` [PATCH v2 5/5] drm/i915/perf: improve tail race workaround Robert Bragg
2017-01-30 15:24 ` ✓ Fi.CI.BAT: success for drm/i915/perf: Improve handling of OA tail race (rev2) Patchwork
2017-02-13 4:57 ` [PATCH v2 0/5] drm/i915/perf: Improve handling of OA tail race Kenneth Graunke
-- strict thread matches above, loose matches on Subject: below --
2017-02-13 14:36 Robert Bragg
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=20170127174205.15325-1-robert@sixbynine.org \
--to=robert@sixbynine.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox