From: Arun Siluvery <arun.siluvery@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Mika Kuoppala <mika.kuoppala@intel.com>
Subject: [PATCH] drm/i915: Emit even number of dwords when emitting LRIs
Date: Wed, 22 Oct 2014 10:09:49 +0100 [thread overview]
Message-ID: <1413968989-16840-1-git-send-email-arun.siluvery@linux.intel.com> (raw)
The number of DWords should be even when doing ring emits as
command sequences require QWord alignment.
Cc: Mika Kuoppala <mika.kuoppala@intel.com>
Signed-off-by: Arun Siluvery <arun.siluvery@linux.intel.com>
---
drivers/gpu/drm/i915/intel_ringbuffer.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
index 12a546f..79211ae 100644
--- a/drivers/gpu/drm/i915/intel_ringbuffer.c
+++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
@@ -680,7 +680,7 @@ static int intel_ring_workarounds_emit(struct intel_engine_cs *ring)
if (ret)
return ret;
- ret = intel_ring_begin(ring, w->count * 3);
+ ret = intel_ring_begin(ring, w->count * 4);
if (ret)
return ret;
@@ -688,6 +688,7 @@ static int intel_ring_workarounds_emit(struct intel_engine_cs *ring)
intel_ring_emit(ring, MI_LOAD_REGISTER_IMM(1));
intel_ring_emit(ring, w->reg[i].addr);
intel_ring_emit(ring, w->reg[i].value);
+ intel_ring_emit(ring, MI_NOOP);
}
intel_ring_advance(ring);
--
2.1.2
next reply other threads:[~2014-10-22 9:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 9:09 Arun Siluvery [this message]
2014-10-22 10:40 ` [PATCH] drm/i915: Emit even number of dwords when emitting LRIs Damien Lespiau
2014-10-22 10:54 ` Damien Lespiau
-- strict thread matches above, loose matches on Subject: below --
2014-10-22 17:59 Arun Siluvery
2014-10-22 21:59 ` Damien Lespiau
2014-10-23 12:21 ` Daniel Vetter
2014-10-23 12:42 ` Damien Lespiau
2014-10-23 12:50 ` Chris Wilson
2014-10-23 13:41 ` Ville Syrjälä
2014-10-23 13:55 ` Siluvery, Arun
2014-10-23 14:42 ` Mika Kuoppala
2014-10-23 15:49 ` Daniel Vetter
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=1413968989-16840-1-git-send-email-arun.siluvery@linux.intel.com \
--to=arun.siluvery@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@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