From: Stuart Summers <stuart.summers@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/2] Add module parameter to reduce engine instances
Date: Tue, 27 Aug 2019 16:14:33 -0700 [thread overview]
Message-ID: <20190827231435.398-1-stuart.summers@intel.com> (raw)
Add a new module parameter, ring_mask, to allow users to
disable certain engines for a platform. By default this
mask is set to all engines enabled. Bits in the mask are
aligned with the intel_engine_id enums.
As a prerequisite to the patch which adds the module parameter,
change the BUG_ON to a WARN_ON in the event a VDbox or VEbox
engine for a platform does not match the total number of engines
of these catagories supported in the corresponding fuses.
Stuart Summers (2):
drm/i915: WARN rather than BUG with unexpected media engines
drm/i915: Add ring_mask module parameter
drivers/gpu/drm/i915/i915_params.c | 3 +++
drivers/gpu/drm/i915/i915_params.h | 3 ++-
drivers/gpu/drm/i915/intel_device_info.c | 10 ++++++++--
3 files changed, 13 insertions(+), 3 deletions(-)
--
2.22.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-08-27 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 23:14 Stuart Summers [this message]
2019-08-27 23:14 ` [PATCH 1/2] drm/i915: WARN rather than BUG with unexpected media engines Stuart Summers
2019-08-27 23:14 ` [PATCH 2/2] drm/i915: Add ring_mask module parameter Stuart Summers
2019-08-28 9:34 ` Chris Wilson
2019-08-28 15:13 ` Summers, Stuart
2019-08-27 23:21 ` ✗ Fi.CI.CHECKPATCH: warning for Add module parameter to reduce engine instances Patchwork
2019-08-28 9:28 ` ✓ Fi.CI.BAT: success " Patchwork
2019-08-29 10:16 ` ✓ Fi.CI.IGT: " 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=20190827231435.398-1-stuart.summers@intel.com \
--to=stuart.summers@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox