From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: gregory.f.germano@intel.com, saurabhg.gupta@intel.com, "Roper,
Matthew D" <matthew.d.roper@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Increase MCR lock timeout
Date: Wed, 4 Oct 2023 09:25:40 +0100 [thread overview]
Message-ID: <985f0a7d-eb26-7739-e158-29b9fc07ff91@linux.intel.com> (raw)
In-Reply-To: <20231003210840.1173401-1-jonathan.cavitt@intel.com>
On 03/10/2023 22:08, Jonathan Cavitt wrote:
> Increase the timeout MCR waits for the steering semaphore
> in intel_gt_mcr_lock by a factor of 10.
Ideally you mention why in the commit message, with some appropriate
level of detail depending on the situation.
+Matt for MCR stuff.
Regards,
Tvrtko
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_mcr.c b/drivers/gpu/drm/i915/gt/intel_gt_mcr.c
> index 326c2ed1d99bb..e3f7fb1248809 100644
> --- a/drivers/gpu/drm/i915/gt/intel_gt_mcr.c
> +++ b/drivers/gpu/drm/i915/gt/intel_gt_mcr.c
> @@ -378,7 +378,7 @@ void intel_gt_mcr_lock(struct intel_gt *gt, unsigned long *flags)
> */
> if (GRAPHICS_VER_FULL(gt->i915) >= IP_VER(12, 70))
> err = wait_for(intel_uncore_read_fw(gt->uncore,
> - MTL_STEER_SEMAPHORE) == 0x1, 100);
> + MTL_STEER_SEMAPHORE) == 0x1, 1000);
>
> /*
> * Even on platforms with a hardware lock, we'll continue to grab
next prev parent reply other threads:[~2023-10-04 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 21:08 [Intel-gfx] [PATCH] drm/i915/gt: Increase MCR lock timeout Jonathan Cavitt
2023-10-03 22:49 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2023-10-04 0:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: Increase MCR lock timeout (rev2) Patchwork
2023-10-04 3:11 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-04 8:25 ` Tvrtko Ursulin [this message]
2023-10-04 15:30 ` [Intel-gfx] [PATCH] drm/i915/gt: Increase MCR lock timeout Matt Roper
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=985f0a7d-eb26-7739-e158-29b9fc07ff91@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=gregory.f.germano@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=saurabhg.gupta@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.