From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org, "Matthew Auld" <matthew.auld@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: [PATCH 3/4] drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1
Date: Tue, 1 Apr 2025 19:37:51 +0300 [thread overview]
Message-ID: <20250401163752.6412-4-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20250401163752.6412-1-ville.syrjala@linux.intel.com>
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>
Fixes: 71b1669ea9bd ("drm/i915/uapi: tweak error capture on recoverable contexts")
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))
return -EINVAL;
for_each_batch_create_order(eb, j) {
--
2.45.3
next prev parent reply other threads:[~2025-04-01 16:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 16:37 [PATCH 0/4] drm/i915: DG1 fixes Ville Syrjala
2025-04-01 16:37 ` [PATCH 1/4] drm/i915: Apply the combo PLL frac w/a on DG1 Ville Syrjala
2025-04-02 16:34 ` Imre Deak
2025-04-01 16:37 ` [PATCH 2/4] drm/i915: Simplify combo PLL frac w/a Ville Syrjala
2025-04-02 17:17 ` [PATCH v2 " Ville Syrjala
2025-04-03 13:50 ` Imre Deak
2025-04-01 16:37 ` Ville Syrjala [this message]
2025-04-01 17:34 ` [PATCH 3/4] drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1 Andi Shyti
2025-04-01 17:50 ` Ville Syrjälä
2025-04-01 23:13 ` Andi Shyti
2025-04-01 16:37 ` [PATCH 4/4] drm/i915/pci: Remove force_probe requirement for DG1 Ville Syrjala
2025-04-01 17:34 ` Andi Shyti
2025-04-01 18:13 ` ✗ Fi.CI.SPARSE: warning for drm/i915: DG1 fixes Patchwork
2025-04-01 18:31 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-01 21:50 ` ✗ i915.CI.Full: failure " Patchwork
2025-04-02 17:54 ` ✗ Fi.CI.SPARSE: warning for drm/i915: DG1 fixes (rev2) Patchwork
2025-04-02 18:38 ` ✓ i915.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=20250401163752.6412-4-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=stable@vger.kernel.org \
--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