mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-11-26 09:20:54 +07:00
drm/mm: Document locking rules
Drivers need to take care. Motivated by a discussion between Mark and Rob on dri-devel. Cc: Mark yao <mark.yao@rock-chips.com> Cc: Rob Clark <robdclark@gmail.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> [danvet: s/alloc|freeing/modifications/ per Chris' suggestion.] Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/1482833457-29592-1-git-send-email-daniel.vetter@ffwll.ch
This commit is contained in:
parent
adb040b86b
commit
1c9bd1ede8
@ -90,6 +90,11 @@
|
||||
*
|
||||
* Finally iteration helpers to walk all nodes and all holes are provided as are
|
||||
* some basic allocator dumpers for debugging.
|
||||
*
|
||||
* Note that this range allocator is not thread-safe, drivers need to protect
|
||||
* modifications with their on locking. The idea behind this is that for a full
|
||||
* memory manager additional data needs to be protected anyway, hence internal
|
||||
* locking would be fully redundant.
|
||||
*/
|
||||
|
||||
static struct drm_mm_node *drm_mm_search_free_in_range_generic(const struct drm_mm *mm,
|
||||
|
Loading…
Reference in New Issue
Block a user