Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francois Dugast <francois.dugast@intel.com>
To: Nirmoy Das <nirmoy.das@linux.intel.com>
Cc: Nirmoy Das <nirmoy.das@intel.com>,
	<intel-xe@lists.freedesktop.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Matthew Auld <matthew.auld@intel.com>,
	Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH v2 2/2] drm/xe/ufence: Warn if mmget_not_zero() fails
Date: Fri, 18 Oct 2024 15:53:49 +0200	[thread overview]
Message-ID: <ZxJobXkrqE5Ibns2@fdugast-desk> (raw)
In-Reply-To: <8f873b94-ac9a-430c-901b-30bc47a6ccd2@linux.intel.com>

On Fri, Oct 18, 2024 at 03:41:16PM +0200, Nirmoy Das wrote:
> Hi Francois,
> 
> On 10/16/2024 10:23 AM, Nirmoy Das wrote:
> > This shouldn't happen but seen this while debugging ufence timeout
> > issue time to time so log it to isolate this particular case.
> >
> > v2: s/XE_WARN_ON/drm_dbg(Maarten)
> >
> > Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/1630
> > Cc: Francois Dugast <francois.dugast@intel.com>
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Cc: Matthew Auld <matthew.auld@intel.com>
> > Cc: Matthew Brost <matthew.brost@intel.com>
> > Reviewed-by: Francois Dugast <francois.dugast@intel.com> #v1
> 
> 
> is your r-b valid for v2 as well ?

Yes it is.

Reviewed-by: Francois Dugast <francois.dugast@intel.com>

> 
> 
> Regards,
> 
> Nirmoy
> 
> > Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> > ---
> >  drivers/gpu/drm/xe/xe_sync.c | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_sync.c b/drivers/gpu/drm/xe/xe_sync.c
> > index 2e72c06fd40d..a90480c6aecf 100644
> > --- a/drivers/gpu/drm/xe/xe_sync.c
> > +++ b/drivers/gpu/drm/xe/xe_sync.c
> > @@ -83,6 +83,8 @@ static void user_fence_worker(struct work_struct *w)
> >  			XE_WARN_ON("Copy to user failed");
> >  		kthread_unuse_mm(ufence->mm);
> >  		mmput(ufence->mm);
> > +	} else {
> > +		drm_dbg(&ufence->xe->drm, "mmget_not_zero() failed, ufence wasn't signaled\n");
> >  	}
> >  
> >  	wake_up_all(&ufence->xe->ufence_wq);

  reply	other threads:[~2024-10-18 13:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16  8:23 [PATCH v2 0/2] Improve ufence addr validation and error handling Nirmoy Das
2024-10-16  8:23 ` [PATCH v2 1/2] drm/xe/ufence: Prefetch ufence addr to catch bogus address Nirmoy Das
2024-10-18  2:51   ` Matthew Brost
2024-10-16  8:23 ` [PATCH v2 2/2] drm/xe/ufence: Warn if mmget_not_zero() fails Nirmoy Das
2024-10-18 13:41   ` Nirmoy Das
2024-10-18 13:53     ` Francois Dugast [this message]
2024-10-18 13:54       ` Nirmoy Das
2024-10-16 12:04 ` ✓ CI.Patch_applied: success for Improve ufence addr validation and error handling (rev3) Patchwork
2024-10-16 12:04 ` ✓ CI.checkpatch: " Patchwork
2024-10-16 12:05 ` ✓ CI.KUnit: " Patchwork
2024-10-16 12:17 ` ✓ CI.Build: " Patchwork
2024-10-16 12:19 ` ✓ CI.Hooks: " Patchwork
2024-10-16 12:21 ` ✓ CI.checksparse: " Patchwork
2024-10-16 12:38 ` ✓ CI.BAT: " Patchwork
2024-10-17  2:54 ` ✗ CI.FULL: failure " Patchwork
2024-10-18 15:40   ` Nirmoy Das

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=ZxJobXkrqE5Ibns2@fdugast-desk \
    --to=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=nirmoy.das@intel.com \
    --cc=nirmoy.das@linux.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