From: Andi Shyti <andi.shyti@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: "Ville Syrjala" <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org, stable@vger.kernel.org,
"Matthew Auld" <matthew.auld@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Subject: Re: [PATCH 3/4] drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1
Date: Wed, 2 Apr 2025 01:13:48 +0200 [thread overview]
Message-ID: <Z-xzLIqdjhU3RVOA@ashyti-mobl2.lan> (raw)
In-Reply-To: <Z-wjk-9ZVEpBVw0G@ashyti-mobl2.lan>
Hi Ville,
> > 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))
>
> How is this is more relaxed than the old version?
nevermind...
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Thanks,
Andi
next prev parent reply other threads:[~2025-04-01 23:14 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 ` [PATCH 3/4] drm/i915/gem: Allow EXEC_CAPTURE on recoverable contexts on DG1 Ville Syrjala
2025-04-01 17:34 ` Andi Shyti
2025-04-01 17:50 ` Ville Syrjälä
2025-04-01 23:13 ` Andi Shyti [this message]
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=Z-xzLIqdjhU3RVOA@ashyti-mobl2.lan \
--to=andi.shyti@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 \
--cc=ville.syrjala@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;
as well as URLs for NNTP newsgroup(s).