All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v14 0/6] drm/i915: expose RCS topology to userspace
Date: Thu, 22 Feb 2018 17:53:53 +0000	[thread overview]
Message-ID: <20180222175359.16402-1-lionel.g.landwerlin@intel.com> (raw)

Hi all,

This iteration has 2 main changes :

 - Joonas wanted to have stride fields into the
   drm_i915_query_topology_info, so the layout has changed a bit.
   Tvrtko also suggested alignment stuff.

 - In commit b8ec759e6f1c6da0418238df066a0f1ef8fd2075 I added
   slice/subslice mask reporting for Haswell through the existing
   getparam ioctl. Haswell can have up to 10 EUs per half/sub-slice,
   so a few places needed to be updated with deal with u16 internally
   (this doesn't change the uAPI in anyway).

Cheers,

Lionel Landwerlin (6):
  drm/i915: store all subslice masks
  drm/i915/debugfs: reuse max slice/subslices already stored in sseu
  drm/i915/debugfs: add rcs topology entry
  drm/i915: add rcs topology to error state
  drm/i915: add query uAPI
  drm/i915: expose rcs topology through query uAPI

 drivers/gpu/drm/i915/Makefile            |   1 +
 drivers/gpu/drm/i915/i915_debugfs.c      |  63 ++++----
 drivers/gpu/drm/i915/i915_drv.c          |   4 +-
 drivers/gpu/drm/i915/i915_gpu_error.c    |   1 +
 drivers/gpu/drm/i915/i915_query.c        | 131 ++++++++++++++++
 drivers/gpu/drm/i915/i915_query.h        |  15 ++
 drivers/gpu/drm/i915/intel_device_info.c | 248 ++++++++++++++++++++++++-------
 drivers/gpu/drm/i915/intel_device_info.h |  60 +++++++-
 drivers/gpu/drm/i915/intel_lrc.c         |   2 +-
 drivers/gpu/drm/i915/intel_ringbuffer.h  |   2 +-
 include/uapi/drm/i915_drm.h              | 102 +++++++++++++
 11 files changed, 546 insertions(+), 83 deletions(-)
 create mode 100644 drivers/gpu/drm/i915/i915_query.c
 create mode 100644 drivers/gpu/drm/i915/i915_query.h

--
2.16.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2018-02-22 17:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 17:53 Lionel Landwerlin [this message]
2018-02-22 17:53 ` [PATCH v14 1/6] drm/i915: store all subslice masks Lionel Landwerlin
2018-02-23 13:47   ` Lionel Landwerlin
2018-02-22 17:53 ` [PATCH v14 2/6] drm/i915/debugfs: reuse max slice/subslices already stored in sseu Lionel Landwerlin
2018-02-22 17:53 ` [PATCH v14 3/6] drm/i915/debugfs: add rcs topology entry Lionel Landwerlin
2018-02-22 17:53 ` [PATCH v14 4/6] drm/i915: add rcs topology to error state Lionel Landwerlin
2018-02-22 17:53 ` [PATCH v14 5/6] drm/i915: add query uAPI Lionel Landwerlin
2018-03-05 14:54   ` Joonas Lahtinen
2018-03-05 15:03     ` Lionel Landwerlin
2018-02-22 17:53 ` [PATCH v14 6/6] drm/i915: expose rcs topology through " Lionel Landwerlin
2018-03-05 15:48   ` Joonas Lahtinen
2018-02-22 18:07 ` ✗ Fi.CI.SPARSE: warning for drm/i915: expose RCS topology to userspace Patchwork
2018-02-22 18:20 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-22 19:08 ` [PATCH v14 0/6] " Lionel Landwerlin
2018-02-23  0:33 ` ✗ Fi.CI.IGT: failure for " 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=20180222175359.16402-1-lionel.g.landwerlin@intel.com \
    --to=lionel.g.landwerlin@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 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.