From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 06/19] drm/i915/stolen: pass the allocation flags
Date: Wed, 14 Apr 2021 16:09:44 +0100 [thread overview]
Message-ID: <4dc60bcc-ffb8-db6a-dc0d-4a3700661258@linux.intel.com> (raw)
In-Reply-To: <20210412090526.30547-7-matthew.auld@intel.com>
On 12/04/2021 10:05, Matthew Auld wrote:
> From: CQ Tang <cq.tang@intel.com>
>
> Stolen memory is always allocated as physically contiguous pages, mark
> the object flags as such.
>
> Signed-off-by: CQ Tang <cq.tang@intel.com>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_stolen.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_stolen.c b/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> index f713eabb7671..49a2dfcc8ba7 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> @@ -633,14 +633,15 @@ static const struct drm_i915_gem_object_ops i915_gem_object_stolen_ops = {
>
> static int __i915_gem_object_create_stolen(struct intel_memory_region *mem,
> struct drm_i915_gem_object *obj,
> - struct drm_mm_node *stolen)
> + struct drm_mm_node *stolen,
> + unsigned int flags)
> {
> static struct lock_class_key lock_class;
> unsigned int cache_level;
> int err;
>
> drm_gem_private_object_init(&mem->i915->drm, &obj->base, stolen->size);
> - i915_gem_object_init(obj, &i915_gem_object_stolen_ops, &lock_class, 0);
> + i915_gem_object_init(obj, &i915_gem_object_stolen_ops, &lock_class, flags);
>
> obj->stolen = stolen;
> obj->read_domains = I915_GEM_DOMAIN_CPU | I915_GEM_DOMAIN_GTT;
> @@ -682,7 +683,7 @@ static int _i915_gem_object_stolen_init(struct intel_memory_region *mem,
> if (ret)
> goto err_free;
>
> - ret = __i915_gem_object_create_stolen(mem, obj, stolen);
> + ret = __i915_gem_object_create_stolen(mem, obj, stolen, flags);
> if (ret)
> goto err_remove;
>
> @@ -840,7 +841,8 @@ i915_gem_object_create_stolen_for_preallocated(struct drm_i915_private *i915,
> goto err_stolen;
> }
>
> - ret = __i915_gem_object_create_stolen(mem, obj, stolen);
> + ret = __i915_gem_object_create_stolen(mem, obj, stolen,
> + I915_BO_ALLOC_CONTIGUOUS);
> if (ret)
> goto err_object_free;
>
>
Are all stolen objects always contiguous or only ones allocated by
i915_gem_object_create_stolen_for_preallocated? If former should
__i915_gem_object_create_stolen just set the flag without the need to
pass it in?
Regards,
Tvrtko
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 06/19] drm/i915/stolen: pass the allocation flags
Date: Wed, 14 Apr 2021 16:09:44 +0100 [thread overview]
Message-ID: <4dc60bcc-ffb8-db6a-dc0d-4a3700661258@linux.intel.com> (raw)
In-Reply-To: <20210412090526.30547-7-matthew.auld@intel.com>
On 12/04/2021 10:05, Matthew Auld wrote:
> From: CQ Tang <cq.tang@intel.com>
>
> Stolen memory is always allocated as physically contiguous pages, mark
> the object flags as such.
>
> Signed-off-by: CQ Tang <cq.tang@intel.com>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_stolen.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_stolen.c b/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> index f713eabb7671..49a2dfcc8ba7 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_stolen.c
> @@ -633,14 +633,15 @@ static const struct drm_i915_gem_object_ops i915_gem_object_stolen_ops = {
>
> static int __i915_gem_object_create_stolen(struct intel_memory_region *mem,
> struct drm_i915_gem_object *obj,
> - struct drm_mm_node *stolen)
> + struct drm_mm_node *stolen,
> + unsigned int flags)
> {
> static struct lock_class_key lock_class;
> unsigned int cache_level;
> int err;
>
> drm_gem_private_object_init(&mem->i915->drm, &obj->base, stolen->size);
> - i915_gem_object_init(obj, &i915_gem_object_stolen_ops, &lock_class, 0);
> + i915_gem_object_init(obj, &i915_gem_object_stolen_ops, &lock_class, flags);
>
> obj->stolen = stolen;
> obj->read_domains = I915_GEM_DOMAIN_CPU | I915_GEM_DOMAIN_GTT;
> @@ -682,7 +683,7 @@ static int _i915_gem_object_stolen_init(struct intel_memory_region *mem,
> if (ret)
> goto err_free;
>
> - ret = __i915_gem_object_create_stolen(mem, obj, stolen);
> + ret = __i915_gem_object_create_stolen(mem, obj, stolen, flags);
> if (ret)
> goto err_remove;
>
> @@ -840,7 +841,8 @@ i915_gem_object_create_stolen_for_preallocated(struct drm_i915_private *i915,
> goto err_stolen;
> }
>
> - ret = __i915_gem_object_create_stolen(mem, obj, stolen);
> + ret = __i915_gem_object_create_stolen(mem, obj, stolen,
> + I915_BO_ALLOC_CONTIGUOUS);
> if (ret)
> goto err_object_free;
>
>
Are all stolen objects always contiguous or only ones allocated by
i915_gem_object_create_stolen_for_preallocated? If former should
__i915_gem_object_create_stolen just set the flag without the need to
pass it in?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-04-14 15:10 UTC|newest]
Thread overview: 132+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 9:05 [PATCH 00/19] More DG1 enabling Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-12 9:05 ` [PATCH 01/19] drm/i915/gt: Skip aperture remapping selftest where there is no aperture Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-12 14:48 ` Daniel Vetter
2021-04-12 14:48 ` Daniel Vetter
2021-04-12 9:05 ` [PATCH 02/19] drm/i915/selftests: Only query RAPL for integrated power measurements Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-12 9:05 ` [PATCH 03/19] drm/i915: Create stolen memory region from local memory Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-14 15:01 ` Tvrtko Ursulin
2021-04-14 15:01 ` Tvrtko Ursulin
2021-04-16 15:04 ` Matthew Auld
2021-04-16 15:04 ` Matthew Auld
2021-04-19 14:15 ` Tvrtko Ursulin
2021-04-19 14:15 ` Tvrtko Ursulin
2021-04-12 9:05 ` [PATCH 04/19] drm/i915/stolen: treat stolen local as normal " Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-14 15:06 ` Tvrtko Ursulin
2021-04-14 15:06 ` Tvrtko Ursulin
2021-04-12 9:05 ` [PATCH 05/19] drm/i915/stolen: enforce the min_page_size contract Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-14 15:07 ` Tvrtko Ursulin
2021-04-14 15:07 ` Tvrtko Ursulin
2021-04-12 9:05 ` [PATCH 06/19] drm/i915/stolen: pass the allocation flags Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-14 15:09 ` Tvrtko Ursulin [this message]
2021-04-14 15:09 ` Tvrtko Ursulin
2021-04-16 13:53 ` Matthew Auld
2021-04-16 13:53 ` Matthew Auld
2021-04-12 9:05 ` [PATCH 07/19] drm/i915/fbdev: Use lmem physical addresses for fb_mmap() on discrete Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-12 15:00 ` Daniel Vetter
2021-04-12 15:00 ` [Intel-gfx] " Daniel Vetter
2021-04-12 9:05 ` [PATCH 08/19] drm/i915: Return error value when bo not in LMEM for discrete Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-14 15:16 ` Tvrtko Ursulin
2021-04-14 15:16 ` Tvrtko Ursulin
2021-04-12 9:05 ` [PATCH 09/19] drm/i915/lmem: Fail driver init if LMEM training failed Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-12 9:05 ` [PATCH 10/19] drm/i915/dg1: Fix mapping type for default state object Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-12 9:05 ` [PATCH 11/19] drm/i915: Update the helper to set correct mapping Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-14 15:22 ` Tvrtko Ursulin
2021-04-14 15:22 ` Tvrtko Ursulin
2021-04-14 16:20 ` Matthew Auld
2021-04-14 16:20 ` Matthew Auld
2021-04-15 8:20 ` Tvrtko Ursulin
2021-04-15 8:20 ` Tvrtko Ursulin
2021-04-15 9:23 ` Matthew Auld
2021-04-15 9:23 ` Matthew Auld
2021-04-15 11:05 ` Tvrtko Ursulin
2021-04-15 11:05 ` Tvrtko Ursulin
2021-04-19 11:30 ` Matthew Auld
2021-04-19 11:30 ` Matthew Auld
2021-04-19 14:07 ` Tvrtko Ursulin
2021-04-19 14:07 ` Tvrtko Ursulin
2021-04-19 14:37 ` Matthew Auld
2021-04-19 14:37 ` Matthew Auld
2021-04-19 15:01 ` Tvrtko Ursulin
2021-04-19 15:01 ` Tvrtko Ursulin
2021-04-21 11:42 ` Matthew Auld
2021-04-21 11:42 ` Matthew Auld
2021-04-21 15:41 ` Tvrtko Ursulin
2021-04-21 15:41 ` Tvrtko Ursulin
2021-04-21 19:13 ` Matthew Auld
2021-04-21 19:13 ` Matthew Auld
2021-04-26 8:57 ` Matthew Auld
2021-04-26 8:57 ` Matthew Auld
2021-04-26 9:21 ` Tvrtko Ursulin
2021-04-26 9:21 ` Tvrtko Ursulin
2021-04-12 9:05 ` [PATCH 12/19] drm/i915/lmem: Bypass aperture when lmem is available Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-14 15:33 ` Tvrtko Ursulin
2021-04-14 15:33 ` Tvrtko Ursulin
2021-04-16 14:25 ` Matthew Auld
2021-04-16 14:25 ` Matthew Auld
2021-04-19 14:16 ` Tvrtko Ursulin
2021-04-19 14:16 ` Tvrtko Ursulin
2021-04-12 9:05 ` [PATCH 13/19] drm/i915/dg1: Read OPROM via SPI controller Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-09-17 23:29 ` Lucas De Marchi
2021-04-12 9:05 ` [PATCH 14/19] drm/i915/oprom: Basic sanitization Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-12 22:36 ` kernel test robot
2021-04-12 22:36 ` kernel test robot
2021-04-12 22:36 ` kernel test robot
2021-04-12 22:36 ` [PATCH] drm/i915/oprom: fix memdup.cocci warnings kernel test robot
2021-04-12 22:36 ` kernel test robot
2021-04-12 22:36 ` [Intel-gfx] " kernel test robot
2021-05-17 11:57 ` [Intel-gfx] [PATCH 14/19] drm/i915/oprom: Basic sanitization Jani Nikula
2021-05-17 11:57 ` Jani Nikula
2021-09-18 4:30 ` Lucas De Marchi
2021-09-20 7:41 ` Jani Nikula
2021-09-20 8:04 ` Gupta, Anshuman
2021-09-20 8:04 ` Gupta, Anshuman
2021-09-20 8:43 ` Jani Nikula
2021-09-20 8:43 ` Jani Nikula
2021-09-22 21:53 ` Lucas De Marchi
2021-04-12 9:05 ` [PATCH 15/19] drm/i915: WA for zero memory channel Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-12 16:57 ` Souza, Jose
2021-04-12 16:57 ` [Intel-gfx] " Souza, Jose
2021-04-12 9:05 ` [PATCH 16/19] drm/i915/dg1: Compute MEM Bandwidth using MCHBAR Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-12 9:05 ` [PATCH 17/19] drm/i915/dg1: Double memory bandwidth available Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-12 9:05 ` [PATCH 18/19] drm/i915/gtt: map the PD up front Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-12 15:17 ` Daniel Vetter
2021-04-12 15:17 ` Daniel Vetter
2021-04-12 16:01 ` Jani Nikula
2021-04-12 16:01 ` Jani Nikula
2021-04-12 16:36 ` Daniel Vetter
2021-04-12 16:36 ` Daniel Vetter
2021-04-12 16:08 ` Matthew Auld
2021-04-12 16:08 ` Matthew Auld
2021-04-12 17:00 ` Daniel Vetter
2021-04-12 17:00 ` Daniel Vetter
2021-04-13 9:28 ` Matthew Auld
2021-04-13 9:28 ` Matthew Auld
2021-04-13 10:18 ` Daniel Vetter
2021-04-13 10:18 ` Daniel Vetter
2021-04-12 9:05 ` [PATCH 19/19] drm/i915/gtt/dgfx: place the PD in LMEM Matthew Auld
2021-04-12 9:05 ` [Intel-gfx] " Matthew Auld
2021-04-14 15:37 ` Tvrtko Ursulin
2021-04-14 15:37 ` Tvrtko Ursulin
2021-04-12 11:07 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for More DG1 enabling Patchwork
2021-04-12 11:12 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2021-04-12 11:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-04-12 13:37 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=4dc60bcc-ffb8-db6a-dc0d-4a3700661258@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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.