Improved TTM Memory Management Eviction Submitted Ahead Of Linux 6.17
Sent out today was the newest drm-misc-next pull request of changes built up over the past week for DRM-Next ahead of the Linux 6.17 kernel cycle. The drm-misc-next material is the usual random assortment of DRM display/graphics driver changes and core improvements, which this week includes some TTM eviction work.
The drm-misc-next code in today's pull request includes adding AM65x OLDI bridge support to the TIDSS driver, the Intel i915 driver now using backlight control helpers for embedded DisplayPort (eDP), a few new display panels being supported, and then improved eviction for the TTM memory management code.
The TTM memory management code continues to be used by several DRM drivers. The TTM work this round is from Intel engineer Thomas Hellström to enhance the core code and carrying through some improvements to the Intel Xe graphics driver.
The work queued is the series to consolidate the buffer object LRU walks. Thomas explained in that patch series about the clean-up/consolidation for that TTM code:
The drm-misc-next code is working its way to DRM-Next for then merging into Linux 6.17 once that merge window opens in a few weeks.
The drm-misc-next code in today's pull request includes adding AM65x OLDI bridge support to the TIDSS driver, the Intel i915 driver now using backlight control helpers for embedded DisplayPort (eDP), a few new display panels being supported, and then improved eviction for the TTM memory management code.
The TTM memory management code continues to be used by several DRM drivers. The TTM work this round is from Intel engineer Thomas Hellström to enhance the core code and carrying through some improvements to the Intel Xe graphics driver.
The work queued is the series to consolidate the buffer object LRU walks. Thomas explained in that patch series about the clean-up/consolidation for that TTM code:
"This is a deferred task from the Xe bo shrinker addition.
TTM currently have two separate ways of doing buffer object LRU walks, of which one is exposed to drivers. Both have their benefits but we shouldn't be implementing the complex bo locking in two different places. So implement the ttm_lru_walk_for_evict() function in terms of the guarded iteration also exposed to drivers.
This means that when we get to implement locking using drm_exec, we only need to do that in a single place.
Add ticketlocking support to the guarded iteration and modify the iteration arguments."
The drm-misc-next code is working its way to DRM-Next for then merging into Linux 6.17 once that merge window opens in a few weeks.