From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: "Das, Nirmoy" <nirmoy.das@linux.intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: fix remaining_timeout in intel_gt_retire_requests_timeout
Date: Fri, 25 Mar 2022 13:33:58 -0700 [thread overview]
Message-ID: <eeeedf74-4793-8b83-dd81-cb2cc3c22ea1@intel.com> (raw)
In-Reply-To: <71bbc214-b3a0-d3ca-c3bc-fe6d0b8d162c@linux.intel.com>
On 3/25/2022 11:37 AM, Das, Nirmoy wrote:
>
> On 3/25/2022 6:58 PM, Daniele Ceraolo Spurio wrote:
>> In intel_gt_wait_for_idle, we use the remaining timeout returned from
>> intel_gt_retire_requests_timeout to wait on the GuC being idle. However,
>> the returned variable can have a negative value if something goes wrong
>> during the wait, leading to us hitting a GEM_BUG_ON in the GuC wait
>> function.
>> To fix this, make sure to only return the timeout if it is positive.
>>
>> Fixes: b97060a99b01b ("drm/i915/guc: Update intel_gt_wait_for_idle to
>> work with GuC")
>> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>> Cc: Matthew Brost <matthew.brost@intel.com>
>> Cc: John Harrison <john.c.harrison@intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/intel_gt_requests.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_requests.c
>> b/drivers/gpu/drm/i915/gt/intel_gt_requests.c
>> index edb881d756309..ef70c209976d8 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_gt_requests.c
>> +++ b/drivers/gpu/drm/i915/gt/intel_gt_requests.c
>> @@ -197,7 +197,7 @@ out_active: spin_lock(&timelines->lock);
>> active_count++;
>> if (remaining_timeout)
>> - *remaining_timeout = timeout;
>> + *remaining_timeout = timeout > 0 ? timeout : 0;
>
>
> Should the last flush_submission() be "if ( timeout > 0
> &&flush_submission(gt, timeout))" ?
I considered it, but flush_submission only checks for timeout != 0 so it
won't accidentally make use of a negative value thinking it's positive.
I don't know if the flush is purposely done even if timeout is negative
or if that's a mistake, but that code has been there long before we
modified the function to return the remaining timeout and never seems to
have caused issues, so I decided not to change it.
Daniele
>
>
> Nirmoy
>
>> return active_count ? timeout : 0;
>> }
next prev parent reply other threads:[~2022-03-25 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 17:58 [Intel-gfx] [PATCH] drm/i915: fix remaining_timeout in intel_gt_retire_requests_timeout Daniele Ceraolo Spurio
2022-03-25 18:29 ` Matthew Brost
2022-03-25 18:37 ` Das, Nirmoy
2022-03-25 20:33 ` Ceraolo Spurio, Daniele [this message]
2022-03-28 9:16 ` Das, Nirmoy
2022-03-25 19:39 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for " Patchwork
2022-03-25 20:02 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
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=eeeedf74-4793-8b83-dd81-cb2cc3c22ea1@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@linux.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