From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Andi Shyti <andi.shyti@intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 0/3] drm/i915/gt: Expose per gt defaults in sysfs
Date: Mon, 18 Jul 2022 18:09:27 -0700 [thread overview]
Message-ID: <87v8rtc3i0.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <87o7zapjov.wl-ashutosh.dixit@intel.com>
On Thu, 02 Jun 2022 16:55:50 -0700, Matt Roper wrote:
>
> On Thu, Jun 02, 2022 at 04:36:02PM -0700, Dixit, Ashutosh wrote:
> > On Fri, 27 May 2022 16:41:28 -0700, Matt Roper wrote:
> > >
> > > On Thu, May 26, 2022 at 12:00:42PM -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.
> > >
> > > Drive-by comment: since this is a GT-related change, I think we're
> > > required to Cc: dri-devel as well.
> >
> > Sure.
> >
> > > And since this is new ABI, we'd need an open source userspace consumer
> > > or a very clear explanation why this is an exception to the rule (e.g.,
> > > if these are meant to be twiddled directly by the user rather than
> > > accessed by userspace software).
> >
> > This series is in response to the following oneAPI requirement ("setting to
> > -1 will return the frequency to the factory value"):
> >
> > https://spec.oneapi.io/level-zero/latest/sysman/api.html?highlight=zesfrequencysetrange#zesfrequencysetrange
> > https://spec.oneapi.io/level-zero/latest/sysman/api.html?highlight=zesfrequencysetrange#_CPPv416zes_freq_range_t
> >
> > So maybe an open-source oneAPI user mode driver will be acceptable
> > userspace? So yes not merely to be twiddled just by the user.
>
> oneapi/l0 is implemented at https://github.com/intel/compute-runtime,
> right? I think that should be fine as long as we provide a link to the
> actual implementation code that's accessing the new sysfs directory.
> Since the userspace code probably won't fully land until after the
> kernel change lands, this would be something like a pull request
> against their repo that's reviewed and fully-ready to go.
I have included a reference to an approved oneAPI/Level-0 UMD pull request
in the latest version of this series here:
https://patchwork.freedesktop.org/series/106460/
I have also removed sysfs files which are not included in the UMD pull
request from the series.
Thanks.
--
Ashutosh
prev parent reply other threads:[~2022-07-19 1:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 19:00 [Intel-gfx] [PATCH v2 0/3] drm/i915/gt: Expose per gt defaults in sysfs Ashutosh Dixit
2022-05-26 19:00 ` [Intel-gfx] [PATCH 1/3] drm/i915/gt: Create gt/gtN/.defaults for per gt sysfs defaults Ashutosh Dixit
2022-05-26 19:00 ` [Intel-gfx] [PATCH 2/3] drm/i915/gt: Expose per-gt RPS defaults in sysfs Ashutosh Dixit
2022-05-26 19:00 ` [Intel-gfx] [PATCH 3/3] drm/i915/gt: Expose default value for media_freq_factor in per-gt sysfs Ashutosh Dixit
2022-05-26 19:30 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/gt: Expose per gt defaults in sysfs Patchwork
2022-05-26 21:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-05-27 0:26 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-27 23:41 ` [Intel-gfx] [PATCH v2 0/3] " Matt Roper
2022-06-02 23:36 ` Dixit, Ashutosh
2022-06-02 23:55 ` Matt Roper
2022-06-03 2:25 ` Dixit, Ashutosh
2022-07-19 1:09 ` Dixit, Ashutosh [this message]
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=87v8rtc3i0.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=andi.shyti@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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