From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v2 5/5] drm/i915: Use partial view in mmap fault handler
Date: Thu, 30 Apr 2015 13:32:21 +0100 [thread overview]
Message-ID: <554220D5.6000307@linux.intel.com> (raw)
In-Reply-To: <1430392887.1189.10.camel@jlahtine-mobl1>
On 04/30/2015 12:21 PM, Joonas Lahtinen wrote:
>
> Use partial view for huge BOs (bigger than the mappable aperture)
> in fault handler so that they can be accessed without trying to make
> room for them by evicting other objects.
>
> v2:
> - Only use partial views in the case where early rejection was
> previously done.
> - Account variable type changes from previous reroll.
>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 69 +++++++++++++++++++++++++++--------------
> 1 file changed, 46 insertions(+), 23 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index a020836..2f3fa0b 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -1635,6 +1635,7 @@ int i915_gem_fault(struct vm_area_struct *vma, struct vm_fault *vmf)
> struct drm_i915_gem_object *obj = to_intel_bo(vma->vm_private_data);
> struct drm_device *dev = obj->base.dev;
> struct drm_i915_private *dev_priv = dev->dev_private;
> + struct i915_ggtt_view view = i915_ggtt_view_normal;
> pgoff_t page_offset;
> unsigned long pfn;
> int ret = 0;
> @@ -1667,8 +1668,21 @@ int i915_gem_fault(struct vm_area_struct *vma, struct vm_fault *vmf)
> goto unlock;
> }
>
> - /* Now bind it into the GTT if needed */
> - ret = i915_gem_obj_ggtt_pin(obj, 0, PIN_MAPPABLE);
> + /* Use a partial view if the object is bigger than the aperture. */
> + if (obj->base.size >= dev_priv->gtt.mappable_end) {
> + static const unsigned int chunk_size = 256; // 1 MiB
> + memset(&view, 0, sizeof(view));
I think you don't need to memset since you assigned normal view to it.
> + view.type = I915_GGTT_VIEW_PARTIAL;
> + view.params.partial.offset = rounddown(page_offset, chunk_size);
> + view.params.partial.size =
> + min_t(unsigned int,
> + chunk_size,
> + (vma->vm_end - vma->vm_start)/PAGE_SIZE -
> + view.params.partial.offset);
> + }
> +
> + /* Now pin it into the GTT if needed */
> + ret = i915_gem_object_ggtt_pin(obj, &view, 0, PIN_MAPPABLE);
Next fault outside this partial view will create a new vma? Is there
something which would remove the old one for that case? Or they are just
allowed to accumulate?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-04-30 12:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1430392239.git.joonas.lahtinen@linux.intel.com>
2015-04-30 11:18 ` [PATCH v2 1/5] drm/i915: Do not clear mappings beyond VMA size Joonas Lahtinen
2015-04-30 11:19 ` [PATCH v2 2/5] drm/i915: Do not make assumptions on GGTT VMA sizes Joonas Lahtinen
2015-04-30 12:03 ` Tvrtko Ursulin
2015-05-06 11:43 ` Joonas Lahtinen
2015-04-30 11:20 ` [PATCH v2 3/5] drm/i915: Consider object pinned if any VMA is pinned Joonas Lahtinen
2015-04-30 11:20 ` [PATCH v2 4/5] drm/i915: Add a partial GGTT view type Joonas Lahtinen
2015-04-30 12:16 ` Tvrtko Ursulin
2015-05-06 10:20 ` Daniel Vetter
2015-05-06 11:40 ` Joonas Lahtinen
2015-05-07 16:15 ` Daniel Vetter
2015-04-30 11:21 ` [PATCH v2 5/5] drm/i915: Use partial view in mmap fault handler Joonas Lahtinen
2015-04-30 12:32 ` Tvrtko Ursulin [this message]
2015-04-30 14:54 ` Tvrtko Ursulin
2015-05-04 11:51 ` Joonas Lahtinen
2015-05-05 9:07 ` Tvrtko Ursulin
2015-05-06 11:30 ` Joonas Lahtinen
2015-05-01 20:56 ` shuang.he
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=554220D5.6000307@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@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