From: Andi Shyti <andi.shyti@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: Abdiel Janulgue <abdiel.janulgue@gmail.com>,
Intel GFX <intel-gfx@lists.freedesktop.org>,
Lucas De Marchi <lucas.demarchi@intel.com>,
DRI Devel <dri-devel@lists.freedesktop.org>,
Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH v2 2/2] drm/i915/gt: make a gt sysfs group and move power management files
Date: Fri, 14 Jan 2022 20:20:14 +0200 [thread overview]
Message-ID: <YeG+3nv9j/JoAWis@intel.intel> (raw)
In-Reply-To: <YeGuFsMLL5kxzTiu@mdroper-desk1.amr.corp.intel.com>
Hi Matt,
> > The GT has its own properties and in sysfs they should be grouped
> > in the 'gt/' directory.
> >
> > Create a 'gt/' directory in sysfs which will contain gt0...gtN
> > directories related to each tile configured in the GPU. Move the
> > power management files inside those directories.
> >
> > The previous power management files are kept in their original
> > root directory to avoid breaking the ABI. They point to the tile
> > '0' and a warning message is printed whenever accessed to. The
> > deprecated interface needs for the CONFIG_SYSFS_DEPRECATED_V2
> > flag in order to be generated.
> >
> > The new sysfs structure will have a similar layout for the 4 tile
> > case:
> >
> > /sys/.../card0
> > ├── gt
> > │ ├── gt0
> > │ │ ├── id
> > │ │ ├── rc6_enable
> > │ │ ├── rc6_residency_ms
> > │ │ ├── rps_act_freq_mhz
> > │ │ ├── rps_boost_freq_mhz
> > │ │ ├── rps_cur_freq_mhz
> > │ │ ├── rps_max_freq_mhz
> > │ │ ├── rps_min_freq_mhz
> > │ │ ├── rps_RP0_freq_mhz
> > │ │ ├── rps_RP1_freq_mhz
> > │ │ └── rps_RPn_freq_mhz
> > . .
> > . .
> > . .
> > │ └── gt3
> > │ ├── id
> > │ ├── rc6_enable
> > │ ├── rc6_residency_ms
> > │ ├── rps_act_freq_mhz
> > │ ├── rps_boost_freq_mhz
> > │ ├── rps_cur_freq_mhz
> > │ ├── rps_max_freq_mhz
> > │ ├── rps_min_freq_mhz
> > │ ├── rps_RP0_freq_mhz
> > │ ├── rps_RP1_freq_mhz
> > │ └── rps_RPn_freq_mhz
> > ├── gt_act_freq_mhz -+
> > ├── gt_boost_freq_mhz |
> > ├── gt_cur_freq_mhz | Original interface
> > ├── gt_max_freq_mhz +─-> kept as existing ABI;
> > ├── gt_min_freq_mhz | it points to gt0/
> > ├── gt_RP0_freq_mhz |
> > └── gt_RP1_freq_mhz |
> > └── gt_RPn_freq_mhz -+
> >
> > Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
> > Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> > Cc: Matt Roper <matthew.d.roper@intel.com>
> > Cc: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
> > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Even though this is a pretty natural extension of sysfs entries we
> already have in the driver today, it's still technically "new ABI" so I
> think we need a link to the IGT changes that exercise it to make sure
> it's working as expected.
this patch should unblock the level0 sysman for DG1 and DG2,
currently being upstreamed, and this will be handled by Sujaritha
in the next days.
Besides there a patch that is adding an hwmon interface to i915
that depends on this one.
> Likewise we need a link to the real userspace consumer that is expecting
> to use this (does some of the Level0 stuff use these knobs?). If this
> is one of those really rare cases where we never expect any specific
> userspace software to use the ABI, but the intent is instead to let
> sysadmins turn the knobs manually with custom shell scripts or whatever,
> that would need to be justified in the commit message too.
I think with the first multitile platform coming (next series)
this will be essential to control the power of multitile devices,
either manually or with tools, otherwise we will be able only to
access tile 0.
I can add a note in the commit message.
Andi
next prev parent reply other threads:[~2022-01-14 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 22:20 [Intel-gfx] [PATCH v2 0/2] Introduce multitile support Andi Shyti
2022-01-12 22:20 ` [Intel-gfx] [PATCH v2 1/2] drm/i915: Prepare for multiple GTs Andi Shyti
2022-01-14 16:55 ` Matt Roper
2022-01-14 17:59 ` Andi Shyti
2022-01-17 18:03 ` Abdiel Janulgue
2022-01-12 22:20 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/gt: make a gt sysfs group and move power management files Andi Shyti
2022-01-12 22:42 ` Sundaresan, Sujaritha
2022-01-14 17:08 ` Matt Roper
2022-01-14 18:20 ` Andi Shyti [this message]
2022-01-12 22:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce multitile support Patchwork
2022-01-12 22:36 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-01-12 23:06 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-13 3:45 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=YeG+3nv9j/JoAWis@intel.intel \
--to=andi.shyti@linux.intel.com \
--cc=abdiel.janulgue@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.d.roper@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;
as well as URLs for NNTP newsgroup(s).