Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	tvrtko.ursulin@linux.intel.com, daniel@ffwll.ch
Subject: Re: [PATCH 0/6 V4] fdinfo shared stats
Date: Fri, 16 Feb 2024 13:45:27 +0100	[thread overview]
Message-ID: <c3563341-bfcb-4df9-a6c0-f983835a4e2e@gmail.com> (raw)
In-Reply-To: <CADnq5_MwEB_=2uySBmiOu3mBcA=uRDvsoA_jT9umHNnwLELWZQ@mail.gmail.com>

Am 15.02.24 um 15:20 schrieb Alex Deucher:
> On Thu, Feb 15, 2024 at 9:18 AM Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>> Am 12.02.24 um 22:04 schrieb Alex Deucher:
>>> We had a request to add shared buffer stats to fdinfo for amdgpu and
>>> while implementing that, Christian mentioned that just looking at
>>> the GEM handle count doesn't take into account buffers shared with other
>>> subsystems like V4L or RDMA.  Those subsystems don't use GEM, so it
>>> doesn't really matter from a GPU top perspective, but it's more
>>> correct if you actually want to see shared buffers.
>>>
>>> After further discussions, add a helper and update all fdinfo
>>> implementations to use that helper for consistency.
>>>
>>> v4: switch drm_gem_object_is_shared_for_memory_stats() to an inline function
>> I'm still not sure if looking at the actual handle count is the right
>> approach, but it's certainly better than before.
> Well, it's consistent across drivers.

Yeah, which makes it easy to change if we find something better.

>
>> So Reviewed-by: Christian König <christian.koenig@amd.com> for the
>> entire series.
>>
>> Should I take this through drm-misc-next?
> Yes, please.

Done.

Regards,
Christian.

>
> Thanks,
>
> Alex
>
>> Regards,
>> Christian.
>>
>>> Alex Deucher (6):
>>>     Documentation/gpu: Update documentation on drm-shared-*
>>>     drm: add drm_gem_object_is_shared_for_memory_stats() helper
>>>     drm: update drm_show_memory_stats() for dma-bufs
>>>     drm/amdgpu: add shared fdinfo stats
>>>     drm/i915: Update shared stats to use the new gem helper
>>>     drm/xe: Update shared stats to use the new gem helper
>>>
>>>    Documentation/gpu/drm-usage-stats.rst      |  2 +-
>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_fdinfo.c |  4 ++++
>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 11 +++++++++++
>>>    drivers/gpu/drm/amd/amdgpu/amdgpu_object.h |  6 ++++++
>>>    drivers/gpu/drm/drm_file.c                 |  2 +-
>>>    drivers/gpu/drm/i915/i915_drm_client.c     |  2 +-
>>>    drivers/gpu/drm/xe/xe_drm_client.c         |  2 +-
>>>    include/drm/drm_gem.h                      | 13 +++++++++++++
>>>    8 files changed, 38 insertions(+), 4 deletions(-)
>>>


      reply	other threads:[~2024-02-16 12:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 21:04 [PATCH 0/6 V4] fdinfo shared stats Alex Deucher
2024-02-12 21:04 ` [PATCH 1/6] Documentation/gpu: Update documentation on drm-shared-* Alex Deucher
2024-02-12 21:04 ` [PATCH 2/6] drm: add drm_gem_object_is_shared_for_memory_stats() helper Alex Deucher
2024-02-12 21:04 ` [PATCH 3/6] drm: update drm_show_memory_stats() for dma-bufs Alex Deucher
2024-02-12 21:04 ` [PATCH 4/6] drm/amdgpu: add shared fdinfo stats Alex Deucher
2024-02-12 21:04 ` [PATCH 5/6] drm/i915: Update shared stats to use the new gem helper Alex Deucher
2024-02-12 21:04 ` [PATCH 6/6] drm/xe: " Alex Deucher
2024-02-13  5:29 ` ✓ CI.Patch_applied: success for fdinfo shared stats (rev3) Patchwork
2024-02-13  5:29 ` ✗ CI.checkpatch: warning " Patchwork
2024-02-13  5:30 ` ✓ CI.KUnit: success " Patchwork
2024-02-13  5:40 ` ✓ CI.Build: " Patchwork
2024-02-13  5:41 ` ✓ CI.Hooks: " Patchwork
2024-02-13  5:42 ` ✗ CI.checksparse: warning " Patchwork
2024-02-13  6:18 ` ✓ CI.BAT: success " Patchwork
2024-02-15 14:12 ` [PATCH 0/6 V4] fdinfo shared stats Christian König
2024-02-15 14:20   ` Alex Deucher
2024-02-16 12:45     ` Christian König [this message]

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=c3563341-bfcb-4df9-a6c0-f983835a4e2e@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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