From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Luca Coelho <luciano.coelho@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 1/2] Revert "FIXME: drm/i915/crtc: use irqsave for locking event_lock"
Date: Thu, 12 Oct 2023 14:59:42 -0400 [thread overview]
Message-ID: <ZShCHmEtCjXzfsiL@intel.com> (raw)
In-Reply-To: <20230919094737.743358-2-luciano.coelho@intel.com>
On Tue, Sep 19, 2023 at 12:47:36PM +0300, Luca Coelho wrote:
> This reverts commit 0aff77c2fbd20da430763bdb25db5eaa6245650a.
>
> The interrupts are already disabled at this point, so there's no need
> to use _irqsave()/_irqrestore() in this context. Most other callers
> of the drm_crtc_arm_vblank_event(), outside the i915 driver, call it
> immediately after locking the spinlock with _irqsave(), or at least
> _irq(), and that may be the reason why this was added unnecessarily
> here.
>
> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_crtc.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_crtc.c b/drivers/gpu/drm/i915/display/intel_crtc.c
> index 23bb3bb9c7db..182c6dd64f47 100644
> --- a/drivers/gpu/drm/i915/display/intel_crtc.c
> +++ b/drivers/gpu/drm/i915/display/intel_crtc.c
> @@ -670,15 +670,13 @@ void intel_pipe_update_end(struct intel_crtc_state *new_crtc_state)
> drm_crtc_accurate_vblank_count(&crtc->base) + 1,
> false);
> } else if (new_crtc_state->uapi.event) {
> - unsigned long flags;
> -
> drm_WARN_ON(&dev_priv->drm,
> drm_crtc_vblank_get(&crtc->base) != 0);
>
> - spin_lock_irqsave(&crtc->base.dev->event_lock, flags);
> + spin_lock(&crtc->base.dev->event_lock);
> drm_crtc_arm_vblank_event(&crtc->base,
> new_crtc_state->uapi.event);
> - spin_unlock_irqrestore(&crtc->base.dev->event_lock, flags);
> + spin_unlock(&crtc->base.dev->event_lock);
>
> new_crtc_state->uapi.event = NULL;
> }
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-10-12 18:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 9:47 [Intel-xe] [PATCH 0/2] Some changes for Xe in spinlock handling in i915/display Luca Coelho
2023-09-19 9:47 ` [Intel-xe] [PATCH 1/2] Revert "FIXME: drm/i915/crtc: use irqsave for locking event_lock" Luca Coelho
2023-10-12 18:59 ` Rodrigo Vivi [this message]
2023-09-19 9:47 ` [Intel-xe] [PATCH 2/2] drm/i915: handle uncore spinlock when not available Luca Coelho
2023-10-12 19:05 ` Rodrigo Vivi
2023-10-18 11:45 ` Coelho, Luciano
2023-09-19 10:05 ` [Intel-xe] ✓ CI.Patch_applied: success for Some changes for Xe in spinlock handling in i915/display Patchwork
2023-09-19 10:06 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-19 10:07 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-19 10:14 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-19 10:14 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-19 10:16 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-19 10:46 ` [Intel-xe] ✓ CI.BAT: success " 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=ZShCHmEtCjXzfsiL@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=luciano.coelho@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 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.