Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Andi Shyti <andi.shyti@intel.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/2] drm/i915/gt: Expose per gt defaults in sysfs
Date: Tue, 19 Jul 2022 06:19:14 -0400	[thread overview]
Message-ID: <YtaFIr9gGmh1V+7A@intel.com> (raw)
In-Reply-To: <cover.1658192398.git.ashutosh.dixit@intel.com>

On Mon, Jul 18, 2022 at 06:07:06PM -0700, Ashutosh Dixit wrote:
> Create a gt/gtN/.defaults/ directory (similar to
> engine/<engine-name>/.defaults/) to expose default parameter values for each
> gt in sysfs. This allows userspace to restore default parameter values
> after they may have changed.
> 
> Patch 1: Creates the gt/gtN/.defaults/ directory
> Patch 2: Adds per-gt RPS defaults (rps_max_freq_mhz and rps_min_freq_mhz)
> 	 to gt/gtN/.defaults/
> 
> An approved Level-0/oneAPI UMD pull request which consumes the exposed
> defaults can be seen here:
> 	https://github.com/intel/compute-runtime/pull/552
> The UMD pull request will be merged if/after this series is merged to i915.

Pushed to drm-intel-gt-next. Thanks for the patches.

> 
> Previous discussion on these patches can be seen here:
> 	https://patchwork.freedesktop.org/patch/484238/?series=102665&rev=4
> 	https://patchwork.freedesktop.org/patch/483988/?series=102665&rev=3
> 
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Cc: Andi Shyti <andi.shyti@linux.intel.com>
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> 
> Ashutosh Dixit (2):
>   drm/i915/gt: Create gt/gtN/.defaults/ for per gt sysfs defaults
>   drm/i915/gt: Expose per-gt RPS defaults in sysfs
> 
>  drivers/gpu/drm/i915/gt/intel_gt_sysfs.c    | 10 +++---
>  drivers/gpu/drm/i915/gt/intel_gt_sysfs.h    |  6 ++++
>  drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c | 34 +++++++++++++++++++++
>  drivers/gpu/drm/i915/gt/intel_gt_types.h    |  9 ++++++
>  drivers/gpu/drm/i915/gt/intel_rps.c         |  2 ++
>  drivers/gpu/drm/i915/gt/uc/intel_guc_slpc.c | 12 +++++---
>  6 files changed, 64 insertions(+), 9 deletions(-)
> 
> -- 
> 2.34.1
> 

  parent reply	other threads:[~2022-07-19 10:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19  1:07 [Intel-gfx] [PATCH 0/2] drm/i915/gt: Expose per gt defaults in sysfs Ashutosh Dixit
2022-07-19  1:07 ` [Intel-gfx] [PATCH 1/2] drm/i915/gt: Create gt/gtN/.defaults/ for per gt sysfs defaults Ashutosh Dixit
2022-07-19  1:07 ` [Intel-gfx] [PATCH 2/2] drm/i915/gt: Expose per-gt RPS defaults in sysfs Ashutosh Dixit
2022-07-19  1:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/gt: Expose per gt " Patchwork
2022-07-19  1:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-19  6:27 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-07-19 10:19 ` Rodrigo Vivi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-26 18:35 [Intel-gfx] [PATCH 0/2] " Ashutosh Dixit

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=YtaFIr9gGmh1V+7A@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=andi.shyti@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --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