From: "Lis, Tomasz" <tomasz.lis@intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: intel-xe@lists.freedesktop.org,
"Michał Wajdeczko" <michal.wajdeczko@intel.com>,
"Piotr Piórkowski" <piotr.piorkowski@intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Lucas De Marchi" <lucas.demarchi@intel.com>
Subject: Re: [PATCH v3 7/7] drm/xe/vf: Post migration, repopulate ring area for pending request
Date: Sat, 31 May 2025 01:03:05 +0200 [thread overview]
Message-ID: <a41dc60c-7ee6-4583-af6f-d99c77639d5a@intel.com> (raw)
In-Reply-To: <twcothnuc6agtazwjigkjpmpu4zuqa557lx7jbo23ohzm2ufaq@ecd7fu6tuopa>
[-- Attachment #1: Type: text/plain, Size: 6389 bytes --]
On 28.05.2025 12:54, Michał Winiarski wrote:
> On Tue, May 20, 2025 at 01:19:25AM +0200, Tomasz Lis wrote:
>> The commands within ring area allocated for a request may contain
>> references to GGTT. These references require update after VF
>> migration, in order to continue any preempted LRCs, or jobs which
>> were emitted to the ring but not sent to GuC yet.
>>
>> This change calls the emit function again for all such jobs,
>> as part of post-migration recovery.
>>
>> v2: Moved few functions to better files
>>
>> Signed-off-by: Tomasz Lis<tomasz.lis@intel.com>
>> Cc: Michal Wajdeczko<michal.wajdeczko@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_exec_queue.c | 17 +++++++++++++++++
>> drivers/gpu/drm/xe/xe_exec_queue.h | 2 ++
>> drivers/gpu/drm/xe/xe_guc_submit.c | 19 +++++++++++++++++++
>> drivers/gpu/drm/xe/xe_guc_submit.h | 2 ++
>> drivers/gpu/drm/xe/xe_sriov_vf.c | 13 ++++++++++++-
>> 5 files changed, 52 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_exec_queue.c b/drivers/gpu/drm/xe/xe_exec_queue.c
>> index 9c3e568400e0..0488d80d5b99 100644
>> --- a/drivers/gpu/drm/xe/xe_exec_queue.c
>> +++ b/drivers/gpu/drm/xe/xe_exec_queue.c
>> @@ -1056,3 +1056,20 @@ void xe_exec_queue_contexts_hwsp_rebase(struct xe_exec_queue *q)
>> xe_lrc_update_hwctx_regs_with_address(q->lrc[i]);
>> }
>> }
>> +
>> +/**
>> + * xe_exec_queue_jobs_ring_restore - Re-emit ring commands of requests pending on given queue.
>> + * @q: the &xe_exec_queue struct instance
>> + */
>> +void xe_exec_queue_jobs_ring_restore(struct xe_exec_queue *q)
>> +{
>> + struct xe_gpu_scheduler *sched = &q->guc->sched;
>> + struct xe_sched_job *job;
>> +
>> + list_for_each_entry(job, &sched->base.pending_list, drm.list) {
>> + if (xe_sched_job_is_error(job))
>> + continue;
>> +
>> + q->ring_ops->emit_job(job);
>> + }
> Shouldn't we take the lock that protects sched->base.pending_list?
> I know we're under guc->submission_state_lock, but that doesn't protect
> it, right?
Right, the lack of protection is problematic here. There are two
solutions - either to switch to `list_for_each_entry_safe` or to take
`sched->base.job_list_lock`.
Normally I'd prefer the safe iterating, as this doesn't add to
complexity. It is often the preferred solution if our iteration does not
change the list.
But this spin lock is simple enough to not cause any problems if taken
here, I think. The code within the lock never waits for HW, which is the
main indicator on whether it can be used within the recovery.
I will alter the code to take the lock. Unless I'll discover some
non-obvious dependencies which would make it problematic.
-Tomasz
> Other than that - LGTM.
>
> Thanks,
> -Michał
>
>> +}
>> diff --git a/drivers/gpu/drm/xe/xe_exec_queue.h b/drivers/gpu/drm/xe/xe_exec_queue.h
>> index 1d399a33c5c0..67c2baa42c0f 100644
>> --- a/drivers/gpu/drm/xe/xe_exec_queue.h
>> +++ b/drivers/gpu/drm/xe/xe_exec_queue.h
>> @@ -92,4 +92,6 @@ void xe_exec_queue_update_run_ticks(struct xe_exec_queue *q);
>>
>> void xe_exec_queue_contexts_hwsp_rebase(struct xe_exec_queue *q);
>>
>> +void xe_exec_queue_jobs_ring_restore(struct xe_exec_queue *q);
>> +
>> #endif
>> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
>> index 990f3265c7ad..a60e0575cc56 100644
>> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
>> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
>> @@ -766,6 +766,25 @@ guc_exec_queue_run_job(struct drm_sched_job *drm_job)
>> return fence;
>> }
>>
>> +/**
>> + * xe_guc_jobs_ring_rebase - Re-emit ring commands of requests pending
>> + * on all queues under a guc.
>> + * @guc: the &xe_guc struct instance
>> + */
>> +void xe_guc_jobs_ring_rebase(struct xe_guc *guc)
>> +{
>> + struct xe_exec_queue *q;
>> + unsigned long index;
>> +
>> + mutex_lock(&guc->submission_state.lock);
>> + xa_for_each(&guc->submission_state.exec_queue_lookup, index, q) {
>> + if (exec_queue_killed_or_banned_or_wedged(q))
>> + continue;
>> + xe_exec_queue_jobs_ring_restore(q);
>> + }
>> + mutex_unlock(&guc->submission_state.lock);
>> +}
>> +
>> static void guc_exec_queue_free_job(struct drm_sched_job *drm_job)
>> {
>> struct xe_sched_job *job = to_xe_sched_job(drm_job);
>> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.h b/drivers/gpu/drm/xe/xe_guc_submit.h
>> index 2cc44298465f..e31680a08dba 100644
>> --- a/drivers/gpu/drm/xe/xe_guc_submit.h
>> +++ b/drivers/gpu/drm/xe/xe_guc_submit.h
>> @@ -33,6 +33,8 @@ int xe_guc_exec_queue_memory_cat_error_handler(struct xe_guc *guc, u32 *msg,
>> int xe_guc_exec_queue_reset_failure_handler(struct xe_guc *guc, u32 *msg, u32 len);
>> int xe_guc_error_capture_handler(struct xe_guc *guc, u32 *msg, u32 len);
>>
>> +void xe_guc_jobs_ring_rebase(struct xe_guc *guc);
>> +
>> struct xe_guc_submit_exec_queue_snapshot *
>> xe_guc_exec_queue_snapshot_capture(struct xe_exec_queue *q);
>> void
>> diff --git a/drivers/gpu/drm/xe/xe_sriov_vf.c b/drivers/gpu/drm/xe/xe_sriov_vf.c
>> index 0a9761b6ffb5..3e7eb365f2e9 100644
>> --- a/drivers/gpu/drm/xe/xe_sriov_vf.c
>> +++ b/drivers/gpu/drm/xe/xe_sriov_vf.c
>> @@ -8,6 +8,7 @@
>> #include "xe_assert.h"
>> #include "xe_device.h"
>> #include "xe_exec_queue_types.h"
>> +#include "xe_guc_exec_queue_types.h"
>> #include "xe_gt.h"
>> #include "xe_gt_sriov_printk.h"
>> #include "xe_gt_sriov_vf.h"
>> @@ -16,6 +17,7 @@
>> #include "xe_irq.h"
>> #include "xe_lrc.h"
>> #include "xe_pm.h"
>> +#include "xe_sched_job_types.h"
>> #include "xe_sriov.h"
>> #include "xe_sriov_printk.h"
>> #include "xe_sriov_vf.h"
>> @@ -245,6 +247,15 @@ static void vf_post_migration_fixup_contexts(struct xe_device *xe)
>> }
>> }
>>
>> +static void vf_post_migration_fixup_jobs(struct xe_device *xe)
>> +{
>> + struct xe_gt *gt;
>> + unsigned int id;
>> +
>> + for_each_gt(gt, xe, id)
>> + xe_guc_jobs_ring_rebase(>->uc.guc);
>> +}
>> +
>> static void vf_post_migration_fixup_ctb(struct xe_device *xe)
>> {
>> struct xe_gt *gt;
>> @@ -327,7 +338,7 @@ static void vf_post_migration_recovery(struct xe_device *xe)
>> need_fixups = vf_post_migration_fixup_ggtt_nodes(xe);
>> if (need_fixups) {
>> vf_post_migration_fixup_contexts(xe);
>> - /* FIXME: add the recovery steps */
>> + vf_post_migration_fixup_jobs(xe);
>> vf_post_migration_fixup_ctb(xe);
>> }
>>
>> --
>> 2.25.1
>>
[-- Attachment #2: Type: text/html, Size: 7326 bytes --]
next prev parent reply other threads:[~2025-05-30 23:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 23:19 [PATCH v3 0/7] drm/xe/vf: Post-migration recovery of queues and jobs Tomasz Lis
2025-05-19 23:19 ` [PATCH v3 1/7] drm/xe/sa: Avoid caching GGTT address within the manager Tomasz Lis
2025-05-19 23:19 ` [PATCH v3 2/7] drm/xe/vf: Finish RESFIX by reset if CTB not enabled Tomasz Lis
2025-05-27 11:56 ` K V P, Satyanarayana
2025-05-27 14:14 ` Lis, Tomasz
2025-05-19 23:19 ` [PATCH v3 3/7] drm/xe/vf: Pause submissions during RESFIX fixups Tomasz Lis
2025-05-27 13:10 ` K V P, Satyanarayana
2025-05-27 14:28 ` Lis, Tomasz
2025-05-28 20:16 ` Michał Winiarski
2025-05-31 0:05 ` Lis, Tomasz
2025-05-19 23:19 ` [PATCH v3 4/7] drm/xe: Block reset while recovering from VF migration Tomasz Lis
2025-05-28 20:02 ` Michał Winiarski
2025-06-03 20:23 ` Lis, Tomasz
2025-05-19 23:19 ` [PATCH v3 5/7] drm/xe/vf: Rebase HWSP of all contexts after migration Tomasz Lis
2025-05-27 13:45 ` K V P, Satyanarayana
2025-05-28 12:49 ` Michał Winiarski
2025-06-03 20:23 ` Lis, Tomasz
2025-05-19 23:19 ` [PATCH v3 6/7] drm/xe/vf: Rebase MEMIRQ structures for " Tomasz Lis
2025-05-27 14:06 ` K V P, Satyanarayana
2025-05-28 10:44 ` Michał Winiarski
2025-05-29 1:19 ` Lis, Tomasz
2025-05-19 23:19 ` [PATCH v3 7/7] drm/xe/vf: Post migration, repopulate ring area for pending request Tomasz Lis
2025-05-28 10:54 ` Michał Winiarski
2025-05-30 23:03 ` Lis, Tomasz [this message]
2025-05-20 0:00 ` ✓ CI.Patch_applied: success for drm/xe/vf: Post-migration recovery of queues and jobs (rev3) Patchwork
2025-05-20 0:00 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-20 0:01 ` ✓ CI.KUnit: success " Patchwork
2025-05-20 0:11 ` ✓ CI.Build: " Patchwork
2025-05-20 0:14 ` ✓ CI.Hooks: " Patchwork
2025-05-20 0:15 ` ✓ CI.checksparse: " Patchwork
2025-05-20 0:39 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-20 12:47 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-27 5:49 ` ✗ CI.Patch_applied: " 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=a41dc60c-7ee6-4583-af6f-d99c77639d5a@intel.com \
--to=tomasz.lis@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.brost@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=michal.winiarski@intel.com \
--cc=piotr.piorkowski@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