From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Report correct GGTT space usage
Date: Tue, 30 Jun 2015 10:50:15 +0100 [thread overview]
Message-ID: <55926657.4070804@linux.intel.com> (raw)
In-Reply-To: <20150630093659.GL15506@nuc-i3427.alporthouse.com>
On 06/30/2015 10:36 AM, Chris Wilson wrote:
> On Tue, Jun 30, 2015 at 10:28:02AM +0100, Tvrtko Ursulin wrote:
>> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
>> index a2a4a27..7d69294 100644
>> --- a/drivers/gpu/drm/i915/i915_gem.c
>> +++ b/drivers/gpu/drm/i915/i915_gem.c
>> @@ -156,7 +156,7 @@ i915_gem_get_aperture_ioctl(struct drm_device *dev, void *data,
>> mutex_lock(&dev->struct_mutex);
>> list_for_each_entry(obj, &dev_priv->mm.bound_list, global_list)
>> if (i915_gem_obj_is_pinned(obj))
>> - pinned += i915_gem_obj_ggtt_size(obj);
>> + pinned += i915_gem_obj_total_ggtt_size(obj);
>
> Please just rewrite this as a single vma walk, or review the patches I
> sent to do so.
Sorry there is a lot of patches floating around and I don't know which
ones you refer too.
I just noticed debugfs displays wrong values when GGTT views other than
normal are present.
So just open code the loop in get_aperture you say?
It is slightly ugly when there are helpers, but it is also true
different callers want to know slightly different things. (Difference
between GGTT usage reported in get_aperture vs debugfs - pinned or just
allocated.)
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-06-30 9:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 9:28 [PATCH] drm/i915: Report correct GGTT space usage Tvrtko Ursulin
2015-06-30 9:36 ` Chris Wilson
2015-06-30 9:50 ` Tvrtko Ursulin [this message]
2015-06-30 10:01 ` Chris Wilson
2015-06-30 10:27 ` [PATCH v2] " Tvrtko Ursulin
2015-06-30 10:33 ` Chris Wilson
2015-06-30 11:03 ` Tvrtko Ursulin
2015-06-30 11:35 ` Chris Wilson
2015-06-30 12:53 ` [PATCH v3] " Tvrtko Ursulin
2015-06-30 13:30 ` Chris Wilson
2015-06-30 14:32 ` [PATCH v4] " Tvrtko Ursulin
2015-06-30 15:00 ` Chris Wilson
2015-07-01 10:53 ` Tvrtko Ursulin
2015-07-01 10:58 ` Chris Wilson
2015-07-02 7:30 ` shuang.he
2015-07-02 0:23 ` [PATCH v3] " shuang.he
2015-07-01 20:01 ` [PATCH v2] " shuang.he
2015-07-01 17:58 ` [PATCH] " 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=55926657.4070804@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
/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