All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Inject a failure into the initial modeset
Date: Sun, 06 Dec 2020 12:43:07 +0200	[thread overview]
Message-ID: <877dpvb4g4.fsf@intel.com> (raw)
In-Reply-To: <20201204171529.6417-1-chris@chris-wilson.co.uk>

On Fri, 04 Dec 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Experiment with how fault tolerant we are if the initial modeset fails
> and we need to abort the driver load.
>
> Suggested-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_display.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> index 6e5b93f6a25e..86124b8d156d 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -18456,7 +18456,9 @@ static int intel_initial_commit(struct drm_device *dev)
>  		}
>  	}
>  
> -	ret = drm_atomic_commit(state);
> +	ret = -ENODEV;
> +	if (!i915_inject_probe_failure(to_i915(dev)))
> +		ret = drm_atomic_commit(state);

If this is just for CI testing, fine. But for actual merging, please
don't hide the happy day scenario in the probe failure if branch.

BR,
Jani.


>  
>  out:
>  	if (ret == -EDEADLK) {

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-12-06 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 17:14 [Intel-gfx] [PATCH] drm/i915/display: Inject a failure into the initial modeset Chris Wilson
2020-12-04 17:15 ` Chris Wilson
2020-12-06 10:43   ` Jani Nikula [this message]
2020-12-06 13:20     ` Chris Wilson
2020-12-04 20:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Inject a failure into the initial modeset (rev2) Patchwork
2020-12-04 23:25 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-12-06 14:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Inject a failure into the initial modeset (rev3) Patchwork
2020-12-06 19:13 ` [Intel-gfx] ✓ 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=877dpvb4g4.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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 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.