Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
	Intel GFX <intel-gfx@lists.freedesktop.org>,
	DRI Devel <dri-devel@lists.freedesktop.org>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	Matthew Auld <matthew.auld@intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH v6 4/7] drm/i915/gt: create per-tile sysfs interface
Date: Fri, 18 Mar 2022 16:00:34 +0100	[thread overview]
Message-ID: <7eceab36-9ace-c412-8aca-0fbb4fc16a52@intel.com> (raw)
In-Reply-To: <20220318021046.40348-5-andi.shyti@linux.intel.com>

On 18.03.2022 03:10, Andi Shyti wrote:
> Now that we have tiles we want each of them to have its own
> interface. A directory "gt/" is created under "cardN/" that will
> contain as many diroctories as the tiles.
> 
> In the coming patches tile related interfaces will be added. For
> now the sysfs gt structure simply has an id interface related
> to the current tile count.
> 
> The directory structure will follow this scheme:
> 
>      /sys/.../card0
>               └── gt
>                   ├── gt0
>                   │   └── id
>                   :
> 		 :
> 		 └─- gtN
>                       └── id
> 
> This new set of interfaces will be a basic tool for system
> managers and administrators when using i915.
> 
> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Cc: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Reviewed-by: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
> ---
>   drivers/gpu/drm/i915/Makefile            |   1 +
>   drivers/gpu/drm/i915/gt/intel_gt.c       |   2 +
>   drivers/gpu/drm/i915/gt/intel_gt_sysfs.c | 103 +++++++++++++++++++++++
>   drivers/gpu/drm/i915/gt/intel_gt_sysfs.h |  34 ++++++++
>   drivers/gpu/drm/i915/i915_drv.h          |   2 +
>   drivers/gpu/drm/i915/i915_sysfs.c        |   7 +-
>   drivers/gpu/drm/i915/i915_sysfs.h        |   3 +
>   scripts/extract-cert                     | Bin 0 -> 17952 bytes


With above removed.

Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>

Regards
Andrzej


  parent reply	other threads:[~2022-03-18 15:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18  2:10 [Intel-gfx] [PATCH v6 0/7] Introduce multitile support Andi Shyti
2022-03-18  2:10 ` [Intel-gfx] [PATCH v6 1/7] drm/i915: Rename INTEL_REGION_LMEM with INTEL_REGION_LMEM_0 Andi Shyti
2022-03-18  2:10 ` [Intel-gfx] [PATCH v6 2/7] drm/i915/gt: add gt_is_root() helper Andi Shyti
2022-03-18  2:10 ` [Intel-gfx] [PATCH v6 3/7] drm/i915: Prepare for multiple GTs Andi Shyti
2022-03-18 13:04   ` Andrzej Hajda
2022-03-18  2:10 ` [Intel-gfx] [PATCH v6 4/7] drm/i915/gt: create per-tile sysfs interface Andi Shyti
2022-03-18 13:19   ` Matthew Auld
2022-03-18 14:01     ` Andi Shyti
2022-03-18 15:00   ` Andrzej Hajda [this message]
2022-03-18  2:10 ` [Intel-gfx] [PATCH v6 5/7] drm/i915/gt: Create per-tile RC6 " Andi Shyti
2022-03-18  2:10 ` [Intel-gfx] [PATCH v6 6/7] drm/i915/gt: Create per-tile RPS sysfs interfaces Andi Shyti
2022-03-18 14:54   ` Andrzej Hajda
2022-03-18  2:10 ` [Intel-gfx] [PATCH v6 7/7] drm/i915/gt: Adding new sysfs frequency attributes Andi Shyti
2022-03-18 13:09   ` Andrzej Hajda
2022-03-18  3:07 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce multitile support Patchwork
2022-03-18  3:08 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-18  3:43 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-18  5:45 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-03-18  8:17   ` Andi Shyti
2022-03-18 13:25     ` Matthew Auld
2022-03-18 13:51       ` Tvrtko Ursulin
2022-03-18 14:26         ` Andi Shyti
  -- strict thread matches above, loose matches on Subject: below --
2022-03-18 22:46 [Intel-gfx] [PATCH v6 0/7] " Andi Shyti
2022-03-18 22:46 ` [Intel-gfx] [PATCH v6 4/7] drm/i915/gt: create per-tile sysfs interface Andi Shyti

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=7eceab36-9ace-c412-8aca-0fbb4fc16a52@intel.com \
    --to=andrzej.hajda@intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.auld@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