/Linux-v4.19/drivers/gpu/drm/scheduler/ |
D | sched_fence.c | 51 int ret = dma_fence_signal(&fence->scheduled); in drm_sched_fence_scheduled() 54 DMA_FENCE_TRACE(&fence->scheduled, in drm_sched_fence_scheduled() 57 DMA_FENCE_TRACE(&fence->scheduled, in drm_sched_fence_scheduled() 126 dma_fence_put(&fence->scheduled); in drm_sched_fence_release_finished() 144 return container_of(f, struct drm_sched_fence, scheduled); in to_drm_sched_fence() 168 dma_fence_init(&fence->scheduled, &drm_sched_fence_ops_scheduled, in drm_sched_fence_create()
|
D | gpu_scheduler.c | 460 fence = dma_fence_get(&s_fence->scheduled); in drm_sched_entity_add_dependency_cb() 646 if (bad->s_fence->scheduled.context == entity->fence_context) { in drm_sched_hw_job_reset() 686 guilty_context = s_job->s_fence->scheduled.context; in drm_sched_job_recovery() 689 if (found_guilty && s_job->s_fence->scheduled.context == guilty_context) in drm_sched_job_recovery()
|
/Linux-v4.19/Documentation/powerpc/ |
D | pmu-ebb.txt | 43 user process. This means once an EBB event is scheduled on the PMU, no non-EBB 55 first will be scheduled and the other will be put in error state. See the 83 userspace is able to reliably determine which PMC the event is scheduled on. 94 guarantee that it has been scheduled on the PMU. To ensure that the EBB event 95 has been scheduled on the PMU, you must perform a read() on the event. If the 96 read() returns EOF, then the event has not been scheduled and EBBs are not
|
/Linux-v4.19/net/sctp/ |
D | stream_sched_prio.c | 107 bool scheduled = false; in sctp_sched_prio_unsched() local 113 scheduled = true; in sctp_sched_prio_unsched() 129 return scheduled; in sctp_sched_prio_unsched()
|
/Linux-v4.19/fs/btrfs/ |
D | reada.c | 60 int scheduled; member 109 re->scheduled = 0; in __readahead_hook() 684 if (re->scheduled || list_empty(&re->extctl)) { in reada_start_machine_dev() 689 re->scheduled = 1; in reada_start_machine_dev() 841 list_empty(&re->extctl), re->scheduled); in dump_devs() 868 if (!re->scheduled) { in dump_devs() 874 list_empty(&re->extctl), re->scheduled); in dump_devs()
|
/Linux-v4.19/kernel/ |
D | workqueue_internal.h | 34 struct list_head scheduled; /* L: scheduled works */ member
|
D | workqueue.c | 1707 INIT_LIST_HEAD(&worker->scheduled); in alloc_worker() 1858 WARN_ON(!list_empty(&worker->scheduled)) || in destroy_worker() 2079 move_linked_works(work, &collision->scheduled, NULL); in process_one_work() 2209 while (!list_empty(&worker->scheduled)) { in process_scheduled_works() 2210 struct work_struct *work = list_first_entry(&worker->scheduled, in process_scheduled_works() 2276 WARN_ON_ONCE(!list_empty(&worker->scheduled)); in worker_thread() 2297 if (unlikely(!list_empty(&worker->scheduled))) in worker_thread() 2300 move_linked_works(work, &worker->scheduled, NULL); in worker_thread() 2346 struct list_head *scheduled = &rescuer->scheduled; in rescuer_thread() local 2392 WARN_ON_ONCE(!list_empty(scheduled)); in rescuer_thread() [all …]
|
/Linux-v4.19/Documentation/ABI/removed/ |
D | devfs | 2 Date: July 2005 (scheduled), finally removed in kernel v2.6.18
|
D | sysfs-class-rfkill | 11 This file was scheduled to be removed in 2012, and was removed
|
D | raw1394 | 2 Date: May 2010 (scheduled), finally removed in kernel v2.6.37
|
D | dv1394 | 2 Date: May 2010 (scheduled), finally removed in kernel v2.6.37
|
D | video1394 | 2 Date: May 2010 (scheduled), finally removed in kernel v2.6.37
|
/Linux-v4.19/drivers/gpu/drm/amd/amdgpu/ |
D | amdgpu_sync.c | 281 if (dma_fence_is_signaled(&s_fence->scheduled)) in amdgpu_sync_peek_fence() 284 return &s_fence->scheduled; in amdgpu_sync_peek_fence()
|
D | amdgpu_ib.c | 142 fence_ctx = job->base.s_fence->scheduled.context; in amdgpu_ib_schedule()
|
/Linux-v4.19/net/dsa/ |
D | Kconfig | 26 This feature is scheduled for removal in 4.17.
|
/Linux-v4.19/Documentation/vm/ |
D | active_mm.rst | 54 anonymous process gets scheduled away, the borrowed address space is 66 gets scheduled away in favour of a real thread, the "zombie" mm gets
|
/Linux-v4.19/include/drm/ |
D | gpu_scheduler.h | 119 struct dma_fence scheduled; member
|
/Linux-v4.19/drivers/scsi/libsas/ |
D | sas_scsi_host.c | 443 int scheduled = 0, tries = 100; in sas_queue_reset() local 453 while (!scheduled && tries--) { in sas_queue_reset() 457 scheduled = 1; in sas_queue_reset() 470 if (scheduled) in sas_queue_reset()
|
/Linux-v4.19/Documentation/media/v4l-drivers/ |
D | pxa_camera.rst | 168 - Videobuffer3 capture is not scheduled on DMA chain (as it stopped !!!) 184 and Videobuffer3 is scheduled on DMA chain.
|
/Linux-v4.19/drivers/soc/fsl/qbman/ |
D | Kconfig | 64 across a series of FQs scheduled to different portals (and cpus), with
|
/Linux-v4.19/drivers/rtc/ |
D | interface.c | 407 time64_t now, scheduled; in __rtc_set_alarm() local 414 scheduled = rtc_tm_to_time64(&alarm->time); in __rtc_set_alarm() 421 if (scheduled <= now) in __rtc_set_alarm()
|
/Linux-v4.19/Documentation/driver-api/dmaengine/ |
D | pxa_dma.rst | 122 is raised. Upon this interrupt, a tasklet is scheduled for the physical 133 be raised, and the tasklet will be scheduled once again, having a new
|
/Linux-v4.19/Documentation/ABI/stable/ |
D | sysfs-class-rfkill | 49 This file was scheduled to be removed in 2014, but due to its
|
/Linux-v4.19/Documentation/scheduler/ |
D | sched-deadline.txt | 59 scheduled using EDF[1] on these scheduling deadlines (the task with the 109 and cannot be scheduled until its scheduling deadline. The "replenishment 379 (Task_1 is scheduled as soon as it is released, and finishes just in time 380 to respect its deadline; Task_2 is scheduled immediately after Task_1, hence 418 result, Task_1 can be scheduled only at time t + e, and will finish at 462 In order to do this, a task must be scheduled by setting: 597 runtime at each instance, and that is scheduled according to the urgency of 718 The above creates 2 threads. The first one, scheduled by SCHED_DEADLINE, 719 executes for 10ms every 100ms. The second one, scheduled at SCHED_FIFO
|
/Linux-v4.19/sound/ |
D | Kconfig | 30 /proc/devices. sound-slot/service-* module aliases are scheduled
|