From: Tvrtko Ursulin <tursulin@ursulin.net>
To: Intel-gfx@lists.freedesktop.org
Subject: [CI v2] drm/i915: GuC test run
Date: Tue, 20 Feb 2018 18:36:36 +0000 [thread overview]
Message-ID: <20180220183636.28204-1-tvrtko.ursulin@linux.intel.com> (raw)
In-Reply-To: <20180220173623.27822-1-tvrtko.ursulin@linux.intel.com>
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
With disabled aggressive idling from IGT. To see how shard run fares.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
drivers/gpu/drm/i915/i915_debugfs.c | 3 ---
drivers/gpu/drm/i915/i915_params.h | 2 +-
2 files changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
index 05b41045b8f9..61da6569ad6c 100644
--- a/drivers/gpu/drm/i915/i915_debugfs.c
+++ b/drivers/gpu/drm/i915/i915_debugfs.c
@@ -4076,9 +4076,6 @@ i915_drop_caches_set(void *data, u64 val)
i915_gem_shrink_all(dev_priv);
fs_reclaim_release(GFP_KERNEL);
- if (val & DROP_IDLE)
- drain_delayed_work(&dev_priv->gt.idle_work);
-
if (val & DROP_FREED)
i915_gem_drain_freed_objects(dev_priv);
diff --git a/drivers/gpu/drm/i915/i915_params.h b/drivers/gpu/drm/i915/i915_params.h
index 430f5f9d0ff4..3deae1e22974 100644
--- a/drivers/gpu/drm/i915/i915_params.h
+++ b/drivers/gpu/drm/i915/i915_params.h
@@ -47,7 +47,7 @@ struct drm_printer;
param(int, disable_power_well, -1) \
param(int, enable_ips, 1) \
param(int, invert_brightness, 0) \
- param(int, enable_guc, 0) \
+ param(int, enable_guc, -1) \
param(int, guc_log_level, 0) \
param(char *, guc_firmware_path, NULL) \
param(char *, huc_firmware_path, NULL) \
--
2.14.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-20 18:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 17:36 [CI] drm/i915: GuC test run Tvrtko Ursulin
2018-02-20 18:05 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-02-20 18:19 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-02-20 18:36 ` Tvrtko Ursulin [this message]
2018-02-21 8:08 ` [CI v3] " Tvrtko Ursulin
2018-02-21 10:12 ` Tvrtko Ursulin
2018-02-21 10:32 ` Sagar Arun Kamble
2018-02-21 10:42 ` Tvrtko Ursulin
2018-02-21 10:46 ` [CI v4] " Tvrtko Ursulin
2018-02-20 18:58 ` ✗ Fi.CI.BAT: failure for drm/i915: GuC test run (rev2) Patchwork
2018-02-21 9:19 ` ✗ Fi.CI.BAT: failure for drm/i915: GuC test run (rev3) Patchwork
2018-02-21 12:36 ` ✓ Fi.CI.BAT: success for drm/i915: GuC test run (rev4) Patchwork
2018-02-21 16:41 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-02-22 6:07 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-22 7:50 ` ✗ 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=20180220183636.28204-1-tvrtko.ursulin@linux.intel.com \
--to=tursulin@ursulin.net \
--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.