From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: Zhanjun Dong <zhanjun.dong@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>
Cc: Alan Previn <alan.previn.teres.alexis@intel.com>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Michal Wajdeczko <michal.wajdeczko@intel.com>,
Andi Shyti <andi.shyti@intel.com>
Subject: Re: [PATCH v1] drm/i915/guc: Always disable interrupt ahead of synchronize_irq
Date: Mon, 27 Jan 2025 14:44:29 +0000 [thread overview]
Message-ID: <D7CXPGEMO1T0.39WDP8CFIFXL5@intel.com> (raw)
In-Reply-To: <20250123162351.1364395-1-zhanjun.dong@intel.com>
Hi Zhanjun
There is a missing newline at drm-tip/drivers/gpu/drm/i915/gt/intel_rps.c:249
Overall, LGTM.
On Thu Jan 23, 2025 at 4:23 PM UTC, Zhanjun Dong wrote:
> The purpose of synchronize_irq is to wait for any pending IRQ handlers for the
> interrupt to complete, if synchronize_irq called before interrupt disabled, an
> tiny timing window created, where no more pending IRQ, but interrupt not
> disabled yet. Meanwhile, if the interrupt event happened in this timing window,
> an unexpected IRQ handling will be triggered.
>
> Fixed by always disable interrupt ahead of synchronize_irq.
>
> Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13454
> Fixes: 26705e20752a ("drm/i915: Support for GuC interrupts")
> Fixes: 54c52a841250 ("drm/i915/guc: Correctly handle GuC interrupts on Gen11")
> Fixes: 2ae096872a2c ("drm/i915/pxp: Implement PXP irq handler")
> Fixes: 3e7abf814193 ("drm/i915: Extract GT render power state management")
>
> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
>
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
--
Best regards,
Sebastian
next prev parent reply other threads:[~2025-01-27 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 16:23 [PATCH v1] drm/i915/guc: Always disable interrupt ahead of synchronize_irq Zhanjun Dong
2025-01-23 16:53 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2025-01-23 17:07 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-24 9:43 ` ✗ i915.CI.Full: failure " Patchwork
2025-01-27 14:44 ` Sebastian Brzezinka [this message]
2025-01-27 15:21 ` [PATCH v1] " Andi Shyti
[not found] ` <41833264-348a-443e-ba89-f559cc9114cb@intel.com>
2025-02-03 13:29 ` Andi Shyti
2025-02-03 23:50 ` Dong, Zhanjun
2025-02-04 10:25 ` Andi Shyti
2025-01-27 17:12 ` Daniele Ceraolo Spurio
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=D7CXPGEMO1T0.39WDP8CFIFXL5@intel.com \
--to=sebastian.brzezinka@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=andi.shyti@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=zhanjun.dong@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