From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
"Marcin Ślusarz" <marcin.slusarz@gmail.com>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/gt: obey "reset" module parameter
Date: Tue, 18 Aug 2020 13:49:19 -0400 [thread overview]
Message-ID: <20200818174919.GA3311723@intel.com> (raw)
In-Reply-To: <159775188083.667.5734044425203263287@build.alporthouse.com>
On Tue, Aug 18, 2020 at 12:58:00PM +0100, Chris Wilson wrote:
> Quoting Marcin Ślusarz (2020-08-18 12:36:07)
> > From: Marcin Ślusarz <marcin.slusarz@intel.com>
> >
> > For some reason intel_gt_reset attempts to reset the GPU twice.
> > On one code path (do_reset) "reset" parameter is obeyed, but is
> > not on the other one (__intel_gt_set_wedged).
>
> It's not that simple, we do want to force __intel_gt_set_wedged() to
> cancel whatever is running on the GPU as it is used for more than just
> failing resets (e.g. around control boundaries) regardless of what the
> user may want.
>
> I'm loathe to add a parameter just to enable unsafe behaviour, but that
> may be the compromise.
we probably need this compromise for these cases Marcin faced...
what about moving this to intel_get_gpu_reset()?
@bool intel_has_gpu_reset(const struct intel_gt *gt)
- if (!gt->i915->params.reset)
- return NULL;
@ static reset_func intel_get_gpu_reset(const struct intel_gt *gt)
+ if (!gt->i915->params.reset)
+ return NULL;
> -Chris
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-08-18 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 11:36 [Intel-gfx] [PATCH 1/2] drm/i915/gt: obey "reset" module parameter Marcin Ślusarz
2020-08-18 11:37 ` [Intel-gfx] [PATCH 2/2] drm/i915/gt: raise logging level of "gpu reset disabled" message Marcin Ślusarz
2020-08-18 11:44 ` Chris Wilson
2020-08-18 11:56 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [1/2] drm/i915/gt: obey "reset" module parameter Patchwork
2020-08-18 11:58 ` [Intel-gfx] [PATCH 1/2] " Chris Wilson
2020-08-18 17:49 ` Rodrigo Vivi [this message]
2020-08-18 18:12 ` Chris Wilson
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=20200818174919.GA3311723@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marcin.slusarz@gmail.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.