From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Tejas Upadhyay <tejas.upadhyay@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] [PATCH V2 4/7] drm/xe: Record each drm client with its VM
Date: Wed, 13 Sep 2023 14:28:13 +0530 [thread overview]
Message-ID: <f441acbe-c4de-4e2e-872a-648b97ecaa33@intel.com> (raw)
In-Reply-To: <20230912115239.3554341-5-tejas.upadhyay@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
On 12-09-2023 17:22, Tejas Upadhyay wrote:
> Enable accounting of indirect client memory usage.
>
> Signed-off-by: Tejas Upadhyay<tejas.upadhyay@intel.com>
> ---
> drivers/gpu/drm/xe/xe_vm.c | 1 +
> drivers/gpu/drm/xe/xe_vm_types.h | 2 ++
> 2 files changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index a6a0f17fec1d..92d8c78c9284 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -2051,6 +2051,7 @@ int xe_vm_create_ioctl(struct drm_device *dev, void *data,
> }
>
> args->vm_id = id;
> + vm->xef = xef;
>
> #if IS_ENABLED(CONFIG_DRM_XE_DEBUG_MEM)
> /* Warning: Security issue - never enable by default */
> diff --git a/drivers/gpu/drm/xe/xe_vm_types.h b/drivers/gpu/drm/xe/xe_vm_types.h
> index 52e5eaed91c3..af2ba4acf1f9 100644
> --- a/drivers/gpu/drm/xe/xe_vm_types.h
> +++ b/drivers/gpu/drm/xe/xe_vm_types.h
> @@ -336,6 +336,8 @@ struct xe_vm {
>
> /** @batch_invalidate_tlb: Always invalidate TLB before batch start */
> bool batch_invalidate_tlb;
> + /** @xef: XE file handle for tracking this VM's drm client */
> + struct xe_file *xef;
LGTM. Reviewed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> };
>
> /** struct xe_vma_op_map - VMA map operation */
[-- Attachment #2: Type: text/html, Size: 2729 bytes --]
next prev parent reply other threads:[~2023-09-13 8:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 11:52 [Intel-xe] [PATCH V2 0/7] drm/xe: fdinfo memory stats Tejas Upadhyay
2023-09-12 11:52 ` [Intel-xe] [PATCH V2 1/7] drm/xe: Add drm-client infrastructure Tejas Upadhyay
2023-09-12 11:52 ` [Intel-xe] [PATCH V2 2/7] drm/xe: Interface xe drm client with fdinfo interface Tejas Upadhyay
2023-09-12 11:52 ` [Intel-xe] [PATCH V2 3/7] drm/xe: Add tracking support for bos per client Tejas Upadhyay
2023-09-13 8:39 ` Ghimiray, Himal Prasad
2023-09-12 11:52 ` [Intel-xe] [PATCH V2 4/7] drm/xe: Record each drm client with its VM Tejas Upadhyay
2023-09-13 8:58 ` Ghimiray, Himal Prasad [this message]
2023-09-12 11:52 ` [Intel-xe] [PATCH V2 5/7] drm/xe: Track page table memory usage for client Tejas Upadhyay
2023-09-13 8:38 ` Ghimiray, Himal Prasad
2023-09-12 11:52 ` [Intel-xe] [PATCH V2 6/7] drm/xe: Account ring buffer and context state storage Tejas Upadhyay
2023-09-12 11:52 ` [Intel-xe] [PATCH V2 7/7] drm/xe: Implement fdinfo memory stats printing Tejas Upadhyay
2023-09-12 12:06 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: fdinfo memory stats (rev2) Patchwork
2023-09-12 12:07 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-12 12:08 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-12 12:15 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-12 12:15 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-12 12:17 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-12 12:49 ` [Intel-xe] ✓ CI.BAT: " Patchwork
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=f441acbe-c4de-4e2e-872a-648b97ecaa33@intel.com \
--to=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=tejas.upadhyay@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