From: Arun Siluvery <arun.siluvery@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v2 0/4] Gen9 WA Batch patches
Date: Mon, 6 Jul 2015 17:12:37 +0100 [thread overview]
Message-ID: <1436199161-3641-1-git-send-email-arun.siluvery@linux.intel.com> (raw)
Compared to v1 changes are only in Patch 1, these changes are to group
all infrastructure bits in a single patch. Patch 2 wasn't getting applied
cleanly because of this hence sending all patches.
Arun Siluvery (4):
drm/i915: Enable WA batch buffers for Gen9
drm/i915/gen9: Add WaDisableCtxRestoreArbitration workaround
drm/i915/gen9: Add WaFlushCoherentL3CacheLinesAtContextSwitch
workaround
drm/i915/gen9: Add
WaSetDisablePixMaskCammingAndRhwoInCommonSliceChicken
drivers/gpu/drm/i915/intel_lrc.c | 73 +++++++++++++++++++++++++++++++--
drivers/gpu/drm/i915/intel_ringbuffer.c | 7 +++-
2 files changed, 75 insertions(+), 5 deletions(-)
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-07-06 16:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 16:12 Arun Siluvery [this message]
2015-07-06 16:12 ` [PATCH v2 1/4] drm/i915: Enable WA batch buffers for Gen9 Arun Siluvery
2015-07-10 15:52 ` Mika Kuoppala
2015-07-10 16:16 ` Siluvery, Arun
2015-07-06 16:12 ` [PATCH v2 2/4] drm/i915/gen9: Add WaDisableCtxRestoreArbitration workaround Arun Siluvery
2015-07-07 17:41 ` Arun Siluvery
2015-07-13 12:31 ` Mika Kuoppala
2015-07-13 14:49 ` Daniel Vetter
2015-07-13 14:52 ` Daniel Vetter
2015-07-06 16:12 ` [PATCH v2 3/4] drm/i915/gen9: Add WaFlushCoherentL3CacheLinesAtContextSwitch workaround Arun Siluvery
2015-07-13 10:36 ` Arun Siluvery
2015-07-13 13:08 ` Mika Kuoppala
2015-07-06 16:12 ` [PATCH v2 4/4] drm/i915/gen9: Add WaSetDisablePixMaskCammingAndRhwoInCommonSliceChicken Arun Siluvery
2015-07-07 17:43 ` Arun Siluvery
2015-07-13 13:16 ` Mika Kuoppala
2015-07-14 9:34 ` Dave Gordon
2015-07-14 9:52 ` Mika Kuoppala
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=1436199161-3641-1-git-send-email-arun.siluvery@linux.intel.com \
--to=arun.siluvery@linux.intel.com \
--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.