Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sujaritha <sujaritha.sundaresan@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/1] drm/i915: Fixing error code for WOPCM initialization
Date: Tue, 5 Mar 2019 16:11:38 -0800	[thread overview]
Message-ID: <e7de215f-f55d-9e12-1cf5-c48a92e15600@intel.com> (raw)
In-Reply-To: <aafed438-260e-86f0-6201-4164e1247db2@intel.com>


On 3/5/19 2:06 PM, Daniele Ceraolo Spurio wrote:
>
>
> On 3/5/19 2:05 PM, Daniele Ceraolo Spurio wrote:
>>
>>
>> On 3/4/19 4:55 PM, Sujaritha Sundaresan wrote:
>>> Replacing the -E2BIG error code return for WOPCM
>>> initialization with -ENODEV. This will prevent the pci from
>>> picking this up as a warning during fault injection testing.
>>
>> To clarify, we want to silence this:
>>
>
> forgot to paste the log...
>
> <4> [381.569479] i915: probe of 0000:00:02.0 failed with error -7
>
> Daniele
>
>>
>>
>>>
>>> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>>> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
>>> Signed-off-by: Sujaritha Sundaresan <sujaritha.sundaresan@intel.com>
>>> ---
>>>   drivers/gpu/drm/i915/intel_wopcm.c | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/intel_wopcm.c 
>>> b/drivers/gpu/drm/i915/intel_wopcm.c
>>> index f82a415ea2ba..a651557e6e4e 100644
>>> --- a/drivers/gpu/drm/i915/intel_wopcm.c
>>> +++ b/drivers/gpu/drm/i915/intel_wopcm.c
>>> @@ -169,7 +169,7 @@ int intel_wopcm_init(struct intel_wopcm *wopcm)
>>>       GEM_BUG_ON(!wopcm->size);
>>>       if (i915_inject_load_failure())
>>> -        return -E2BIG;
>>> +        return -ENODEV;
>>
>> Would it be better to just change the final return code in 
>> i915_pci_probe() to ENODEV?
>>
>> i.e.
>>      err = i915_driver_load(pdev, ent);
>>      if (err)
>>          return i915_error_injected() ? -ENODEV : err;
>>
>> This way we can test that the possible error codes (E2BIG in this 
>> case) don't hit issues in dedicated cases during onion unwinding.
>>
>> Daniele
>>
>>>       if (guc_fw_size >= wopcm->size) {
>>>           DRM_ERROR("GuC FW (%uKiB) is too big to fit in WOPCM.",
>>>

Okay this approach seems to provide a wider fix. Will make this change. 
Thanks for the review.

Sujaritha

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-03-06  0:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05  0:55 [PATCH 1/1] drm/i915: Fixing error code for WOPCM initialization Sujaritha Sundaresan
2019-03-05  2:23 ` ✓ Fi.CI.BAT: success for series starting with [1/1] " Patchwork
2019-03-05  7:25 ` ✓ Fi.CI.IGT: " Patchwork
2019-03-05 22:05 ` [PATCH 1/1] " Daniele Ceraolo Spurio
2019-03-05 22:06   ` Daniele Ceraolo Spurio
2019-03-06  0:11     ` Sujaritha [this message]
2019-03-06  0:30 ` [PATCH v2] drm/i915/guc: " Sujaritha Sundaresan
2019-03-06  8:41   ` Michal Wajdeczko
2019-03-06  8:45     ` Chris Wilson
2019-03-06  9:01       ` Michal Wajdeczko
2019-03-06  9:08         ` Chris Wilson
2019-03-06 18:44           ` Sujaritha
2019-03-06 19:17           ` Sundaresan, Sujaritha
2019-03-06  1:31 ` ✓ Fi.CI.BAT: success for series starting with [v2] drm/i915/guc: Fixing error code for WOPCM initialization (rev2) Patchwork
2019-03-06  9:10 ` ✓ Fi.CI.IGT: " 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=e7de215f-f55d-9e12-1cf5-c48a92e15600@intel.com \
    --to=sujaritha.sundaresan@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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