All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [CI 3/6] drm/i915: Track page table backing store usage
Date: Tue,  7 Nov 2023 10:18:03 +0000	[thread overview]
Message-ID: <20231107101806.608990-3-tvrtko.ursulin@linux.intel.com> (raw)
In-Reply-To: <20231107101806.608990-1-tvrtko.ursulin@linux.intel.com>

From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Account page table backing store against the owning client memory usage
stats.

Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: Aravind Iddamsetty <aravind.iddamsetty@intel.com>
---
 drivers/gpu/drm/i915/gt/intel_gtt.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/gpu/drm/i915/gt/intel_gtt.c b/drivers/gpu/drm/i915/gt/intel_gtt.c
index 4fbed27ef0ec..3bef6d0769c6 100644
--- a/drivers/gpu/drm/i915/gt/intel_gtt.c
+++ b/drivers/gpu/drm/i915/gt/intel_gtt.c
@@ -63,6 +63,9 @@ struct drm_i915_gem_object *alloc_pt_lmem(struct i915_address_space *vm, int sz)
 	if (!IS_ERR(obj)) {
 		obj->base.resv = i915_vm_resv_get(vm);
 		obj->shares_resv_from = vm;
+
+		if (vm->fpriv)
+			i915_drm_client_add_object(vm->fpriv->client, obj);
 	}
 
 	return obj;
@@ -84,6 +87,9 @@ struct drm_i915_gem_object *alloc_pt_dma(struct i915_address_space *vm, int sz)
 	if (!IS_ERR(obj)) {
 		obj->base.resv = i915_vm_resv_get(vm);
 		obj->shares_resv_from = vm;
+
+		if (vm->fpriv)
+			i915_drm_client_add_object(vm->fpriv->client, obj);
 	}
 
 	return obj;
-- 
2.39.2


  parent reply	other threads:[~2023-11-07 10:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 10:18 [Intel-gfx] [CI 1/6] drm/i915: Add ability for tracking buffer objects per client Tvrtko Ursulin
2023-11-07 10:18 ` [Intel-gfx] [CI 2/6] drm/i915: Record which client owns a VM Tvrtko Ursulin
2023-11-07 10:18 ` Tvrtko Ursulin [this message]
2023-11-07 10:18 ` [Intel-gfx] [CI 4/6] drm/i915: Account ring buffer and context state storage Tvrtko Ursulin
2023-11-07 10:18 ` [Intel-gfx] [CI 5/6] drm/i915: Add stable memory region names Tvrtko Ursulin
2023-11-07 10:18 ` [Intel-gfx] [CI 6/6] drm/i915: Implement fdinfo memory stats printing Tvrtko Ursulin
2023-11-07 13:17 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/6] drm/i915: Add ability for tracking buffer objects per client Patchwork
2023-11-07 13:29 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-08  4:00 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-08 10:39 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/6] drm/i915: Add ability for tracking buffer objects per client (rev2) Patchwork
2023-11-08 10:57 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-08 14:22 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/6] drm/i915: Add ability for tracking buffer objects per client (rev3) Patchwork
2023-11-08 14:39 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-08 19:54 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/6] drm/i915: Add ability for tracking buffer objects per client (rev4) Patchwork
2023-11-08 20:11 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-11-09 19:01 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/6] drm/i915: Add ability for tracking buffer objects per client (rev5) Patchwork
2023-11-09 19:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-09 23:54 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-10 11:52   ` Tvrtko Ursulin
  -- strict thread matches above, loose matches on Subject: below --
2023-11-06 12:36 [Intel-gfx] [CI 0/6] fdinfo memory CI run Tvrtko Ursulin
2023-11-06 12:36 ` [Intel-gfx] [CI 3/6] drm/i915: Track page table backing store usage Tvrtko Ursulin

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=20231107101806.608990-3-tvrtko.ursulin@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --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 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.