On Wed, Aug 30, 2023 at 8:51 AM Adrián Larumbe
wrote:
>
> >> The current implementation will try to pick the highest available
> >> unit. This is rather unflexible, and allowing drivers to display BO size
> >> statistics through fdinfo in units of their choice might be desirable.
> >>
> >> The
patch link:
https://lore.kernel.org/r/20230824013604.466224-7-adrian.larumbe%40collabora.com
patch subject: [PATCH v2 6/6] drm/drm-file: Allow size unit selection in
drm_show_memory_stats
config: x86_64-randconfig-002-20230902
(https://download.01.org/0day-ci/archive/20230902/202309020634
>> The current implementation will try to pick the highest available
>> unit. This is rather unflexible, and allowing drivers to display BO size
>> statistics through fdinfo in units of their choice might be desirable.
>>
>> The new argument to drm_show_memory_stats is to be interpreted as the
>>
On Wed, Aug 23, 2023 at 6:36 PM Adrián Larumbe
wrote:
>
> The current implementation will try to pick the highest available
> unit. This is rather unflexible, and allowing drivers to display BO size
> statistics through fdinfo in units of their choice might be desirable.
>
> The new argument to
-next
patch link:
https://lore.kernel.org/r/20230824013604.466224-7-adrian.larumbe%40collabora.com
patch subject: [PATCH v2 6/6] drm/drm-file: Allow size unit selection in
drm_show_memory_stats
config: m68k-allyesconfig
(https://download.01.org/0day-ci/archive/20230824/202308241401.hr6gvevs
The current implementation will try to pick the highest available
unit. This is rather unflexible, and allowing drivers to display BO size
statistics through fdinfo in units of their choice might be desirable.
The new argument to drm_show_memory_stats is to be interpreted as the
integer