From: John Harrison <john.c.harrison@intel.com>
To: <Intel-Xe@Lists.FreeDesktop.Org>,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH v4 0/2] Support/debug for slow GuC loads
Date: Mon, 25 Mar 2024 16:32:47 -0700 [thread overview]
Message-ID: <f5ad70e0-1a4f-4ab3-a730-fed6c4ccc0cc@intel.com> (raw)
In-Reply-To: <20240228011002.2454419-1-John.C.Harrison@Intel.com>
@Lucas, ping for review?
On 2/27/2024 17:09, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> Sometimes the GuC load is slower that it should be. For end users,
> that usually means some kind of thermal throttling issue. Internally,
> there can be any number of bugs that cause it. So don't completely
> fail to load, just cope with it and report the problem.
>
> v2: Revert include order (review feedback from Lucas)
> v3: Remove '_sysfs' from throttle file names and keep limit query in
> the same file rather than moving elsewhere (review feedback from
> Rodrigo). Fix the reporting of requested vs granted frequencies
> (review feedback from Badal).
> v4: Manually code the loop timeout/condition checking because helper
> functions are not allowed (review feedback from Lucas/Rodrigo)
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
>
>
> John Harrison (2):
> drm/xe: Make read_perf_limit_reasons globally accessible
> drm/xe/guc: Port over the slow GuC loading support from i915
>
> drivers/gpu/drm/xe/Makefile | 2 +-
> drivers/gpu/drm/xe/abi/guc_errors_abi.h | 26 +-
> drivers/gpu/drm/xe/regs/xe_guc_regs.h | 2 +
> drivers/gpu/drm/xe/xe_gt_freq.c | 4 +-
> ...e_gt_throttle_sysfs.c => xe_gt_throttle.c} | 26 +-
> drivers/gpu/drm/xe/xe_gt_throttle.h | 17 ++
> drivers/gpu/drm/xe/xe_gt_throttle_sysfs.h | 16 --
> drivers/gpu/drm/xe/xe_guc.c | 226 ++++++++++++++----
> drivers/gpu/drm/xe/xe_mmio.c | 61 +++++
> drivers/gpu/drm/xe/xe_mmio.h | 2 +
> 10 files changed, 307 insertions(+), 75 deletions(-)
> rename drivers/gpu/drm/xe/{xe_gt_throttle_sysfs.c => xe_gt_throttle.c} (86%)
> create mode 100644 drivers/gpu/drm/xe/xe_gt_throttle.h
> delete mode 100644 drivers/gpu/drm/xe/xe_gt_throttle_sysfs.h
>
next prev parent reply other threads:[~2024-03-25 23:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 1:09 [PATCH v4 0/2] Support/debug for slow GuC loads John.C.Harrison
2024-02-28 1:09 ` [PATCH v4 1/2] drm/xe: Make read_perf_limit_reasons globally accessible John.C.Harrison
2024-04-04 18:30 ` Lucas De Marchi
2024-02-28 1:09 ` [PATCH v4 2/2] drm/xe/guc: Port over the slow GuC loading support from i915 John.C.Harrison
2024-04-04 19:19 ` Lucas De Marchi
2024-04-04 19:52 ` John Harrison
2024-04-04 20:03 ` Lucas De Marchi
2024-04-04 20:11 ` John Harrison
2024-04-04 21:07 ` Lucas De Marchi
2024-04-08 23:48 ` John Harrison
2024-02-28 1:16 ` ✓ CI.Patch_applied: success for Support/debug for slow GuC loads Patchwork
2024-02-28 1:16 ` ✗ CI.checkpatch: warning " Patchwork
2024-02-28 1:17 ` ✓ CI.KUnit: success " Patchwork
2024-02-28 1:28 ` ✓ CI.Build: " Patchwork
2024-02-28 1:29 ` ✓ CI.Hooks: " Patchwork
2024-02-28 1:30 ` ✓ CI.checksparse: " Patchwork
2024-02-28 1:48 ` ✓ CI.BAT: " Patchwork
2024-03-25 23:32 ` John Harrison [this message]
2024-04-04 18:25 ` [PATCH v4 0/2] " Lucas De Marchi
2024-04-09 0:09 ` John Harrison
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=f5ad70e0-1a4f-4ab3-a730-fed6c4ccc0cc@intel.com \
--to=john.c.harrison@intel.com \
--cc=Intel-Xe@Lists.FreeDesktop.Org \
--cc=lucas.demarchi@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