All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: matthew.auld@intel.com
Subject: [PATCH 05/15] drm/i915/gt: Ignore forcewake acquisition for posting_reads
Date: Wed,  3 Jul 2019 10:17:16 +0100	[thread overview]
Message-ID: <20190703091726.11690-5-chris@chris-wilson.co.uk> (raw)
In-Reply-To: <20190703091726.11690-1-chris@chris-wilson.co.uk>

We don't care about the result of the read, so it may be garbage, we
only care that the mmio is flushed. As such, we can forgo using an
individual forcewake and lock around any posting-read for an engine.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
---
 drivers/gpu/drm/i915/gt/intel_engine.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/gt/intel_engine.h b/drivers/gpu/drm/i915/gt/intel_engine.h
index 557b08b13feb..0331e9ac2485 100644
--- a/drivers/gpu/drm/i915/gt/intel_engine.h
+++ b/drivers/gpu/drm/i915/gt/intel_engine.h
@@ -51,7 +51,7 @@ struct drm_printer;
 #define ENGINE_READ16(...)	__ENGINE_READ_OP(read16, __VA_ARGS__)
 #define ENGINE_READ(...)	__ENGINE_READ_OP(read, __VA_ARGS__)
 #define ENGINE_READ_FW(...)	__ENGINE_READ_OP(read_fw, __VA_ARGS__)
-#define ENGINE_POSTING_READ(...) __ENGINE_READ_OP(posting_read, __VA_ARGS__)
+#define ENGINE_POSTING_READ(...) __ENGINE_READ_OP(posting_read_fw, __VA_ARGS__)
 #define ENGINE_POSTING_READ16(...) __ENGINE_READ_OP(posting_read16, __VA_ARGS__)
 
 #define ENGINE_READ64(engine__, lower_reg__, upper_reg__) \
-- 
2.20.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-07-03  9:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03  9:17 [PATCH 01/15] drm/i915/selftests: Common live setup/teardown Chris Wilson
2019-07-03  9:17 ` [PATCH 02/15] drm/i915/selftests: Lock the drm_mm while modifying Chris Wilson
2019-07-03  9:50   ` Matthew Auld
2019-07-03  9:17 ` [PATCH 03/15] drm/i915/gt: Use caller provided forcewake for intel_mocs_init_engine Chris Wilson
2019-07-03 11:23   ` Tvrtko Ursulin
2019-07-03 11:47     ` Chris Wilson
2019-07-03 12:01       ` Tvrtko Ursulin
2019-07-03  9:17 ` [PATCH 04/15] drm/i915/gt: Assume we hold forcewake for execlists resume Chris Wilson
2019-07-03 12:03   ` Tvrtko Ursulin
2019-07-03  9:17 ` Chris Wilson [this message]
2019-07-03 11:26   ` [PATCH 05/15] drm/i915/gt: Ignore forcewake acquisition for posting_reads Tvrtko Ursulin
2019-07-03 11:44     ` Chris Wilson
2019-07-03  9:17 ` [PATCH 06/15] drm/i915/gem: Free pages before rcu-freeing the object Chris Wilson
2019-07-03 10:37   ` Matthew Auld
2019-07-03  9:17 ` [PATCH 07/15] drm/i915: Markup potential lock for i915_active Chris Wilson
2019-07-03 10:38   ` Matthew Auld
2019-07-03  9:17 ` [PATCH 08/15] drm/i915: Mark up vma->active as safe for use inside shrinkers Chris Wilson
2019-07-03 10:53   ` Matthew Auld
2019-07-03  9:17 ` [PATCH 09/15] drm/i915/execlists: Hesitate before slicing Chris Wilson
2019-07-03  9:17 ` [PATCH 10/15] drm/i915: Teach execbuffer to take the engine wakeref not GT Chris Wilson
2019-07-03  9:17 ` [PATCH 11/15] drm/i915/gt: Track timeline activeness in enter/exit Chris Wilson
2019-07-03  9:17 ` [PATCH 12/15] drm/i915/gt: Convert timeline tracking to spinlock Chris Wilson
2019-07-03  9:17 ` [PATCH 13/15] drm/i915/gt: Guard timeline pinning with its own mutex Chris Wilson
2019-07-03  9:17 ` [PATCH 14/15] drm/i915: Protect request retirement with timeline->mutex Chris Wilson
2019-07-03  9:17 ` [PATCH 15/15] drm/i915: Replace struct_mutex for batch pool serialisation Chris Wilson
2019-07-03  9:41 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/15] drm/i915/selftests: Common live setup/teardown Patchwork
2019-07-03  9:47 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-07-03  9:48 ` [PATCH 01/15] " Matthew Auld
2019-07-03 10:04   ` Chris Wilson
2019-07-03  9:59 ` ✓ Fi.CI.BAT: success for series starting with [01/15] " Patchwork
2019-07-04  3:22 ` ✗ Fi.CI.IGT: failure " Patchwork

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=20190703091726.11690-5-chris@chris-wilson.co.uk \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@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 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.