Home
last modified time | relevance | path

Searched refs:destroyed (Results 1 – 25 of 76) sorted by relevance

1234

/kernel/linux/linux-5.10/drivers/infiniband/sw/rxe/
Drxe_task.c105 task->destroyed = false; in rxe_init_task()
124 task->destroyed = true; in rxe_cleanup_task()
137 if (task->destroyed) in rxe_run_task()
Drxe_task.h30 bool destroyed; member
/kernel/linux/linux-5.10/drivers/gpu/drm/amd/amdgpu/
Damdgpu_vce.c724 uint32_t destroyed = 0; in amdgpu_vce_ring_parse_cs() local
824 if (destroyed & (1 << session_idx)) { in amdgpu_vce_ring_parse_cs()
825 destroyed &= ~(1 << session_idx); in amdgpu_vce_ring_parse_cs()
876 destroyed |= 1 << session_idx; in amdgpu_vce_ring_parse_cs()
936 tmp = destroyed; in amdgpu_vce_ring_parse_cs()
959 uint32_t destroyed = 0; in amdgpu_vce_ring_parse_cs_vm() local
988 if (destroyed & (1 << session_idx)) { in amdgpu_vce_ring_parse_cs_vm()
989 destroyed &= ~(1 << session_idx); in amdgpu_vce_ring_parse_cs_vm()
1001 destroyed |= 1 << session_idx; in amdgpu_vce_ring_parse_cs_vm()
1025 tmp = destroyed; in amdgpu_vce_ring_parse_cs_vm()
/kernel/linux/linux-5.10/Documentation/core-api/
Ddebug-objects.rst19 - 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
Dgenalloc.rst37 pool when the given device is destroyed.
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-dev18 dynamically created and destroyed as devices enter and
Dsysfs-bus-fcoe33 discovery and login. The FCoE Controller is destroyed by
/kernel/linux/linux-5.10/drivers/gpu/drm/radeon/
Dradeon_vce.c560 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()
/kernel/linux/linux-5.10/Documentation/networking/
Dl2tp.rst157 CONN_ID Y Identifies the tunnel id to be destroyed.
212 to be destroyed.
213 SESSION_ID Y Identifies the session id to be destroyed.
429 tunnel management socket is connected and is destroyed when the
434 are set using setsockopt. The L2TP session instance is destroyed
524 tunnel and all of its sessions must be closed and destroyed. Since the
533 eventually destroyed, it's sk_destruct finally frees the L2TP tunnel
605 L2TP Ethernet sessions are created and destroyed by netlink request,
606 or are destroyed when the tunnel is destroyed. Unlike PPP sessions,
/kernel/linux/linux-5.10/fs/nilfs2/
DKconfig9 destroyed just a few seconds ago. Since this file system can keep
/kernel/linux/linux-5.10/arch/m68k/fpsp040/
Dx_store.S106 | a0 -> destroyed
107 | a1 -> destroyed
/kernel/linux/linux-5.10/drivers/infiniband/hw/i40iw/
Di40iw_verbs.h161 u8 destroyed:1; member
/kernel/linux/linux-5.10/Documentation/i2c/
Dinstantiating-devices.rst25 unbound and destroyed when the I2C bus they sit on goes away (if ever).
198 destroyed automatically when the driver which detected them is removed,
199 or when the underlying I2C bus is itself destroyed, whichever happens
/kernel/linux/linux-5.10/tools/lib/traceevent/Documentation/
Dlibtraceevent-handle.txt38 the last reference is removed, the _tep_ is destroyed, and all resources that
/kernel/linux/linux-5.10/drivers/scsi/isci/
Dremote_device.c1414 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()
/kernel/linux/linux-5.10/Documentation/admin-guide/gpio/
Dgpio-aggregator.rst25 Aggregated GPIO controllers are instantiated and destroyed by writing to
/kernel/linux/linux-5.10/Documentation/filesystems/
Dconfigfs.rst26 destroyed in kernel, the kernel controls the lifecycle of the sysfs
30 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
79 When an item needs to be destroyed, remove it with rmdir(2). An
80 item cannot be destroyed if any other item has a link to it (via
127 Items are created and destroyed inside a config_group. A group is a
Ddlmfs.rst62 destroyed and locks within them accessed.
/kernel/linux/linux-5.10/Documentation/filesystems/spufs/
Dspu_create.rst36 descriptor is closed, the logical SPU context is destroyed.
/kernel/linux/linux-5.10/Documentation/x86/
Dtlb.rst13 destroyed and must be refilled later, at some cost.
/kernel/linux/linux-5.10/Documentation/RCU/
Drcu.rst8 item being destroyed, and one that actually carries out the destruction.
/kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/
Drdma.rst75 Resource pool is destroyed if all the resource limits are set to max and
/kernel/linux/linux-5.10/Documentation/
Dwatch_queue.rst71 or destroyed and the second indicates that some messages have been lost.
113 destroyed to discard any references the watch list holds on the watched
/kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/creating-testcases/
DAddingTestCases.txt80 the tests are run will be destroyed. This is to prevent inaccurate results
/kernel/linux/linux-5.10/drivers/infiniband/hw/qedr/
Dqedr.h303 u8 destroyed; member

1234