diff options
author | Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> | 2020-09-16 13:50:09 +0100 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2020-09-16 14:15:12 +0100 |
commit | d2fed122bddd0db84cd7761e901f7a70bb689cbb (patch) | |
tree | 60a733908908bb9161b996685749ec85db71f24a /lib/intel_batchbuffer.c | |
parent | 705dab66421391804fd7981953ba88ccf7b4e34c (diff) |
lib/intel_bufops: clarify buffer ownership rules
To avoid intel_buf handle leakage we need to clarify of buffer ownership
rules. So we currently have:
1. intel_buf_init(), intel_buf_create() which create handle and take
ownership of such handle.
2. intel_buf_init_using_handle(), intel_buf_create_using_handle() which
take bo handle from the caller and doesn't take ownership.
intel_buf_close()/intel_buf_destroy() will honour ownership and skip
closing handle if buffer is not owned.
To take/release buffer ownership intel_buf_set_ownership() can be used.
Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
Cc: Dominik Grzegorzek <dominik.grzegorzek@intel.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'lib/intel_batchbuffer.c')
0 files changed, 0 insertions, 0 deletions