Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/debugfs: Fix perf_limit_reasons debugfs
Date: Sun, 18 Sep 2022 20:14:14 -0700	[thread overview]
Message-ID: <874jx4hx89.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20220917031501.1916123-1-ashutosh.dixit@intel.com>

On Fri, 16 Sep 2022 20:15:01 -0700, Ashutosh Dixit wrote:
>
> Register GT0_PERF_LIMIT_REASONS (0x1381a8) is available only for Gen11+.

PLEASE IGNORE THIS PATCH. I will submit a different patch for this issue.

Thanks.
--
Ashutosh

> On Gen < 5 igt@debugfs_test@read_all_entries results in the following oops:
>
> <1> [88.829420] BUG: unable to handle page fault for address: ffffc90000bb81a8
> <1> [88.829438] #PF: supervisor read access in kernel mode
> <1> [88.829447] #PF: error_code(0x0000) - not-present page
>
> Bspec: 20008
> Fixes: fe5979665f64 ("drm/i915/debugfs: Add perf_limit_reasons in debugfs")
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
>  drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c b/drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c
> index 68310881a793..e7f057821cd0 100644
> --- a/drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c
> +++ b/drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c
> @@ -660,6 +660,9 @@ static int perf_limit_reasons_get(void *data, u64 *val)
>	struct intel_gt *gt = data;
>	intel_wakeref_t wakeref;
>
> +	if (GRAPHICS_VER(gt->i915) < 11)
> +		return 0;
> +
>	with_intel_runtime_pm(gt->uncore->rpm, wakeref)
>		*val = intel_uncore_read(gt->uncore, intel_gt_perf_limit_reasons_reg(gt));
>
> @@ -671,6 +674,9 @@ static int perf_limit_reasons_clear(void *data, u64 val)
>	struct intel_gt *gt = data;
>	intel_wakeref_t wakeref;
>
> +	if (GRAPHICS_VER(gt->i915) < 11)
> +		return 0;
> +
>	/*
>	 * Clear the upper 16 "log" bits, the lower 16 "status" bits are
>	 * read-only. The upper 16 "log" bits are identical to the lower 16
> --
> 2.34.1
>

      parent reply	other threads:[~2022-09-19  3:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17  3:15 [Intel-gfx] [PATCH] drm/i915/debugfs: Fix perf_limit_reasons debugfs Ashutosh Dixit
2022-09-17  3:54 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-09-17  4:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-17  5:16 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-09-19  3:14 ` 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=874jx4hx89.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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