| /Linux-v5.4/drivers/infiniband/sw/rxe/ |
| D | rxe_task.c | 124 task->destroyed = false; in rxe_init_task()
143 task->destroyed = true; in rxe_cleanup_task()
156 if (task->destroyed) in rxe_run_task()
|
| D | rxe_task.h | 57 bool destroyed; member
|
| /Linux-v5.4/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_vce.c | 714 uint32_t destroyed = 0; in amdgpu_vce_ring_parse_cs() local
814 if (destroyed & (1 << session_idx)) { in amdgpu_vce_ring_parse_cs()
815 destroyed &= ~(1 << session_idx); in amdgpu_vce_ring_parse_cs()
866 destroyed |= 1 << session_idx; in amdgpu_vce_ring_parse_cs()
926 tmp = destroyed; in amdgpu_vce_ring_parse_cs()
949 uint32_t destroyed = 0; in amdgpu_vce_ring_parse_cs_vm() local
978 if (destroyed & (1 << session_idx)) { in amdgpu_vce_ring_parse_cs_vm()
979 destroyed &= ~(1 << session_idx); in amdgpu_vce_ring_parse_cs_vm()
991 destroyed |= 1 << session_idx; in amdgpu_vce_ring_parse_cs_vm()
1015 tmp = destroyed; in amdgpu_vce_ring_parse_cs_vm()
|
| /Linux-v5.4/Documentation/core-api/ |
| D | debug-objects.rst | 19 - Usage of freed/destroyed objects
75 active and destroyed objects. When debugobjects detects an error, then
98 active and destroyed objects. When debugobjects detects an error, then
122 active and destroyed objects. When debugobjects detects an error, then
147 or destroyed objects.
155 This function is called to mark an object destroyed. This is useful to
161 the object can be destroyed. Destruction is not allowed for active and
162 destroyed objects. When debugobjects detects an error, then it calls the
|
| D | genalloc.rst | 37 pool when the given device is destroyed.
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-dev | 17 dynamically created and destroyed as devices enter and
|
| D | sysfs-bus-fcoe | 30 discovery and login. The FCoE Controller is destroyed by
|
| /Linux-v5.4/drivers/gpu/drm/radeon/ |
| D | radeon_vce.c | 560 bool destroyed = false, created = false, allocated = false; in radeon_vce_cs_parse() local
575 if (destroyed) { in radeon_vce_cs_parse()
628 destroyed = true; in radeon_vce_cs_parse()
674 if ((!r && destroyed) || (r && allocated)) { in radeon_vce_cs_parse()
|
| /Linux-v5.4/fs/nilfs2/ |
| D | Kconfig | 9 destroyed just a few seconds ago. Since this file system can keep
|
| /Linux-v5.4/arch/m68k/fpsp040/ |
| D | x_store.S | 106 | a0 -> destroyed
107 | a1 -> destroyed
|
| /Linux-v5.4/drivers/infiniband/hw/i40iw/ |
| D | i40iw_verbs.h | 162 u8 destroyed:1; member
|
| /Linux-v5.4/drivers/infiniband/hw/qedr/ |
| D | qedr.h | 293 u8 destroyed; member
441 bool destroyed; member
|
| /Linux-v5.4/Documentation/i2c/ |
| D | instantiating-devices.rst | 51 The devices will be automatically unbound and destroyed when the I2C bus
187 destroyed automatically when the driver which detected them is removed,
188 or when the underlying I2C bus is itself destroyed, whichever happens
|
| /Linux-v5.4/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-handle.txt | 38 the last reference is removed, the _tep_ is destroyed, and all resources that
|
| /Linux-v5.4/drivers/scsi/isci/ |
| D | remote_device.c | 1414 int destroyed; in isci_remote_device_resume_from_abort() local
1424 destroyed = sci_remote_node_context_is_being_destroyed(&idev->rnc); in isci_remote_device_resume_from_abort()
1425 if (!destroyed) in isci_remote_device_resume_from_abort()
1430 if (!destroyed && (status == SCI_SUCCESS)) in isci_remote_device_resume_from_abort()
|
| /Linux-v5.4/Documentation/filesystems/configfs/ |
| D | configfs.txt | 24 destroyed in kernel, the kernel controls the lifecycle of the sysfs
28 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
76 When an item needs to be destroyed, remove it with rmdir(2). An
77 item cannot be destroyed if any other item has a link to it (via
122 Items are created and destroyed inside a config_group. A group is a
|
| /Linux-v5.4/Documentation/x86/ |
| D | tlb.rst | 13 destroyed and must be refilled later, at some cost.
|
| /Linux-v5.4/Documentation/admin-guide/cgroup-v1/ |
| D | rdma.rst | 75 Resource pool is destroyed if all the resource limits are set to max and
|
| /Linux-v5.4/Documentation/RCU/ |
| D | rcu.rst | 8 item being destroyed, and one that actually carries out the destruction.
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | dlmfs.txt | 57 destroyed and locks within them accessed.
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 80 the tests are run will be destroyed. This is to prevent inaccurate results
|
| /Linux-v5.4/scripts/ |
| D | spelling.txt | 425 destoried||destroyed
427 destoryed||destroyed
429 destroied||destroyed
|
| /Linux-v5.4/Documentation/livepatch/ |
| D | shadow-vars.rst | 110 If parent data structures are frequently created and destroyed, it may
|
| /Linux-v5.4/Documentation/gpu/ |
| D | tegra.rst | 45 the subsystem specific bits are torn down and the clients destroyed in turn.
|
| /Linux-v5.4/Documentation/driver-api/driver-model/ |
| D | devres.rst | 208 when it is released or destroyed (removed and freed) - no reference
|
