From: "Dong, Zhanjun" <zhanjun.dong@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH v1] drm/i915/guc: Always disable interrupt ahead of synchronize_irq
Date: Mon, 3 Feb 2025 18:50:16 -0500 [thread overview]
Message-ID: <0613d63c-d236-45e6-a610-97b6a36eee75@intel.com> (raw)
In-Reply-To: <Z6DEtCX-XzJE8cwm@ashyti-mobl2.lan>
On 2025-02-03 8:29 a.m., Andi Shyti wrote:
> Hi,
>
> Please, next time, do not remove the mailing and the other folks
> you cc'ed.
>
> I'm adding back the mailing list and Daniele who has commented
> before.
Thanks, I also found my previous response click on "reply", not the
"reply all".
>
> ...
>
>>>> 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")
>>>
>>> There is an issue here, each fixes is introduced in different
>>> kernel versions and they can't be mixed all together as it would
>>> be impossible to backport them to the stable brances.
>>>
>>> E.g.:
>>> Fixes: 3e7abf814193 ("drm/i915: Extract GT render power state management")
>>> Cc: <stable@vger.kernel.org> # v5.5+
>>>
>>> Fixes: 2ae096872a2c ("drm/i915/pxp: Implement PXP irq handler")
>>> Cc: <stable@vger.kernel.org> # v5.16+
>>>
>>> Fixes: 54c52a841250 ("drm/i915/guc: Correctly handle GuC interrupts on Gen11")
>>> Cc: <stable@vger.kernel.org> # v5.3+
>>>
>>> Fixes: 26705e20752a ("drm/i915: Support for GuC interrupts")
>>> Cc: <stable@vger.kernel.org> # v4.10+
>>>
>>> Could you please split this patch in the four different patches
>>> that address the four different fixes?
>> Sure, will split it in next rev.
>
> First of all we need to understand if those Fixes are really
> needed or not. Daniele in his review has pointed out that...
I agree with Daniele, these fixes is not needed.
>
>>>>
>>>
>>> No blank lines in the tag section, please.
>>>
>>>> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
>>>>
>>>> ---
>>>> Cc: Alan Previn <alan.previn.teres.alexis@intel.com>
>>>> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>>>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>>> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
>>>> Cc: Andi Shyti <andi.shyti@intel.com>
>>>> ---
>>>> drivers/gpu/drm/i915/gt/intel_rps.c | 3 +--
>>>> drivers/gpu/drm/i915/gt/uc/intel_guc.c | 4 ++--
>>>> drivers/gpu/drm/i915/pxp/intel_pxp_irq.c | 2 +-
>>>> 3 files changed, 4 insertions(+), 5 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/i915/gt/intel_rps.c b/drivers/gpu/drm/i915/gt/intel_rps.c
>>>> index fa304ea088e4..0fe7a8d7f460 100644
>>>> --- a/drivers/gpu/drm/i915/gt/intel_rps.c
>>>> +++ b/drivers/gpu/drm/i915/gt/intel_rps.c
>>>> @@ -244,8 +244,8 @@ static void rps_disable_interrupts(struct intel_rps *rps)
>>>> gen6_gt_pm_disable_irq(gt, GEN6_PM_RPS_EVENTS);
>>>> spin_unlock_irq(gt->irq_lock);
>>>> + rps_reset_interrupts(rps);
>
> ... the interrupts here are already disabled (read a couple of
> lines above).
>
> What is the reproduction rate of the issue? And how have you
> tested it?
I run the issue igt test
(https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13454) on ARL
for more than 3000 loops, but no reproduce at all. This issue seems
happens few month a time, and auto closed by Jira as no reproduce after
few weeks.
Due to the issue is hard to reproduce, what I do now is by code analysis.
Regards,
Zhanjun Dong
>
> Thanks,
> Andi
>
>>>> intel_synchronize_irq(gt->i915);
>>>> -
>>>
>>> Sebastian has already commented in his review, but please don't
>>> remove this blank line.
>>>
>>> Andi
>>>
>>>> /*
>>>> * Now that we will not be generating any more work, flush any
>>>> * outstanding tasks. As we are called on the RPS idle path,
next prev parent reply other threads:[~2025-02-03 23:51 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 ` [PATCH v1] " Sebastian Brzezinka
2025-01-27 15:21 ` 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 [this message]
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=0613d63c-d236-45e6-a610-97b6a36eee75@intel.com \
--to=zhanjun.dong@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox