From: Matthew Brost <matthew.brost@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Fix fault on fd close when wedged
Date: Thu, 12 Dec 2024 08:30:03 -0800 [thread overview]
Message-ID: <Z1sPi9G00q6advpY@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <ffgubo3r4kue5fmlbb6grii3t3rfafnpk5av4ieht7em7du7xw@svwhtkn3exfq>
On Wed, Dec 11, 2024 at 10:26:15PM -0600, Lucas De Marchi wrote:
> On Wed, Dec 11, 2024 at 07:51:57PM -0800, Matthew Brost wrote:
> > On Wed, Dec 11, 2024 at 02:53:32PM -0800, Lucas De Marchi wrote:
> > > If device is wedged, the final run ticks update for the client should be
> > > skipped as it's already unmapped. Fix this pagefault when forcing a
> >
> > Where does exec queue get unmapped on wedging a device?
>
> it's the lrc we are trying to read: lrc->bo, with offset == timestamp.
>
> I thought it was part of the the xe_gt_declare_wedged(), but I'm not
> following what triggers it - the only thing that should trigger that
> would be the xe_lrc_put() and the refcount reaching 0. Something is not
> adding up here, I will have to trace the destroy to see what's going on.
>
Quick reached the same conclusion - accessing the LRC BO should be safe
until the final put, hence my question. It does appear something else
weird is going on here.
Matt
> Lucas De Marchi
next prev parent reply other threads:[~2024-12-12 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 22:53 [PATCH] drm/xe: Fix fault on fd close when wedged Lucas De Marchi
2024-12-11 23:12 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-11 23:12 ` ✓ CI.checkpatch: " Patchwork
2024-12-11 23:13 ` ✓ CI.KUnit: " Patchwork
2024-12-11 23:31 ` ✓ CI.Build: " Patchwork
2024-12-11 23:34 ` ✓ CI.Hooks: " Patchwork
2024-12-11 23:35 ` ✓ CI.checksparse: " Patchwork
2024-12-12 3:51 ` [PATCH] " Matthew Brost
2024-12-12 4:26 ` Lucas De Marchi
2024-12-12 16:30 ` Matthew Brost [this message]
2024-12-17 22:20 ` Lucas De Marchi
2024-12-12 4:43 ` ✗ Xe.CI.Full: failure for " Patchwork
2024-12-12 6:38 ` ✓ CI.BAT: success " 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=Z1sPi9G00q6advpY@lstrano-desk.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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