Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arunpravin Paneer Selvam <arunpravin.paneerselvam@amd.com>
To: "Christian König" <christian.koenig@amd.com>,
	"Daniel Vetter" <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
	luben.tuikov@amd.com, dri-devel@lists.freedesktop.org,
	alexander.deucher@amd.com, matthew.auld@intel.com
Subject: Re: [Intel-gfx] [PATCH v6 1/6] drm/ttm: Add new callbacks to ttm res mgr
Date: Thu, 8 Sep 2022 16:38:24 +0530	[thread overview]
Message-ID: <c0036ff6-b667-4c70-6d2b-d9ecbb10f508@amd.com> (raw)
In-Reply-To: <291548ba-3fbe-6a7d-eda1-ac12f1e799ff@amd.com>



On 9/8/2022 11:34 AM, Christian König wrote:
> Am 07.09.22 um 19:00 schrieb Daniel Vetter:
>> [SNIP]
>>>> I'm a bit confused why the bloat here ...
>>> Drivers do have specialized implementations of the backend, e.g. 
>>> VMWGFX have
>>> his handle backend, amdgpu the VRAM backend with special placements, 
>>> i915 is
>>> completely special as well.
>>>
>>> Here we only move the decision if resources intersect or are 
>>> compatible into
>>> those specialized backends. Previously we had all this in a centralized
>>> callback for all backends of a driver.
>>>
>>> See the switch in amdgpu_ttm_bo_eviction_valuable() for an example. 
>>> Final
>>> goal is to move all this stuff into the specialized backends and 
>>> remove this
>>> callback.
>>>
>>> The only driver where I couldn't figure out why we have duplicated 
>>> all this
>>> from the standard implementation is Nouveau.
>> Yeah I didn't read this too carefully, apologies.
>>
>>>> Also please document new callbacks precisely with inline kerneldoc. 
>>>> I know
>>>> ttm docs aren't great yet, but they don't get better if we don't start
>>>> somewhere. I think the in-depth comments for modeset vfuncs (e.g. in
>>>> drm_modeset_helper_vtables.h) are a good standard here.
>>> I thought we already did that. Please be a bit more specific.
>> Yeah rushed this too, but the kerneldoc isn't too great yet. It's
>> definitely not formatted correctly (you can't do a full function
>> definition in a struct unfortunately, see the examples I linked). And it
>> would be good to specificy what the default implementation is, that 
>> there
>> is one (i.e. the hook is optional) and when exactly a driver would 
>> want to
>> overwrite this. Atm it's a one-liner that explains exactly as much as 
>> you
>> can guess from the function interface anyway, that's not super userful.
>> -Daniel
>
> Arun can you take care of improving this?

Hi Christian,
Yes, I will check on this.

Thanks,
Arun
>
> Thanks,
> Christian.
>
>>
>>
>>
>>> Thanks,
>>> Christian.
>>>
>>>> -Daniel
>>>>
>>>>> Thanks,
>>>>> Arun
>>>>>> Regards,
>>>>>> Christian.
>>>>>>
>


  reply	other threads:[~2022-09-08 11:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 13:30 [Intel-gfx] [PATCH v6 1/6] drm/ttm: Add new callbacks to ttm res mgr Arunpravin Paneer Selvam
2022-08-12 13:30 ` [Intel-gfx] [PATCH v6 2/6] drm/ttm: Implement intersect/compatible functions Arunpravin Paneer Selvam
2022-08-12 13:30 ` [Intel-gfx] [PATCH v6 3/6] drm/amdgpu: " Arunpravin Paneer Selvam
2022-08-12 13:30 ` [Intel-gfx] [PATCH v6 4/6] drm/i915: " Arunpravin Paneer Selvam
2022-08-12 13:30 ` [Intel-gfx] [PATCH v6 5/6] drm/nouveau: " Arunpravin Paneer Selvam
2022-08-12 13:30 ` [Intel-gfx] [PATCH v6 6/6] drm/ttm: Switch to using the new res callback Arunpravin Paneer Selvam
2022-08-12 13:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v6,1/6] drm/ttm: Add new callbacks to ttm res mgr Patchwork
2022-08-12 14:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-08-12 20:45 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-08-15 11:05 ` [Intel-gfx] [PATCH v6 1/6] " Christian König
2022-08-16  5:03   ` Arunpravin Paneer Selvam
2022-09-06 19:58     ` Daniel Vetter
2022-09-07  6:45       ` Christian König
2022-09-07 17:00         ` Daniel Vetter
2022-09-08  6:04           ` Christian König
2022-09-08 11:08             ` Arunpravin Paneer Selvam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-20  7:32 Arunpravin Paneer Selvam
2022-08-22 13:38 ` Christian König

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=c0036ff6-b667-4c70-6d2b-d9ecbb10f508@amd.com \
    --to=arunpravin.paneerselvam@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=luben.tuikov@amd.com \
    --cc=matthew.auld@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