From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
stable@vger.kernel.org, "Matthew Auld" <matthew.auld@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Andi Shyti" <andi.shyti@linux.intel.com>
Subject: Re: [PATCH v2 1/2] drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1
Date: Thu, 22 May 2025 12:35:05 +0300 [thread overview]
Message-ID: <aC7vyURBb6k8TqBI@intel.com> (raw)
In-Reply-To: <174789510455.12498.1410930072009074388@jlahtine-mobl>
On Thu, May 22, 2025 at 09:25:04AM +0300, Joonas Lahtinen wrote:
> (+ Tvrkto)
>
> Quoting Ville Syrjala (2025-04-11 17:43:12)
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > The intel-media-driver is currently broken on DG1 because
> > it uses EXEC_CAPTURE with recovarable contexts. Relax the
> > check to allow that.
> >
> > I've also submitted a fix for the intel-media-driver:
> > https://github.com/intel/media-driver/pull/1920
> >
> > Cc: stable@vger.kernel.org
> > Cc: Matthew Auld <matthew.auld@intel.com>
> > Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > Testcase: igt/gem_exec_capture/capture-invisible
> > Fixes: 71b1669ea9bd ("drm/i915/uapi: tweak error capture on recoverable contexts")
> > Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> > index ca7e9216934a..ea9d5063ce78 100644
> > --- a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> > +++ b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> > @@ -2013,7 +2013,7 @@ static int eb_capture_stage(struct i915_execbuffer *eb)
> > continue;
> >
> > if (i915_gem_context_is_recoverable(eb->gem_context) &&
> > - (IS_DGFX(eb->i915) || GRAPHICS_VER_FULL(eb->i915) > IP_VER(12, 0)))
> > + GRAPHICS_VER_FULL(eb->i915) > IP_VER(12, 10))
>
> The IS_DGFX check was there because the error capture is expected to be
> broken on anything with VRAM.
I don't care. It's a regression that prevents current userspace
from working.
>
> If we have already submitted an userspace fix to remove that flag, that
> would be the right way to go.
There has a been an open pull request for that for who knows how long
without any action.
>
> So reverting this for now.
*You* make sure a userspace fix actually gets released then.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-05-22 9:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 14:43 [PATCH v2 0/2] drm/i915: DG1 fixes Ville Syrjala
2025-04-11 14:43 ` [PATCH v2 1/2] drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1 Ville Syrjala
2025-05-22 6:25 ` Joonas Lahtinen
2025-05-22 6:35 ` Andi Shyti
2025-05-22 9:35 ` Ville Syrjälä [this message]
2025-05-22 10:58 ` Joonas Lahtinen
2025-04-11 14:43 ` [PATCH v2 2/2] drm/i915/pci: Remove force_probe requirement for DG1 Ville Syrjala
2025-04-11 15:22 ` ✗ Fi.CI.SPARSE: warning for drm/i915: DG1 fixes (rev3) Patchwork
2025-04-11 15:46 ` ✗ i915.CI.BAT: failure " Patchwork
2025-04-11 19:34 ` ✗ Fi.CI.SPARSE: warning for drm/i915: DG1 fixes (rev4) Patchwork
2025-04-12 3:48 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-12 6:09 ` ✗ i915.CI.Full: failure " Patchwork
2025-05-07 21:06 ` ✗ Fi.CI.SPARSE: warning for drm/i915: DG1 fixes (rev5) Patchwork
2025-05-12 15:57 ` ✗ Fi.CI.SPARSE: warning for drm/i915: DG1 fixes (rev6) Patchwork
2025-05-17 23:09 ` [PATCH v2 0/2] drm/i915: DG1 fixes Andi Shyti
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=aC7vyURBb6k8TqBI@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=stable@vger.kernel.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.