From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Jason Ekstrand <jason@jlekstrand.net>, intel-gfx@lists.freedesktop.org
Cc: Dave Airlie <airlied@redhat.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gem: Drop relocation support on all new hardware (v4)
Date: Fri, 12 Mar 2021 09:50:14 +0000 [thread overview]
Message-ID: <39bfc60f-cc5a-d793-5cea-e1b8e0751d62@linux.intel.com> (raw)
In-Reply-To: <20210311181733.1048640-1-jason@jlekstrand.net>
On 11/03/2021 18:17, Jason Ekstrand wrote:
> The Vulkan driver in Mesa for Intel hardware never uses relocations if
> it's running on a version of i915 that supports at least softpin which
> all versions of i915 supporting Gen12 do. On the OpenGL side, Gen12+ is
> only supported by iris which never uses relocations. The older i965
> driver in Mesa does use relocations but it only supports Intel hardware
> through Gen11 and has been deprecated for all hardware Gen9+. The
> compute driver also never uses relocations. This only leaves the media
> driver which is supposed to be switching to softpin going forward.
> Making softpin a requirement for all future hardware seems reasonable.
>
> There is one piece of hardware enabled by default in i915: RKL which was
> enabled by e22fa6f0a976 which has not yet landed in drm-next so this
> almost but not really a userspace API change for RKL. If it becomes a
> problem, we can always add !IS_ROCKETLAKE(eb->i915) to the condition.
>
> Rejecting relocations starting with newer Gen12 platforms has the
> benefit that we don't have to bother supporting it on platforms with
> local memory. Given how much CPU touching of memory is required for
> relocations, not having to do so on platforms where not all memory is
> directly CPU-accessible carries significant advantages.
>
> v2 (Jason Ekstrand):
> - Allow TGL-LP platforms as they've already shipped
>
> v3 (Jason Ekstrand):
> - WARN_ON platforms with LMEM support in case the check is wrong
>
> v4 (Jason Ekstrand):
> - Call out Rocket Lake in the commit message
>
> Signed-off-by: Jason Ekstrand <jason@jlekstrand.net>
> Acked-by: Keith Packard <keithp@keithp.com>
> Cc: Dave Airlie <airlied@redhat.com>
> Cc: Daniel Vetter <daniel.vetter@intel.com>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> index 99772f37bff60..b02dbd16bfa03 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c
> @@ -1764,7 +1764,8 @@ eb_relocate_vma_slow(struct i915_execbuffer *eb, struct eb_vma *ev)
> return err;
> }
>
> -static int check_relocations(const struct drm_i915_gem_exec_object2 *entry)
> +static int check_relocations(const struct i915_execbuffer *eb,
> + const struct drm_i915_gem_exec_object2 *entry)
> {
> const char __user *addr, *end;
> unsigned long size;
> @@ -1774,6 +1775,14 @@ static int check_relocations(const struct drm_i915_gem_exec_object2 *entry)
> if (size == 0)
> return 0;
>
> + /* Relocations are disallowed for all platforms after TGL-LP */
> + if (INTEL_GEN(eb->i915) >= 12 && !IS_TIGERLAKE(eb->i915))
> + return -EINVAL;
I still recommend ENODEV as more inline with our established error
codes. (Platform does not support vs dear userspace you messed up your
flags, modes, whatever.)
> +
> + /* All discrete memory platforms are Gen12 or above */
> + if (WARN_ON(HAS_LMEM(eb->i915)))
> + return -EINVAL;
What was the conclusion on value of supporting fake lmem?
Regards,
Tvrtko
> +
> if (size > N_RELOC(ULONG_MAX))
> return -EINVAL;
>
> @@ -1807,7 +1816,7 @@ static int eb_copy_relocations(const struct i915_execbuffer *eb)
> if (nreloc == 0)
> continue;
>
> - err = check_relocations(&eb->exec[i]);
> + err = check_relocations(eb, &eb->exec[i]);
> if (err)
> goto err;
>
> @@ -1880,7 +1889,7 @@ static int eb_prefault_relocations(const struct i915_execbuffer *eb)
> for (i = 0; i < count; i++) {
> int err;
>
> - err = check_relocations(&eb->exec[i]);
> + err = check_relocations(eb, &eb->exec[i]);
> if (err)
> return err;
> }
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-03-12 9:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200507153600.314454-1-jason@jlekstrand.net>
2021-03-10 21:26 ` [Intel-gfx] [PATCH] i915: Drop relocation support on all new hardware Jason Ekstrand
2021-03-10 21:50 ` [Intel-gfx] [PATCH] i915: Drop relocation support on all new hardware (v3) Jason Ekstrand
2021-03-10 22:56 ` Jason Ekstrand
2021-03-11 8:14 ` Lucas De Marchi
2021-03-11 10:20 ` Matthew Auld
2021-03-11 9:54 ` Tvrtko Ursulin
2021-03-11 11:44 ` Zbigniew Kempczyński
2021-03-11 15:50 ` Jason Ekstrand
2021-03-11 15:57 ` Daniel Vetter
2021-03-11 16:24 ` Jason Ekstrand
2021-03-11 16:50 ` Zbigniew Kempczyński
2021-03-11 17:18 ` Jason Ekstrand
2021-03-11 18:19 ` Zbigniew Kempczyński
2021-03-11 18:57 ` Jason Ekstrand
2021-03-12 14:16 ` Daniel Vetter
2021-03-11 16:31 ` Chris Wilson
2021-03-11 16:40 ` Jason Ekstrand
2021-03-11 18:17 ` [Intel-gfx] [PATCH] drm/i915/gem: Drop relocation support on all new hardware (v4) Jason Ekstrand
2021-03-12 9:28 ` Zbigniew Kempczyński
2021-03-12 9:50 ` Tvrtko Ursulin [this message]
2021-03-12 10:56 ` Matthew Auld
2021-03-12 11:33 ` Maarten Lankhorst
2021-03-12 11:52 ` Tvrtko Ursulin
2021-03-12 11:47 ` Tvrtko Ursulin
2021-03-12 12:16 ` Matthew Auld
2021-03-12 14:52 ` Jason Ekstrand
2021-03-12 15:20 ` Tvrtko Ursulin
2021-03-10 21:42 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for RFC: i915: Drop relocation support on Gen12+ (rev2) Patchwork
2021-03-10 22:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-03-10 23:47 ` [Intel-gfx] ✓ Fi.CI.BAT: success for RFC: i915: Drop relocation support on Gen12+ (rev3) Patchwork
2021-03-11 2:32 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-03-11 18:41 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for RFC: i915: Drop relocation support on Gen12+ (rev4) Patchwork
2021-03-11 19:10 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=39bfc60f-cc5a-d793-5cea-e1b8e0751d62@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jason@jlekstrand.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox