From: "Narvaez, Jesus" <jesus.narvaez@intel.com>
To: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/guc: Change GEM_WARN_ON to guc_err to prevent taints in CI
Date: Thu, 15 Aug 2024 10:09:20 -0700 [thread overview]
Message-ID: <a4338df4-764d-4bb5-bd00-73076019e53d@intel.com> (raw)
In-Reply-To: <CH0PR11MB5444A9A2D05F8E115DF635EAE5BA2@CH0PR11MB5444.namprd11.prod.outlook.com>
On 8/9/2024 2:39 PM, Cavitt, Jonathan wrote:
> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Jesus Narvaez
> Sent: Thursday, August 8, 2024 1:50 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Narvaez, Jesus <jesus.narvaez@intel.com>
> Subject: [PATCH] drm/i915/guc: Change GEM_WARN_ON to guc_err to prevent taints in CI
>> This warning was supposed to catch a harmless issue, but changing to
>> guc_error should prevent kernel taints in CI runs.
> I'll defer to your judgement on this, but IMO if we just want to log when this
> happens and guarantee we don't throw kernel taints in CI, we might want to
> consider using guc_info instead. Not blocking on it, though.
> Reviewed-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> -Jonathan Cavitt
Hi Jonathan,
I think using guc_err would be preferred because we still want to catch
the error when it happens, along with preventing kernel taints in CI.
- Jesus Narvaez
>
>> Signed-off-by: Jesus Narvaez <jesus.narvaez@intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
>> index 9400d0eb682b..c3a5d9e1288e 100644
>> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
>> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
>> @@ -2014,11 +2014,12 @@ void intel_guc_submission_reset_finish(struct intel_guc *guc)
>>
>> /*
>> * Technically possible for either of these values to be non-zero here,
>> - * but very unlikely + harmless. Regardless let's add a warn so we can
>> + * but very unlikely + harmless. Regardless let's add an error so we can
>> * see in CI if this happens frequently / a precursor to taking down the
>> * machine.
>> */
>> - GEM_WARN_ON(atomic_read(&guc->outstanding_submission_g2h));
>> + if (atomic_read(&guc->outstanding_submission_g2h))
>> + guc_err(guc, "Unexpected outstanding GuC to Host in reset finish\n");
>> atomic_set(&guc->outstanding_submission_g2h, 0);
>>
>> intel_guc_global_policies_update(guc);
>> --
>> 2.34.1
>>
>>
prev parent reply other threads:[~2024-08-15 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 20:49 [PATCH] drm/i915/guc: Change GEM_WARN_ON to guc_err to prevent taints in CI Jesus Narvaez
2024-08-08 22:08 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-08-09 7:04 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-08-09 21:39 ` [PATCH] " Cavitt, Jonathan
2024-08-15 17:09 ` Narvaez, Jesus [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=a4338df4-764d-4bb5-bd00-73076019e53d@intel.com \
--to=jesus.narvaez@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonathan.cavitt@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