From: Andi Shyti <andi.shyti@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
Intel-gfx@lists.freedesktop.org,
Chris Wilson <chris.p.wilson@intel.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Do not disable preemption for resets
Date: Tue, 26 Sep 2023 11:18:03 +0200 [thread overview]
Message-ID: <ZRKhy6QcQ28Z2cPT@ashyti-mobl2.lan> (raw)
In-Reply-To: <20230705093025.3689748-1-tvrtko.ursulin@linux.intel.com>
Hi Tvrtko,
> Commit ade8a0f59844 ("drm/i915: Make all GPU resets atomic") added a
> preempt disable section over the hardware reset callback to prepare the
> driver for being able to reset from atomic contexts.
>
> In retrospect I can see that the work item at a time was about removing
> the struct mutex from the reset path. Code base also briefly entertained
> the idea of doing the reset under stop_machine in order to serialize
> userspace mmap and temporary glitch in the fence registers (see
> eb8d0f5af4ec ("drm/i915: Remove GPU reset dependence on struct_mutex"),
> but that never materialized and was soon removed in 2caffbf11762
> ("drm/i915: Revoke mmaps and prevent access to fence registers across
> reset") and replaced with a SRCU based solution.
>
> As such, as far as I can see, today we still have a requirement that
> resets must not sleep (invoked from submission tasklets), but no need to
> support invoking them from a truly atomic context.
>
> Given that the preemption section is problematic on RT kernels, since the
> uncore lock becomes a sleeping lock and so is invalid in such section,
> lets try and remove it. Potential downside is that our short waits on GPU
> to complete the reset may get extended if CPU scheduling interferes, but
> in practice that probably isn't a deal breaker.
>
> In terms of mechanics, since the preemption disabled block is being
> removed we just need to replace a few of the wait_for_atomic macros into
> busy looping versions which will work (and not complain) when called from
> non-atomic sections.
looks reasonable, few unrelated questions
> ---
> drivers/gpu/drm/i915/gt/intel_reset.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
> index e2152f75ba2e..6916eba3bd33 100644
> --- a/drivers/gpu/drm/i915/gt/intel_reset.c
> +++ b/drivers/gpu/drm/i915/gt/intel_reset.c
> @@ -167,13 +167,13 @@ static int i915_do_reset(struct intel_gt *gt,
> /* Assert reset for at least 20 usec, and wait for acknowledgement. */
is this /20/50/ ?
> pci_write_config_byte(pdev, I915_GDRST, GRDOM_RESET_ENABLE);
> udelay(50);
> - err = wait_for_atomic(i915_in_reset(pdev), 50);
> + err = _wait_for_atomic(i915_in_reset(pdev), 50, 0);
wait_for_atomic() waits in milliseconds, while _wait_for_atomic()
waits in microseconds, I think you need to update the timer.
Do you think we might need a wait_for_atomic_preempt() macro?
err = wait_for_atomic_preempt(i915_in_reset(pdev), 50);
Thanks,
Andi
next prev parent reply other threads:[~2023-09-26 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 9:30 [PATCH] drm/i915: Do not disable preemption for resets Tvrtko Ursulin
2023-07-26 13:25 ` Sebastian Andrzej Siewior
2023-09-13 8:08 ` Sebastian Andrzej Siewior
2023-09-13 17:04 ` [Intel-gfx] " Valentin Schneider
2023-09-20 11:54 ` Tvrtko Ursulin
2023-09-26 9:18 ` Andi Shyti [this message]
2023-09-26 10:03 ` Tvrtko Ursulin
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=ZRKhy6QcQ28Z2cPT@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=bigeasy@linutronix.de \
--cc=chris.p.wilson@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=paul.gortmaker@windriver.com \
--cc=tvrtko.ursulin@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