From: "Dong, Zhanjun" <zhanjun.dong@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v3 6/6] drm/xe/guc: Fix page fault by moving guc_submit_fini to devm
Date: Tue, 20 Jan 2026 17:56:34 -0500 [thread overview]
Message-ID: <084a3947-f08f-49f8-a94e-6569dc513360@intel.com> (raw)
In-Reply-To: <aW/nk/slTdY/JHwD@lstrano-desk.jf.intel.com>
On 2026-01-20 3:37 p.m., Matthew Brost wrote:
> On Tue, Jan 20, 2026 at 03:16:21PM -0500, Zhanjun Dong wrote:
>> guc_submit_fini requires access to device memory. Using a device-managed
>> action guarantees the correct ordering of cleanup relative to memory
>> unmapping.
>>
>> Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
>
> Since patch #2 is a fixes and this fixes patch #2, can we squash this
> patch into patch #2?
>
> Aside from that, I do think this is correct as guc_submit_fini now
> initiates a hardware teardown so this should be the DEVM handler.
>
> Matt
To be squashed in next rev.
Zhanjun
>
>> ---
>> drivers/gpu/drm/xe/xe_guc_submit.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
>> index c848615d6057..f29ed62d2b12 100644
>> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
>> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
>> @@ -241,7 +241,7 @@ static bool exec_queue_killed_or_banned_or_wedged(struct xe_exec_queue *q)
>>
>> static int __xe_guc_submit_reset_prepare(struct xe_guc *guc);
>>
>> -static void guc_submit_fini(struct drm_device *drm, void *arg)
>> +static void guc_submit_fini(void *arg)
>> {
>> struct xe_guc *guc = arg;
>> struct xe_device *xe = guc_to_xe(guc);
>> @@ -334,7 +334,7 @@ int xe_guc_submit_init(struct xe_guc *guc, unsigned int num_ids)
>>
>> guc->submission_state.initialized = true;
>>
>> - return drmm_add_action_or_reset(&xe->drm, guc_submit_fini, guc);
>> + return devm_add_action_or_reset(xe->drm.dev, guc_submit_fini, guc);
>> }
>>
>> /*
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2026-01-20 22:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 20:16 [PATCH v3 0/6] Attempt to fixup reset, wedge, unload corner cases Zhanjun Dong
2026-01-20 20:16 ` [PATCH v3 1/6] drm/xe: Always kill exec queues in xe_guc_submit_pause_abort Zhanjun Dong
2026-01-20 20:16 ` [PATCH v3 2/6] drm/xe: Forcefully tear down exec queues in GuC submit fini Zhanjun Dong
2026-01-20 20:16 ` [PATCH v3 3/6] drm/xe: Trigger queue cleanup if not in wedged mode 2 Zhanjun Dong
2026-01-20 20:16 ` [PATCH v3 4/6] drm/xe/guc: Ensure CT state transitions via STOP before DISABLED Zhanjun Dong
2026-01-20 20:54 ` Matthew Brost
2026-01-20 22:56 ` Dong, Zhanjun
2026-01-20 20:16 ` [PATCH v3 5/6] drm/xe/uc: Drop xe_guc_sanitize in favor of managed cleanup Zhanjun Dong
2026-01-20 20:40 ` Matthew Brost
2026-01-20 20:16 ` [PATCH v3 6/6] drm/xe/guc: Fix page fault by moving guc_submit_fini to devm Zhanjun Dong
2026-01-20 20:37 ` Matthew Brost
2026-01-20 22:56 ` Dong, Zhanjun [this message]
2026-01-20 20:23 ` ✓ CI.KUnit: success for Attempt to fixup reset, wedge, unload corner cases Patchwork
2026-01-20 20:35 ` [PATCH v3 0/6] " Matthew Brost
2026-01-20 21:50 ` Dong, Zhanjun
2026-01-20 20:56 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-01-21 3:20 ` ✗ Xe.CI.Full: failure " 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=084a3947-f08f-49f8-a94e-6569dc513360@intel.com \
--to=zhanjun.dong@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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