From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Aravind Iddamsetty <aravind.iddamsetty@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: [PATCH 3/6] drm/i915: Track page table backing store usage
Date: Fri, 22 Sep 2023 14:46:57 +0100 [thread overview]
Message-ID: <20230922134700.235039-4-tvrtko.ursulin@linux.intel.com> (raw)
In-Reply-To: <20230922134700.235039-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 13944a14ea2d..c3f29999b379 100644
--- a/drivers/gpu/drm/i915/gt/intel_gtt.c
+++ b/drivers/gpu/drm/i915/gt/intel_gtt.c
@@ -58,6 +58,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;
@@ -79,6 +82,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
next prev parent reply other threads:[~2023-09-22 13:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 13:46 [PATCH v7 0/6] fdinfo memory stats Tvrtko Ursulin
2023-09-22 13:46 ` [PATCH 1/6] drm/i915: Add ability for tracking buffer objects per client Tvrtko Ursulin
2023-09-22 13:46 ` [PATCH 2/6] drm/i915: Record which client owns a VM Tvrtko Ursulin
2023-09-22 13:46 ` Tvrtko Ursulin [this message]
2023-09-22 13:46 ` [PATCH 4/6] drm/i915: Account ring buffer and context state storage Tvrtko Ursulin
2023-09-22 13:46 ` [PATCH 5/6] drm/i915: Add stable memory region names Tvrtko Ursulin
2023-09-26 15:29 ` Iddamsetty, Aravind
2023-09-26 15:42 ` Tvrtko Ursulin
2023-09-27 4:43 ` Iddamsetty, Aravind
2023-09-22 13:47 ` [PATCH 6/6] drm/i915: Implement fdinfo memory stats printing Tvrtko Ursulin
2023-09-27 4:58 ` Iddamsetty, Aravind
2023-09-27 6:54 ` Andi Shyti
2023-09-27 13:23 ` Tvrtko Ursulin
2023-09-27 13:24 ` Tvrtko Ursulin
2023-09-27 8:07 ` kernel test robot
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=20230922134700.235039-4-tvrtko.ursulin@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=aravind.iddamsetty@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tvrtko.ursulin@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