From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc/slpc: Allow SLPC to use efficient frequency
Date: Fri, 09 Dec 2022 10:31:58 -0800 [thread overview]
Message-ID: <871qp8mns1.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20220814234654.34800-1-vinay.belgaumkar@intel.com>
On Sun, 14 Aug 2022 16:46:54 -0700, Vinay Belgaumkar wrote:
>
> Host Turbo operates at efficient frequency when GT is not idle unless
> the user or workload has forced it to a higher level. Replicate the same
> behavior in SLPC by allowing the algorithm to use efficient frequency.
> We had disabled it during boot due to concerns that it might break
> kernel ABI for min frequency. However, this is not the case since
> SLPC will still abide by the (min,max) range limits.
This change seems to have broken the i915 kernel ABI for min frequency for
DG2. Tvrtko pointed this out here:
https://patchwork.freedesktop.org/patch/512274/?series=110574&rev=3
These bugs are the result of that ABI break:
Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/6806
Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/6786
On DG2 when we set min == max freq, we see the GPU running not at the set
min == max freq but at efficient freq (different from the set freq).
We are still trying to see if the ABI can be salvaged but something is
definitely wrong at present.
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2022-12-09 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 23:46 [Intel-gfx] [PATCH] drm/i915/guc/slpc: Allow SLPC to use efficient frequency Vinay Belgaumkar
2022-08-14 23:51 ` Belgaumkar, Vinay
2022-08-15 17:32 ` Rodrigo Vivi
2022-08-15 23:16 ` Belgaumkar, Vinay
2022-08-24 18:14 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/guc/slpc: Allow SLPC to use efficient frequency (rev6) Patchwork
2022-12-09 18:31 ` Dixit, Ashutosh [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-10 0:03 [Intel-gfx] [PATCH] drm/i915/guc/slpc: Allow SLPC to use efficient frequency Vinay Belgaumkar
2022-08-15 16:51 ` Rodrigo Vivi
2022-08-15 16:52 ` Belgaumkar, Vinay
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=871qp8mns1.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=vinay.belgaumkar@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