Home
last modified time | relevance | path

Searched refs:attachments (Results 1 – 23 of 23) sorted by relevance

/openbmc/linux/tools/bpf/bpftool/Documentation/
H A Dbpftool-net.rst7 tool for inspection of networking related bpf prog attachments
38 List bpf program attachments in the kernel networking subsystem.
40 Currently, device driver xdp attachments, tcx and old-style tc
41 classifier/action attachments, flow_dissector as well as netfilter
42 attachments are implemented, i.e., for
50 users can use **bpftool cgroup** to dump cgroup attachments.
54 The current output will start with all xdp program attachments, followed by
55 all tcx, then tc class/qdisc bpf program attachments, then flow_dissector
H A Dbpftool-perf.rst7 tool for inspection of perf related bpf prog attachments
/openbmc/linux/drivers/dma-buf/heaps/
H A Dcma_heap.c33 struct list_head attachments; member
77 list_add(&a->list, &buffer->attachments); in cma_heap_attach()
132 list_for_each_entry(a, &buffer->attachments, list) { in cma_heap_dma_buf_begin_cpu_access()
153 list_for_each_entry(a, &buffer->attachments, list) { in cma_heap_dma_buf_end_cpu_access()
296 INIT_LIST_HEAD(&buffer->attachments); in cma_heap_allocate()
H A Dsystem_heap.c28 struct list_head attachments; member
107 list_add(&a->list, &buffer->attachments); in system_heap_attach()
164 list_for_each_entry(a, &buffer->attachments, list) { in system_heap_dma_buf_begin_cpu_access()
185 list_for_each_entry(a, &buffer->attachments, list) { in system_heap_dma_buf_end_cpu_access()
354 INIT_LIST_HEAD(&buffer->attachments); in system_heap_allocate()
/openbmc/linux/drivers/gpu/drm/amd/amdgpu/
H A Damdgpu_amdkfd_gpuvm.c81 list_for_each_entry(entry, &mem->attachments, list) in kfd_mem_is_attached()
932 list_add(&attachment[i]->list, &mem->attachments); in kfd_mem_attach()
1146 list_for_each_entry(entry, &mem->attachments, list) { in reserve_bo_and_cond_vms()
1705 INIT_LIST_HEAD(&(*mem)->attachments); in amdgpu_amdkfd_gpuvm_alloc_memory_of_gpu()
1868 list_for_each_entry_safe(entry, tmp, &mem->attachments, list) { in amdgpu_amdkfd_gpuvm_free_memory_of_gpu()
2003 list_for_each_entry(entry, &mem->attachments, list) { in amdgpu_amdkfd_gpuvm_map_memory_to_gpu()
2059 list_for_each_entry(entry, &mem->attachments, list) { in amdgpu_amdkfd_gpuvm_dmaunmap_mem()
2106 list_for_each_entry(entry, &mem->attachments, list) { in amdgpu_amdkfd_gpuvm_unmap_memory_from_gpu()
2335 INIT_LIST_HEAD(&(*mem)->attachments); in amdgpu_amdkfd_gpuvm_import_dmabuf()
2594 list_for_each_entry(attachment, &mem->attachments, list) { in validate_invalid_user_pages()
[all …]
H A Damdgpu_amdkfd.h72 struct list_head attachments; member
H A Damdgpu_cs.c802 list_empty(&bo->tbo.base.dma_buf->attachments))) { in amdgpu_cs_bo_validate()
/openbmc/linux/Documentation/process/
H A Demail-clients.rst23 attachments, but then the attachments should have content-type
24 ``text/plain``. However, attachments are generally frowned upon because
152 You can safely GPG sign attachments, but inlined text is preferred for
156 If you absolutely must send patches as attachments instead of inlining
266 - Works well for inlining text (or using attachments).
H A Dsecurity-bugs.rst29 Please send plain text emails without attachments where possible.
31 issue if all the details are hidden away in attachments. Think of it like a
H A D5.Posting.rst301 attachments; that makes it much harder for reviewers to quote sections of
H A Dhowto.rst419 attachments or compressed patches; they may want to comment on
H A Dsubmitting-patches.rst280 No MIME, no links, no compression, no attachments. Just plain text
/openbmc/linux/drivers/dma-buf/
H A Ddma-buf.c84 WARN_ON(!list_empty(&dmabuf->attachments)); in dma_buf_release()
658 INIT_LIST_HEAD(&dmabuf->attachments); in dma_buf_export()
919 list_add(&attach->node, &dmabuf->attachments); in dma_buf_dynamic_attach()
1264 list_for_each_entry(attach, &dmabuf->attachments, node) in dma_buf_move_notify()
1645 list_for_each_entry(attach_obj, &buf_obj->attachments, node) { in dma_buf_debug_show()
/openbmc/linux/include/linux/
H A Ddma-buf.h324 struct list_head attachments; member
/openbmc/linux/Documentation/trace/coresight/
H A Dcoresight-ect.rst43 no programmed trigger/channel attachments, so will not affect the system
/openbmc/linux/drivers/misc/
H A Dfastrpc.c203 struct list_head attachments; member
410 INIT_LIST_HEAD(&buf->attachments); in __fastrpc_buf_alloc()
704 list_add(&a->node, &buffer->attachments); in fastrpc_dma_buf_attach()
/openbmc/qemu/docs/devel/
H A Dsubmitting-a-patch.rst236 attachments can be used as a last resort on a first-time submission.
285 Do not put patches in attachments.
/openbmc/linux/Documentation/translations/sp_SP/process/
H A Demail-clients.rst164 You can safely GPG sign attachments, but inlined text is preferred for
/openbmc/linux/Documentation/arch/s390/
H A Dvfio-ccw.rst69 different peripheral attachments like disk devices (aka. DASDs), tapes,
H A Dcds.rst118 peripheral attachments like disk devices (aka. DASDs), tapes, communication
/openbmc/openbmc/poky/documentation/contributor-guide/
H A Dsubmit-changes.rst377 client. It will also properly include your patches as *inline attachments*,
380 attachments, reviewers wouldn't be able to quote specific sections of your
/openbmc/linux/Documentation/virt/uml/
H A Duser_mode_linux_howto_v2.rst1088 Note - the list does not accept HTML or attachments, all emails must
/openbmc/u-boot/
H A DREADME4963 We prefer patches as plain text. MIME attachments are discouraged,
4964 and compressed attachments must not be used.