From: "Timur Kristóf" <timur.kristof@gmail.com>
To: Tvrtko Ursulin <tursulin@ursulin.net>,
Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
christian.koenig@amd.com, pierre-eric.pelloux-prayer@amd.com,
Natalie Vock <natalie.vock@gmx.de>
Subject: Re: [PATCH 07/11] drm/amdgpu/gfx6: Properly enable/disable priv_req and priv_inst interrupts
Date: Mon, 20 Jul 2026 15:59:26 +0200 [thread overview]
Message-ID: <XMA6udstQameeRGAv_w1iw@gmail.com> (raw)
In-Reply-To: <CADnq5_OTNp-+mJ=BLU6p4vF4B4xrim+8hOVb6fbkmXC01PxURg@mail.gmail.com>
On Thursday, July 16, 2026 4:00:50 PM Central European Summer Time Alex
> >
> > Right, AFAIU assuming the CP hangs, instead of waiting for the TDR
> > timeout with this patch it will be instant via drm_sched_fault() called
> > from either irq handler. Or if CP does not hang but somehow ends up
> > going over it with corruption with this patch it will insta GPU hang.
> >
> > In any case I think it is needed to have a definitive answer whether the
> > interrupts were not enabled until now, and if so, also exercise the
> > until now unused code paths just to make sure it all works as expected.
> > Presumably there are test cases which trigger both conditions?
> >
> > Then I would suggest putting this info in the commit message. That is,
> > instead of saying "These were used without ever calling get()/put() on
> > them." expand with the full story so the whole situation is clear both
> > before and after the patch.
> >
> > Assuming interrupts were not enabled until now, that the unused irq
>
> > handlers work as expected, and with the improved commit message:
> The interrupts would not have been enabled if get() was never called.
> I think they were never enabled because radeon didn't implement
> support and this code was ported from radeon.
> >
> > Unless you don't have the hardware to test it and there are no existing
> > test cases to verify it?
>
> An example test would be attempting to access a privileged register
> from a user IB.
Unfortunately I don't have any test cases like that. We've had some plans for
writing such test cases and integrating them in IGT but the person who was
going to write them left and since then I haven't managed to get around to it
yet. So I've mainly just used the hang test suite for testing that soft reset
works.
If you have doubts about these interrupts on GFX6 then I think we should just
drop this patch until we finish those test cases.
I still plan to write those test cases but it's really tedious and thankless
work, so it hasn't been my priority thus far.
Best regards,
Timur
next prev parent reply other threads:[~2026-07-20 13:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 13:06 [PATCH 00/11] drm/amdgpu/gfx6: Use GFX IP block soft reset on GFX6 Timur Kristóf
2026-07-13 13:06 ` [PATCH 01/11] drm/amdgpu/gfx6: Improve emit_cntxcntl() Timur Kristóf
2026-07-13 13:07 ` [PATCH 02/11] drm/amdgpu/gfx6: Fixup emitting SWITCH_BUFFER packets Timur Kristóf
2026-07-13 13:07 ` [PATCH 03/11] drm/amdgpu/gfx6: Use PFP on the compute queues too Timur Kristóf
2026-07-13 13:07 ` [PATCH 04/11] drm/amdgpu/gfx6: Initialize compute rings before CP start Timur Kristóf
2026-07-13 13:07 ` [PATCH 05/11] drm/amdgpu/gfx6: Clean up rings during reset Timur Kristóf
2026-07-13 13:07 ` [PATCH 06/11] drm/amdgpu/gfx6: Execute CLEAR_STATE when initializing compute rings Timur Kristóf
2026-07-13 13:07 ` [PATCH 07/11] drm/amdgpu/gfx6: Properly enable/disable priv_req and priv_inst interrupts Timur Kristóf
2026-07-15 10:19 ` Tvrtko Ursulin
2026-07-15 10:53 ` Timur Kristóf
2026-07-15 11:22 ` Tvrtko Ursulin
2026-07-15 19:23 ` Timur Kristóf
2026-07-16 11:05 ` Tvrtko Ursulin
2026-07-16 14:00 ` Alex Deucher
2026-07-20 13:59 ` Timur Kristóf [this message]
2026-07-13 13:07 ` [PATCH 08/11] drm/amdgpu/gfx6: Adjust how harvested TCCs are set up Timur Kristóf
2026-07-13 13:07 ` [PATCH 09/11] drm/amdgpu/gfx6: Use COND_EXEC Timur Kristóf
2026-07-13 13:07 ` [PATCH 10/11] drm/amdgpu/gfx6: Add IP block soft reset implementation Timur Kristóf
2026-07-13 13:07 ` [PATCH 11/11] drm/amdgpu/gfx6: Enable IP block soft reset as a GPU recovery method Timur Kristóf
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=XMA6udstQameeRGAv_w1iw@gmail.com \
--to=timur.kristof@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=natalie.vock@gmx.de \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=tursulin@ursulin.net \
/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.