From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Kenneth Graunke <kenneth@whitecape.org>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [Intel-gfx] [PATCH v3 09/13] drm/i915/selftests: skip the mman tests for stolen
Date: Wed, 29 Jun 2022 18:22:46 +0200 [thread overview]
Message-ID: <fe1fa1cc-3e2f-39b0-ea73-b9123a8b76bd@linux.intel.com> (raw)
In-Reply-To: <20220629121427.353800-10-matthew.auld@intel.com>
On 6/29/22 14:14, Matthew Auld wrote:
> It's not supported, and just skips later anyway. With small-BAR things
> get more complicated since all of stolen is likely not even CPU
> accessible, hence not passing I915_BO_ALLOC_GPU_ONLY just results in the
> object create failing.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Cc: Jon Bloomfield <jon.bloomfield@intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Kenneth Graunke <kenneth@whitecape.org>
> Cc: Akeem G Abodunrin <akeem.g.abodunrin@intel.com>
> ---
> drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
This reminds me,
Is there a problem for fbdev (and hence things like plymouth) if the
initial fbdev image ends up as a stolen memory object which in turn ends
up not being mappable? I remember we discussed this before but can't
recall what the answer was.
Anyway, for this patch
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>
> diff --git a/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c b/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> index 5bc93a1ce3e3..388c85b0f764 100644
> --- a/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> +++ b/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> @@ -979,6 +979,9 @@ static int igt_mmap(void *arg)
> };
> int i;
>
> + if (mr->private)
> + continue;
> +
> for (i = 0; i < ARRAY_SIZE(sizes); i++) {
> struct drm_i915_gem_object *obj;
> int err;
> @@ -1435,6 +1438,9 @@ static int igt_mmap_access(void *arg)
> struct drm_i915_gem_object *obj;
> int err;
>
> + if (mr->private)
> + continue;
> +
> obj = __i915_gem_object_create_user(i915, PAGE_SIZE, &mr, 1);
> if (obj == ERR_PTR(-ENODEV))
> continue;
> @@ -1580,6 +1586,9 @@ static int igt_mmap_gpu(void *arg)
> struct drm_i915_gem_object *obj;
> int err;
>
> + if (mr->private)
> + continue;
> +
> obj = __i915_gem_object_create_user(i915, PAGE_SIZE, &mr, 1);
> if (obj == ERR_PTR(-ENODEV))
> continue;
> @@ -1727,6 +1736,9 @@ static int igt_mmap_revoke(void *arg)
> struct drm_i915_gem_object *obj;
> int err;
>
> + if (mr->private)
> + continue;
> +
> obj = __i915_gem_object_create_user(i915, PAGE_SIZE, &mr, 1);
> if (obj == ERR_PTR(-ENODEV))
> continue;
WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
Kenneth Graunke <kenneth@whitecape.org>,
Jon Bloomfield <jon.bloomfield@intel.com>,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Akeem G Abodunrin <akeem.g.abodunrin@intel.com>
Subject: Re: [PATCH v3 09/13] drm/i915/selftests: skip the mman tests for stolen
Date: Wed, 29 Jun 2022 18:22:46 +0200 [thread overview]
Message-ID: <fe1fa1cc-3e2f-39b0-ea73-b9123a8b76bd@linux.intel.com> (raw)
In-Reply-To: <20220629121427.353800-10-matthew.auld@intel.com>
On 6/29/22 14:14, Matthew Auld wrote:
> It's not supported, and just skips later anyway. With small-BAR things
> get more complicated since all of stolen is likely not even CPU
> accessible, hence not passing I915_BO_ALLOC_GPU_ONLY just results in the
> object create failing.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Cc: Jon Bloomfield <jon.bloomfield@intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Kenneth Graunke <kenneth@whitecape.org>
> Cc: Akeem G Abodunrin <akeem.g.abodunrin@intel.com>
> ---
> drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
This reminds me,
Is there a problem for fbdev (and hence things like plymouth) if the
initial fbdev image ends up as a stolen memory object which in turn ends
up not being mappable? I remember we discussed this before but can't
recall what the answer was.
Anyway, for this patch
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>
> diff --git a/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c b/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> index 5bc93a1ce3e3..388c85b0f764 100644
> --- a/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> +++ b/drivers/gpu/drm/i915/gem/selftests/i915_gem_mman.c
> @@ -979,6 +979,9 @@ static int igt_mmap(void *arg)
> };
> int i;
>
> + if (mr->private)
> + continue;
> +
> for (i = 0; i < ARRAY_SIZE(sizes); i++) {
> struct drm_i915_gem_object *obj;
> int err;
> @@ -1435,6 +1438,9 @@ static int igt_mmap_access(void *arg)
> struct drm_i915_gem_object *obj;
> int err;
>
> + if (mr->private)
> + continue;
> +
> obj = __i915_gem_object_create_user(i915, PAGE_SIZE, &mr, 1);
> if (obj == ERR_PTR(-ENODEV))
> continue;
> @@ -1580,6 +1586,9 @@ static int igt_mmap_gpu(void *arg)
> struct drm_i915_gem_object *obj;
> int err;
>
> + if (mr->private)
> + continue;
> +
> obj = __i915_gem_object_create_user(i915, PAGE_SIZE, &mr, 1);
> if (obj == ERR_PTR(-ENODEV))
> continue;
> @@ -1727,6 +1736,9 @@ static int igt_mmap_revoke(void *arg)
> struct drm_i915_gem_object *obj;
> int err;
>
> + if (mr->private)
> + continue;
> +
> obj = __i915_gem_object_create_user(i915, PAGE_SIZE, &mr, 1);
> if (obj == ERR_PTR(-ENODEV))
> continue;
next prev parent reply other threads:[~2022-06-29 16:22 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 12:14 [Intel-gfx] [PATCH v3 00/13] small BAR uapi bits Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 01/13] drm/doc: add rfc section for small BAR uapi Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 02/13] drm/i915/uapi: add probed_cpu_visible_size Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 03/13] drm/i915/uapi: expose the avail tracking Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 04/13] drm/i915: remove intel_memory_region avail Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 05/13] drm/i915/uapi: apply ALLOC_GPU_ONLY by default Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 06/13] drm/i915/uapi: add NEEDS_CPU_ACCESS hint Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 07/13] drm/i915/error: skip non-mappable pages Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 08/13] drm/i915/uapi: tweak error capture on recoverable contexts Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 09/13] drm/i915/selftests: skip the mman tests for stolen Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 16:22 ` Thomas Hellström [this message]
2022-06-29 16:22 ` Thomas Hellström
2022-06-29 16:42 ` [Intel-gfx] " Matthew Auld
2022-06-29 16:42 ` Matthew Auld
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 10/13] drm/i915/selftests: ensure we reserve a fence slot Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 11/13] drm/i915/ttm: handle blitter failure on DG2 Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 16:11 ` [Intel-gfx] " Thomas Hellström
2022-06-29 16:11 ` Thomas Hellström
2022-06-29 16:28 ` [Intel-gfx] " Matthew Auld
2022-06-29 16:28 ` Matthew Auld
2022-06-29 16:47 ` [Intel-gfx] " Thomas Hellström
2022-06-29 16:47 ` Thomas Hellström
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 12/13] drm/i915/ttm: disallow CPU fallback mode for ccs pages Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 12:43 ` [Intel-gfx] " Ramalingam C
2022-06-29 12:43 ` Ramalingam C
2022-06-29 12:14 ` [Intel-gfx] [PATCH v3 13/13] drm/i915: turn on small BAR support Matthew Auld
2022-06-29 12:14 ` Matthew Auld
2022-06-29 16:16 ` [Intel-gfx] " Thomas Hellström
2022-06-29 16:16 ` Thomas Hellström
2022-06-29 13:00 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for small BAR uapi bits (rev4) Patchwork
2022-06-29 13:00 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-06-29 13:22 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-06-29 14:40 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for small BAR uapi bits (rev5) Patchwork
2022-06-29 14:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-06-29 15:05 ` [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=fe1fa1cc-3e2f-39b0-ea73-b9123a8b76bd@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kenneth@whitecape.org \
--cc=matthew.auld@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 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.