Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Philipp Stanner <pstanner@redhat.com>
Cc: <intel-xe@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>, <dakr@kernel.org>,
	<ltuikov89@gmail.com>
Subject: Re: [PATCH v2] drm/sched: Mark scheduler work queues with WQ_MEM_RECLAIM
Date: Thu, 24 Oct 2024 15:47:14 +0000	[thread overview]
Message-ID: <ZxpsAogpxOjU+58p@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <eb625699d08db636e19c5141f681759849ff4a63.camel@redhat.com>

On Thu, Oct 24, 2024 at 05:35:47PM +0200, Philipp Stanner wrote:
> On Wed, 2024-10-23 at 16:59 -0700, Matthew Brost wrote:
> > drm_gpu_scheduler.submit_wq is used to submit jobs, jobs are in the
> > path
> > of dma-fences, and dma-fences are in the path of reclaim. Mark
> > scheduler
> > work queue with WQ_MEM_RECLAIM to ensure forward progress during
> > reclaim; without WQ_MEM_RECLAIM, work queues cannot make forward
> > progress during reclaim.
> > 
> > v2:
> >  - Fixes tags (Philipp)
> >  - Reword commit message (Philipp)
> > 
> > Cc: Luben Tuikov <ltuikov89@gmail.com>
> > Cc: Danilo Krummrich <dakr@kernel.org>
> > Cc: Philipp Stanner <pstanner@redhat.com>
> > Cc: stable@vger.kernel.org
> > Fixes: 34f50cc6441b ("drm/sched: Use drm sched lockdep map for
> > submit_wq")
> > Fixes: a6149f039369 ("drm/sched: Convert drm scheduler to use a work
> > queue rather than kthread")
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > ---
> >  drivers/gpu/drm/scheduler/sched_main.c | 5 +++--
> >  1 file changed, 3 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/scheduler/sched_main.c
> > b/drivers/gpu/drm/scheduler/sched_main.c
> > index 540231e6bac6..df0a5abb1400 100644
> > --- a/drivers/gpu/drm/scheduler/sched_main.c
> > +++ b/drivers/gpu/drm/scheduler/sched_main.c
> > @@ -1283,10 +1283,11 @@ int drm_sched_init(struct drm_gpu_scheduler
> > *sched,
> >  		sched->own_submit_wq = false;
> >  	} else {
> >  #ifdef CONFIG_LOCKDEP
> > -		sched->submit_wq =
> > alloc_ordered_workqueue_lockdep_map(name, 0,
> > +		sched->submit_wq =
> > alloc_ordered_workqueue_lockdep_map(name,
> > +								    
> >    WQ_MEM_RECLAIM,
> >  								    
> >    &drm_sched_lockdep_map);
> >  #else
> > -		sched->submit_wq = alloc_ordered_workqueue(name, 0);
> > +		sched->submit_wq = alloc_ordered_workqueue(name,
> > WQ_MEM_RECLAIM);
> >  #endif
> >  		if (!sched->submit_wq)
> >  			return -ENOMEM;
> 
> 
> Cool, thx – looks good from my POV.
> 

Can I get a RB?

> Since you now sent this patch as a single one, what would be the
> preferred merge plan for this? Your XE-Series doesn't depend on this
> IIUC, so should we take this patch here separately into drm-misc-next?
> 

Merge this one to drm-misc and we will backport into drm-xe-next.

Matt

> 
> Regards,
> P.
> 

  reply	other threads:[~2024-10-24 15:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 23:59 [PATCH v2] drm/sched: Mark scheduler work queues with WQ_MEM_RECLAIM Matthew Brost
2024-10-24 11:44 ` Nirmoy Das
2024-10-24 15:22   ` Matthew Brost
2024-10-24 15:35 ` Philipp Stanner
2024-10-24 15:47   ` Matthew Brost [this message]
2024-10-25 10:06     ` Philipp Stanner
2024-10-24 17:35 ` ✓ CI.Patch_applied: success for " Patchwork
2024-10-24 17:35 ` ✓ CI.checkpatch: " Patchwork
2024-10-24 17:36 ` ✓ CI.KUnit: " Patchwork
2024-10-24 17:48 ` ✓ CI.Build: " Patchwork
2024-10-24 17:50 ` ✓ CI.Hooks: " Patchwork
2024-10-24 17:51 ` ✓ CI.checksparse: " Patchwork
2024-10-24 18:19 ` ✓ CI.BAT: " Patchwork
2024-10-25 22:10 ` ✗ 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=ZxpsAogpxOjU+58p@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=ltuikov89@gmail.com \
    --cc=pstanner@redhat.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