From: Prathap Kumar Valsan <prathap.kumar.valsan@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Chris P Wilson <chris.p.wilson@intel.com>
Subject: [PATCH v3 0/1] Add sysfs interface to control class-of-service
Date: Mon, 7 Oct 2019 12:52:08 -0400 [thread overview]
Message-ID: <20191007165209.31797-1-prathap.kumar.valsan@intel.com> (raw)
For GEN11 MOCS are part of context register state. This means updating
CLOS also needs to update the context state of active contexts.
v3: Rebase
v2: Updated the interface to use two sysfs files(Joonas)
- Gen12 PCode interface is not ready yet to read the way mask.
So removed TGL support and added support for Gen11.
- Updating MOCS in Gen 11 also require changing the context image of
existing contexts.
Referred to gen8_configure_all_contexts() as suggested by Chris.
Prathap Kumar Valsan (1):
drm/i915/ehl: Add sysfs interface to control class-of-service
drivers/gpu/drm/i915/gt/intel_lrc.c | 7 +
drivers/gpu/drm/i915/gt/intel_lrc_reg.h | 1 +
drivers/gpu/drm/i915/gt/intel_mocs.c | 216 +++++++++++++++++++++++-
drivers/gpu/drm/i915/gt/intel_mocs.h | 6 +-
drivers/gpu/drm/i915/i915_drv.h | 8 +
drivers/gpu/drm/i915/i915_reg.h | 1 +
drivers/gpu/drm/i915/i915_sysfs.c | 100 +++++++++++
7 files changed, 337 insertions(+), 2 deletions(-)
--
2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-10-07 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 16:52 Prathap Kumar Valsan [this message]
2019-10-07 16:52 ` [PATCH v3 1/1] drm/i915/ehl: Add sysfs interface to control class-of-service Prathap Kumar Valsan
2019-10-07 20:37 ` Chris Wilson
2019-10-15 7:38 ` Kumar Valsan, Prathap
2019-10-07 16:52 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2019-10-07 17:15 ` ✗ Fi.CI.BAT: 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=20191007165209.31797-1-prathap.kumar.valsan@intel.com \
--to=prathap.kumar.valsan@intel.com \
--cc=chris.p.wilson@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