From: Simona Vetter <simona.vetter@ffwll.ch>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [bug report] drm/xe/svm: Implement prefetch support for SVM ranges
Date: Wed, 4 Jun 2025 16:54:43 +0200 [thread overview]
Message-ID: <aEBeM1sWuSNWNij6@phenom.ffwll.local> (raw)
In-Reply-To: <20250603222952.GD407166@ziepe.ca>
On Tue, Jun 03, 2025 at 07:29:52PM -0300, Jason Gunthorpe wrote:
> On Mon, May 26, 2025 at 10:15:17PM +0530, Ghimiray, Himal Prasad wrote:
> >
> >
> > On 26-05-2025 20:36, Dan Carpenter wrote:
> > > Hello Himal Prasad Ghimiray,
> > >
> > > Commit 09ba0a8f06cd ("drm/xe/svm: Implement prefetch support for SVM
> > > ranges") from May 13, 2025 (linux-next), leads to the following
> > > Smatch static checker warning:
> > >
> > > drivers/gpu/drm/xe/xe_vm.c:2922 prefetch_ranges()
> > > warn: passing positive error code 's32min-(-96),(-94)-(-15),(-13)-(-12),(-10)-(-2),1' to 'ERR_PTR'
> >
> > Hi Dan,
> >
> > Thanks for pointing this out. I see there's a gap in how hmm_range_fault()
> > adheres to its documented behavior. I believe the function should sanitize
> > positive return values from walk_page_range() to ensure consistency.
> >
> > Jason can comment further on same.
>
> Yeah, I don't think it should return positive error code, whatever is
> doing that should be fixed. Can you send a patch?
Not sure that's what's going on, from the comment and reading the code
(albeit non-exhaustively) I think you can only get positive error return
values from walk_page_range if the ops you provide do so. The hmm ones
don't, so I think this should be ok without any code changes?
Maybe a WARN_ON and patching that up for paranoia, but I don't see how
this can happen.
Cheers, Sima
--
Simona Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2025-06-04 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 15:06 [bug report] drm/xe/svm: Implement prefetch support for SVM ranges Dan Carpenter
2025-05-26 16:45 ` Ghimiray, Himal Prasad
[not found] ` <20250603222952.GD407166@ziepe.ca>
2025-06-04 14:54 ` Simona Vetter [this message]
2025-06-04 17:29 ` Dan Carpenter
[not found] ` <20250604145657.GB17991@ziepe.ca>
2025-06-04 17:30 ` Dan Carpenter
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=aEBeM1sWuSNWNij6@phenom.ffwll.local \
--to=simona.vetter@ffwll.ch \
--cc=dan.carpenter@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=matthew.brost@intel.com \
--cc=thomas.hellstrom@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