From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: Preallocate mm node for GTT mmap offset
Date: Wed, 12 Dec 2012 12:48:43 +0200 [thread overview]
Message-ID: <87sj7ba6lw.fsf@intel.com> (raw)
In-Reply-To: <1354912628-7776-3-git-send-email-chris@chris-wilson.co.uk>
On Fri, 07 Dec 2012, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> As the shrinker may be invoked for the allocation, and it may reap
> neighbouring objects in the offset range mm, we need to be careful in
> the order in which we allocate the node, search for free space and then
> insert the node into the mmap offset range manager.
>
> Fixes i-g-t/gem_tiled_swapping
>
> Reported-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 59 ++++++++++++++++++++++++++++++++-------
> 1 file changed, 49 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index d17f52d..3ab97c6 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -1512,14 +1512,29 @@ i915_gem_get_unfenced_gtt_alignment(struct drm_device *dev,
> static int i915_gem_object_create_mmap_offset(struct drm_i915_gem_object *obj)
> {
> struct drm_i915_private *dev_priv = obj->base.dev->dev_private;
> + struct drm_gem_mm *mm = obj->base.dev->mm_private;
> + struct drm_map_list *list;
> int ret;
>
> - if (obj->base.map_list.map)
> + list = &obj->base.map_list;
> + if (list->map)
> return 0;
>
> - ret = drm_gem_create_mmap_offset(&obj->base);
> - if (ret != -ENOSPC)
> - return ret;
> + /* Set the object up for mmap'ing */
> + list->map = kzalloc(sizeof(struct drm_map_list), GFP_KERNEL);
sizeof(struct drm_local_map) or sizeof(*list->map) instead?
Hmm, it's like this in drm_gem_create_mmap_offset too, either it's a bug
or I'm being clueless.
Other than that, with the same disclaimer as on the previous patch,
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> + if (!list->map)
> + return -ENOMEM;
> +
> + list->map->type = _DRM_GEM;
> + list->map->size = obj->base.size;
> + list->map->handle = &obj->base;
> +
> + /* Get a DRM GEM mmap offset allocated... */
> + list->file_offset_node = kzalloc(sizeof(struct drm_mm_node), GFP_KERNEL);
> + if (list->file_offset_node == NULL) {
> + ret = -ENOMEM;
> + goto out_free_list;
> + }
>
> /* Badly fragmented mmap space? The only way we can recover
> * space is by destroying unwanted objects. We can't randomly release
> @@ -1528,13 +1543,37 @@ static int i915_gem_object_create_mmap_offset(struct drm_i915_gem_object *obj)
> * offsets on purgeable objects by truncating it and marking it purged,
> * which prevents userspace from ever using that object again.
> */
> - i915_gem_purge(dev_priv, obj->base.size >> PAGE_SHIFT);
> - ret = drm_gem_create_mmap_offset(&obj->base);
> - if (ret != -ENOSPC)
> - return ret;
> + ret = drm_mm_insert_node(&mm->offset_manager, list->file_offset_node,
> + obj->base.size / PAGE_SIZE, 0);
> + if (ret) {
> + i915_gem_purge(dev_priv, obj->base.size >> PAGE_SHIFT);
> + ret = drm_mm_insert_node(&mm->offset_manager, list->file_offset_node,
> + obj->base.size / PAGE_SIZE, 0);
> + }
> + if (ret) {
> + i915_gem_shrink_all(dev_priv);
> + ret = drm_mm_insert_node(&mm->offset_manager, list->file_offset_node,
> + obj->base.size / PAGE_SIZE, 0);
> + }
> + if (ret) {
> + kfree(list->file_offset_node);
> + goto out_free_list;
> + }
> +
> + list->hash.key = list->file_offset_node->start;
> + ret = drm_ht_insert_item(&mm->offset_hash, &list->hash);
> + if (ret)
> + goto out_free_mm;
>
> - i915_gem_shrink_all(dev_priv);
> - return drm_gem_create_mmap_offset(&obj->base);
> + return 0;
> +
> +out_free_mm:
> + drm_mm_put_block(list->file_offset_node);
> +out_free_list:
> + kfree(list->map);
> + list->map = NULL;
> +
> + return ret;
> }
>
> static void i915_gem_object_free_mmap_offset(struct drm_i915_gem_object *obj)
> --
> 1.7.10.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2012-12-12 10:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 20:37 [PATCH 1/3] drm: Export routines for inserting preallocated nodes into the mm manager Chris Wilson
2012-12-07 20:37 ` [PATCH 2/3] drm/i915: Preallocate the drm_mm_node prior to manipulating the GTT drm_mm manager Chris Wilson
2012-12-12 10:18 ` Jani Nikula
2012-12-12 10:27 ` Chris Wilson
2012-12-07 20:37 ` [PATCH 3/3] drm/i915: Preallocate mm node for GTT mmap offset Chris Wilson
2012-12-12 10:48 ` Jani Nikula [this message]
2012-12-12 10:55 ` Chris Wilson
2012-12-18 21:11 ` Daniel Vetter
2012-12-18 22:36 ` Daniel Vetter
2012-12-18 22:10 ` Dave Airlie
2012-12-18 22:40 ` Chris Wilson
2012-12-12 10:02 ` [PATCH 1/3] drm: Export routines for inserting preallocated nodes into the mm manager Jani Nikula
2012-12-18 0:28 ` Daniel Vetter
2012-12-18 9:13 ` Chris Wilson
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=87sj7ba6lw.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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