All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>,
	john.c.harrison@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/pmu: Wait longer for busyness data to be available from GuC
Date: Wed, 08 Dec 2021 18:10:03 +0200	[thread overview]
Message-ID: <87fsr33wo4.fsf@intel.com> (raw)
In-Reply-To: <20211208021512.72419-1-umesh.nerlige.ramappa@intel.com>

On Tue, 07 Dec 2021, Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com> wrote:
> live_engine_busy_stats waits for busyness to start ticking before
> sampling busyness for the test sample duration. The wait accesses an
> MMIO register and the uncore call to read it takes up to 3 ms in the
> worst case. This can result in the wait timing out since the MMIO read
> itself comsumes up the timeout of 500us. Increase the timeout to a
> larger value of 10ms to account for the MMIO read time.
>
> Resolves: https://gitlab.freedesktop.org/drm/intel/-/issues/4536

$ git log --oneline --grep="^Resolves:" | wc -l
35

Please use Closes: instead.


> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> ---
>  drivers/gpu/drm/i915/gt/selftest_engine_pm.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/selftest_engine_pm.c b/drivers/gpu/drm/i915/gt/selftest_engine_pm.c
> index 75f6efc9882f..8af261831470 100644
> --- a/drivers/gpu/drm/i915/gt/selftest_engine_pm.c
> +++ b/drivers/gpu/drm/i915/gt/selftest_engine_pm.c
> @@ -229,7 +229,7 @@ static int __spin_until_busier(struct intel_engine_cs *engine, ktime_t busyness)
>  	start = ktime_get();
>  	while (intel_engine_get_busy_time(engine, &unused) == busyness) {
>  		dt = ktime_get() - start;
> -		if (dt > 500000) {
> +		if (dt > 10000000) {
>  			pr_err("active wait timed out %lld\n", dt);
>  			ENGINE_TRACE(engine, "active wait time out %lld\n", dt);
>  			return -ETIME;

-- 
Jani Nikula, Intel Open Source Graphics Center

  parent reply	other threads:[~2021-12-08 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08  2:15 [Intel-gfx] [PATCH] drm/i915/pmu: Wait longer for busyness data to be available from GuC Umesh Nerlige Ramappa
2021-12-08  2:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-12-08 11:44 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-12-08 16:10 ` Jani Nikula [this message]
2021-12-08 18:19 ` [Intel-gfx] [PATCH] " Matthew Brost
  -- strict thread matches above, loose matches on Subject: below --
2021-12-08 18:33 Umesh Nerlige Ramappa

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=87fsr33wo4.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=john.c.harrison@intel.com \
    --cc=umesh.nerlige.ramappa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.