Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: "Upadhyay, Tejas" <tejas.upadhyay@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] [PATCH 4/7] drm/xe: Record each drm client with its VM
Date: Thu, 7 Sep 2023 14:58:59 +0530	[thread overview]
Message-ID: <cf6b7769-d433-4c56-8b2c-ec8aed1fe8c2@intel.com> (raw)
In-Reply-To: <SJ1PR11MB62044B92B265221880903F5081EEA@SJ1PR11MB6204.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]


On 07-09-2023 14:19, Upadhyay, Tejas wrote:
>
> *From:*Ghimiray, Himal Prasad <himal.prasad.ghimiray@intel.com>
> *Sent:* Wednesday, September 6, 2023 3:18 PM
> *To:* Upadhyay, Tejas <tejas.upadhyay@intel.com>; 
> intel-xe@lists.freedesktop.org
> *Cc:* Iddamsetty, Aravind <aravind.iddamsetty@intel.com>
> *Subject:* Re: [PATCH 4/7] drm/xe: Record each drm client with its VM
>
> On 31-08-2023 14:35, Tejas Upadhyay wrote:
>
>     Enable accounting of indirect client memory usage.
>
>     Signed-off-by: Tejas Upadhyay<tejas.upadhyay@intel.com>  <mailto: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 9cbf2f63d641..f5f832c8ed42 100644
>
>     --- a/drivers/gpu/drm/xe/xe_vm.c
>
>     +++ b/drivers/gpu/drm/xe/xe_vm.c
>
>     @@ -2057,6 +2057,7 @@ int xe_vm_create_ioctl(struct drm_device *dev, void *data,
>
>              }
>
>       
>
>              args->vm_id = id;
>
>     +       vm->xef = xef;
>
> shouldn't it be applicable only if |CONFIG_PROC_FS is enabled ? |
>
> Tracking VM is not dependent on proc fs so it does not give relation. 
>  Adding bo and FDINFO read/parse is only dependent on procfs otherwise 
> dummy calls. So I do not think it is necessary. Please let me know if 
> you think otherwise.
>
> Thanks,
>
> Tejas
>
Do we have any other use case in mind for vm tracking ? If yes let it be 
as it is, otherwise making it procfs config dependent is better.

BR

Himal Ghimiray

>       
>
>       #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 fd2178dbde3a..db8523d81d0f 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;
>
> Same comment as above.
>
>       };
>
>       
>
>       /** struct xe_vma_op_map - VMA map operation */
>

[-- Attachment #2: Type: text/html, Size: 7774 bytes --]

  reply	other threads:[~2023-09-07  9:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31  9:05 [Intel-xe] [PATCH 0/7] drm/xe: fdinfo memory stats Tejas Upadhyay
2023-08-31  9:05 ` [Intel-xe] [PATCH 1/7] drm/xe: Add drm-client infrastructure Tejas Upadhyay
2023-09-06  4:14   ` Ghimiray, Himal Prasad
2023-09-07  8:57     ` Upadhyay, Tejas
2023-09-12  8:24       ` Ghimiray, Himal Prasad
2023-08-31  9:05 ` [Intel-xe] [PATCH 2/7] drm/xe: Interface xe drm client with fdinfo interface Tejas Upadhyay
2023-09-06  4:21   ` Ghimiray, Himal Prasad
2023-08-31  9:05 ` [Intel-xe] [PATCH 3/7] drm/xe: Add tracking support for bos per client Tejas Upadhyay
2023-09-06  9:38   ` Ghimiray, Himal Prasad
2023-09-07  8:52     ` Upadhyay, Tejas
2023-08-31  9:05 ` [Intel-xe] [PATCH 4/7] drm/xe: Record each drm client with its VM Tejas Upadhyay
2023-09-06  9:47   ` Ghimiray, Himal Prasad
2023-09-07  8:49     ` Upadhyay, Tejas
2023-09-07  9:28       ` Ghimiray, Himal Prasad [this message]
2023-09-07  9:44         ` Upadhyay, Tejas
2023-08-31  9:05 ` [Intel-xe] [PATCH 5/7] drm/xe: Track page table memory usage for client Tejas Upadhyay
2023-09-06  9:54   ` Ghimiray, Himal Prasad
2023-09-07  8:40     ` Upadhyay, Tejas
2023-08-31  9:05 ` [Intel-xe] [PATCH 6/7] drm/xe: Account ring buffer and context state storage Tejas Upadhyay
2023-09-06 11:19   ` Ghimiray, Himal Prasad
2023-08-31  9:05 ` [Intel-xe] [PATCH 7/7] drm/xe: Implement fdinfo memory stats printing Tejas Upadhyay
2023-08-31 12:19   ` Upadhyay, Tejas
2023-09-12  6:22   ` Ghimiray, Himal Prasad
2023-09-12 11:14     ` Jani Nikula
2023-08-31  9:21 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: fdinfo memory stats Patchwork
2023-08-31  9:21 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-31  9:22 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-31  9:29 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-08-31  9:30 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-08-31  9:30 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-08-31 10:04 ` [Intel-xe] ✓ CI.BAT: success " Patchwork
2023-08-31 11:23 ` Patchwork
2023-09-07  9:22 ` [Intel-xe] [PATCH 0/7] " Ghimiray, Himal Prasad
2023-09-07  9:35   ` Upadhyay, Tejas

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=cf6b7769-d433-4c56-8b2c-ec8aed1fe8c2@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