From: jeff.mcgee@intel.com
To: dri-devel@lists.freedesktop.org
Subject: [PATCH] intel: Export GT config attributes
Date: Thu, 18 Dec 2014 12:12:32 -0600 [thread overview]
Message-ID: <1418926353-10871-1-git-send-email-jeff.mcgee@intel.com> (raw)
From: Jeff McGee <jeff.mcgee@intel.com>
The motivation for this change is that fusing can be used to create
multiple slice, subslice, and EU configuration within the same PCI
ID. CHV is the first such device to do this and thus make an ID-based
lookup table approach unreliable. The best solution is for the kernel
to determine the precise config from fuse registers and share the
required information with userspace. Moving to this approach has the
added benefit of reducing the number of static parameters that
userspace must maintain for current and future devices.
The associated kernel patch has been posted to intel-gfx list (no
archive link yet). I'm trying to collect feedback from userspace
which I hope will be interested in adopting some form of this
interface. I am starting with these 4 attributes, but we can add or
remove them according to the userspace needs. Please provide any
comments. Thanks
Jeff McGee (1):
intel: Export GT config attributes
include/drm/i915_drm.h | 4 +++
intel/intel_bufmgr.h | 5 ++++
intel/intel_bufmgr_gem.c | 63 ++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 72 insertions(+)
--
2.2.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-12-18 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 18:12 jeff.mcgee [this message]
2014-12-18 18:12 ` [PATCH] intel: Export GT config attributes jeff.mcgee
2015-01-09 2:56 ` Zhenyu Wang
2015-01-09 16:10 ` Jeff McGee
2015-01-07 23:46 ` Jeff McGee
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=1418926353-10871-1-git-send-email-jeff.mcgee@intel.com \
--to=jeff.mcgee@intel.com \
--cc=dri-devel@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