Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v6 0/5] drm/i915: Expose more GPU properties through sysfs
Date: Thu, 7 Dec 2017 09:21:27 +0000	[thread overview]
Message-ID: <03194f3a-258b-a4bc-2b67-6c4ac992075f@linux.intel.com> (raw)
In-Reply-To: <20171204150238.28011-1-lionel.g.landwerlin@intel.com>


On 04/12/2017 15:02, Lionel Landwerlin wrote:
> Hi,
> 
> After discussion with Chris, Joonas & Tvrtko, this series adds an
> additional commit to link the render node back to the card through a
> symlink. Making it obvious from an application using a render node to
> know where to get the information it needs.

Important thing to mention as well is that it is trivial to get from the 
master drm fd to the sysfs root, via fstat and opendir 
/sys/dev/char/<major>:<minor>. With the addition of the card symlink to 
render nodes it is trivial for render node fd as well.

I am happy with this approach - it is extensible, flexible and avoids 
issues with ioctl versioning or whatnot. With one value per file it is 
trivial for userspace to access.

So for what I'm concerned, given how gputop would use all of this and so 
be the userspace, if everyone else is happy, I think we could do a 
detailed review and prehaps also think about including gputop in some 
distribution to make the case 100% straightforward.

Regards,

Tvrtko

> 
> Cheers,
> 
> Lionel Landwerlin (5):
>    drm: add card symlink in render sysfs directory
>    drm/i915: store all subslice masks
>    drm/i915/debugfs: reuse max slice/subslices already stored in sseu
>    drm/i915: expose engine availability through sysfs
>    drm/i915: expose EU topology through sysfs
> 
>   drivers/gpu/drm/drm_drv.c                |  11 +
>   drivers/gpu/drm/i915/i915_debugfs.c      |  50 ++--
>   drivers/gpu/drm/i915/i915_drv.c          |   2 +-
>   drivers/gpu/drm/i915/i915_drv.h          |  56 ++++-
>   drivers/gpu/drm/i915/i915_sysfs.c        | 386 +++++++++++++++++++++++++++++++
>   drivers/gpu/drm/i915/intel_device_info.c | 169 ++++++++++----
>   drivers/gpu/drm/i915/intel_engine_cs.c   |  12 +
>   drivers/gpu/drm/i915/intel_lrc.c         |   2 +-
>   drivers/gpu/drm/i915/intel_ringbuffer.h  |   6 +-
>   9 files changed, 617 insertions(+), 77 deletions(-)
> 
> --
> 2.15.1
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-12-07  9:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 15:02 [PATCH v6 0/5] drm/i915: Expose more GPU properties through sysfs Lionel Landwerlin
2017-12-04 15:02 ` [PATCH v6 1/5] drm: add card symlink in render sysfs directory Lionel Landwerlin
2017-12-04 15:02 ` [PATCH v6 2/5] drm/i915: store all subslice masks Lionel Landwerlin
2017-12-04 15:02 ` [PATCH v6 3/5] drm/i915/debugfs: reuse max slice/subslices already stored in sseu Lionel Landwerlin
2017-12-04 15:02 ` [PATCH v6 4/5] drm/i915: expose engine availability through sysfs Lionel Landwerlin
2017-12-04 15:02 ` [PATCH v6 5/5] drm/i915: expose EU topology " Lionel Landwerlin
2017-12-04 16:02 ` ✓ Fi.CI.BAT: success for drm/i915: Expose more GPU properties through sysfs (rev6) Patchwork
2017-12-04 18:48 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-12-07  9:21 ` Tvrtko Ursulin [this message]
2017-12-11 10:50   ` [Intel-gfx] [PATCH v6 0/5] drm/i915: Expose more GPU properties through sysfs Joonas Lahtinen
2017-12-11 13:29     ` Lionel Landwerlin
2017-12-11 14:38     ` [Intel-gfx] " Tvrtko Ursulin
2017-12-11 14:47       ` Lionel Landwerlin
2017-12-11 21:05       ` [Intel-gfx] " Daniel Vetter
2017-12-12 11:19         ` Tvrtko Ursulin
2017-12-12 14:33           ` Lionel Landwerlin
2017-12-13  8:17             ` Daniel Vetter
2017-12-13 13:35               ` Chris Wilson
2017-12-13 15:09                 ` Lionel Landwerlin
2017-12-13 15:06               ` Lionel Landwerlin
2017-12-12 15:18           ` Daniel Vetter

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=03194f3a-258b-a4bc-2b67-6c4ac992075f@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lionel.g.landwerlin@intel.com \
    /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