From: Matt Roper <matthew.d.roper@intel.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
cgroups@vger.kernel.org
Subject: [PATCH v4.5 0/8] cgroup private data and DRM/i915 integration
Date: Wed, 21 Mar 2018 16:23:36 -0700 [thread overview]
Message-ID: <20180321232344.20727-1-matthew.d.roper@intel.com> (raw)
This version of the patch series just contains some minor updates to
address checkpatch and sparse warnings. There are no serious design or
implementation changes since v4.
You can find the previous versions of this series (and more detailed
cover letters) here:
(v1) https://lists.freedesktop.org/archives/intel-gfx/2018-January/153156.html
(v2) https://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg208170.html
(v3) https://lists.freedesktop.org/archives/intel-gfx/2018-March/157928.html
(v4) https://lists.freedesktop.org/archives/intel-gfx/2018-March/159222.html
Matt Roper (8):
cgroup: Allow registration and lookup of cgroup private data (v3)
cgroup: Introduce task_get_dfl_cgroup() (v2)
cgroup: Introduce cgroup_priv_get_current
drm/i915: Adjust internal priority definitions (v2)
drm/i915: cgroup integration (v4)
drm/i915: Introduce 'priority offset' for GPU contexts (v4)
drm/i915: Introduce per-cgroup display boost setting
drm/i915: Add context priority & priority offset to debugfs (v2)
drivers/gpu/drm/i915/Makefile | 1 +
drivers/gpu/drm/i915/i915_cgroup.c | 207 ++++++++++++++++++++++++++++++++
drivers/gpu/drm/i915/i915_debugfs.c | 3 +
drivers/gpu/drm/i915/i915_drv.c | 8 ++
drivers/gpu/drm/i915/i915_drv.h | 46 ++++++-
drivers/gpu/drm/i915/i915_gem_context.c | 12 +-
drivers/gpu/drm/i915/i915_gem_context.h | 9 ++
drivers/gpu/drm/i915/i915_request.h | 18 ++-
drivers/gpu/drm/i915/intel_display.c | 5 +-
include/linux/cgroup-defs.h | 8 ++
include/linux/cgroup.h | 37 ++++++
include/uapi/drm/i915_drm.h | 14 +++
kernel/cgroup/cgroup.c | 206 ++++++++++++++++++++++++++++++-
13 files changed, 561 insertions(+), 13 deletions(-)
create mode 100644 drivers/gpu/drm/i915/i915_cgroup.c
--
2.14.3
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-03-21 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 23:23 Matt Roper [this message]
2018-03-21 23:23 ` [PATCH v4.5 1/8] cgroup: Allow registration and lookup of cgroup private data (v3) Matt Roper
2018-03-22 18:04 ` Chris Wilson
2018-03-21 23:23 ` [PATCH v4.5 2/8] cgroup: Introduce task_get_dfl_cgroup() (v2) Matt Roper
2018-03-21 23:23 ` [PATCH v4.5 3/8] cgroup: Introduce cgroup_priv_get_current Matt Roper
2018-03-21 23:23 ` [PATCH v4.5 4/8] drm/i915: Adjust internal priority definitions (v2) Matt Roper
2018-03-21 23:23 ` [PATCH v4.5 5/8] drm/i915: cgroup integration (v4) Matt Roper
2018-03-21 23:23 ` [PATCH v4.5 6/8] drm/i915: Introduce 'priority offset' for GPU contexts (v4) Matt Roper
2018-03-21 23:23 ` [PATCH v4.5 7/8] drm/i915: Introduce per-cgroup display boost setting Matt Roper
2018-03-21 23:23 ` [PATCH v4.5 8/8] drm/i915: Add context priority & priority offset to debugfs (v2) Matt Roper
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=20180321232344.20727-1-matthew.d.roper@intel.com \
--to=matthew.d.roper@intel.com \
--cc=cgroups@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).