/linux/drivers/gpu/drm/scheduler/ |
A D | sched_fence.c | 53 dma_fence_signal(&fence->scheduled); in drm_sched_fence_scheduled() 123 dma_fence_put(&fence->scheduled); in drm_sched_fence_release_finished() 141 return container_of(f, struct drm_sched_fence, scheduled); in to_drm_sched_fence() 172 dma_fence_init(&fence->scheduled, &drm_sched_fence_ops_scheduled, in drm_sched_fence_init()
|
A D | sched_main.c | 545 guilty_context = s_job->s_fence->scheduled.context; in drm_sched_resubmit_jobs_ext() 548 if (found_guilty && s_job->s_fence->scheduled.context == guilty_context) in drm_sched_resubmit_jobs_ext() 836 next->s_fence->scheduled.timestamp = in drm_sched_get_cleanup_job() 1103 if (bad->s_fence->scheduled.context == in drm_sched_increase_karma_ext()
|
/linux/Documentation/powerpc/ |
A D | pmu-ebb.rst | 44 user process. This means once an EBB event is scheduled on the PMU, no non-EBB 56 first will be scheduled and the other will be put in error state. See the 84 userspace is able to reliably determine which PMC the event is scheduled on. 95 guarantee that it has been scheduled on the PMU. To ensure that the EBB event 96 has been scheduled on the PMU, you must perform a read() on the event. If the 97 read() returns EOF, then the event has not been scheduled and EBBs are not
|
/linux/arch/s390/pci/ |
A D | pci_irq.c | 179 atomic_t scheduled; member 185 atomic_t *scheduled = data; in zpci_handle_remote_irq() local 189 } while (atomic_dec_return(scheduled)); in zpci_handle_remote_irq() 211 if (atomic_inc_return(&cpu_data->scheduled) > 1) in zpci_handle_fallback_irq() 214 INIT_CSD(&cpu_data->csd, zpci_handle_remote_irq, &cpu_data->scheduled); in zpci_handle_fallback_irq()
|
/linux/net/sctp/ |
A D | stream_sched_prio.c | 92 bool scheduled = false; in sctp_sched_prio_unsched() local 98 scheduled = true; in sctp_sched_prio_unsched() 114 return scheduled; in sctp_sched_prio_unsched()
|
/linux/fs/btrfs/ |
A D | reada.c | 62 int scheduled; member 113 re->scheduled = 0; in __readahead_hook() 734 if (re->scheduled || list_empty(&re->extctl)) { in reada_start_machine_dev() 739 re->scheduled = 1; in reada_start_machine_dev() 902 list_empty(&re->extctl), re->scheduled); in dump_devs() 929 if (!re->scheduled) { in dump_devs() 935 list_empty(&re->extctl), re->scheduled); in dump_devs()
|
/linux/Documentation/admin-guide/hw-vuln/ |
A D | l1d_flush.rst | 35 performed when the task is scheduled out and the incoming task belongs to a 68 requested L1D flushing is scheduled on a SMT-enabled core the kernel sends
|
A D | core-scheduling.rst | 35 Using this feature, userspace defines groups of tasks that can be co-scheduled 122 tasks selected to be scheduled are of the highest priority in a core. However, 128 by the scheduler (idle thread is scheduled to run). 224 - Gang scheduling: Requirements for a group of tasks that needs to be scheduled
|
/linux/kernel/ |
A D | workqueue_internal.h | 35 struct list_head scheduled; /* L: scheduled works */ member
|
A D | workqueue.c | 1852 INIT_LIST_HEAD(&worker->scheduled); in alloc_worker() 2002 WARN_ON(!list_empty(&worker->scheduled)) || in destroy_worker() 2358 while (!list_empty(&worker->scheduled)) { in process_scheduled_works() 2425 WARN_ON_ONCE(!list_empty(&worker->scheduled)); in worker_thread() 2446 if (unlikely(!list_empty(&worker->scheduled))) in worker_thread() 2449 move_linked_works(work, &worker->scheduled, NULL); in worker_thread() 2495 struct list_head *scheduled = &rescuer->scheduled; in rescuer_thread() local 2541 WARN_ON_ONCE(!list_empty(scheduled)); in rescuer_thread() 2546 move_linked_works(work, scheduled, &n); in rescuer_thread() 2551 if (!list_empty(scheduled)) { in rescuer_thread() [all …]
|
/linux/Documentation/ABI/removed/ |
A D | devfs | 2 Date: July 2005 (scheduled), finally removed in kernel v2.6.18
|
A D | sysfs-class-rfkill | 11 This file was scheduled to be removed in 2012, and was removed
|
A D | dv1394 | 2 Date: May 2010 (scheduled), finally removed in kernel v2.6.37
|
A D | raw1394 | 2 Date: May 2010 (scheduled), finally removed in kernel v2.6.37
|
A D | video1394 | 2 Date: May 2010 (scheduled), finally removed in kernel v2.6.37
|
/linux/drivers/gpu/drm/amd/amdgpu/ |
A D | amdgpu_sync.c | 326 if (dma_fence_is_signaled(&s_fence->scheduled)) in amdgpu_sync_peek_fence() 329 return &s_fence->scheduled; in amdgpu_sync_peek_fence()
|
/linux/kernel/time/ |
A D | posix-cpu-timers.c | 1174 p->posix_cputimers_work.scheduled = false; in clear_posix_cputimers_work() 1194 return tsk->posix_cputimers_work.scheduled; in posix_cpu_timers_work_scheduled() 1199 if (WARN_ON_ONCE(tsk->posix_cputimers_work.scheduled)) in __run_posix_cpu_timers() 1203 tsk->posix_cputimers_work.scheduled = true; in __run_posix_cpu_timers() 1218 tsk->posix_cputimers_work.scheduled = false; in posix_cpu_timers_enable_work() 1239 tsk->posix_cputimers_work.scheduled = false; in posix_cpu_timers_enable_work()
|
/linux/tools/lib/traceevent/Documentation/ |
A D | libtraceevent-event_print.txt | 42 may need to be scheduled in. 55 On preemptible kernels (where the task can be scheduled
|
/linux/drivers/infiniband/hw/hfi1/ |
A D | rc.h | 53 u8 *prev_ack, bool *scheduled);
|
/linux/Documentation/vm/ |
A 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/drivers/scsi/libsas/ |
A D | sas_scsi_host.c | 423 int scheduled = 0, tries = 100; in sas_queue_reset() local 433 while (!scheduled && tries--) { in sas_queue_reset() 437 scheduled = 1; in sas_queue_reset() 450 if (scheduled) in sas_queue_reset()
|
/linux/Documentation/driver-api/media/drivers/ |
A D | pxa_camera.rst | 170 - Videobuffer3 capture is not scheduled on DMA chain (as it stopped !!!) 186 and Videobuffer3 is scheduled on DMA chain.
|
/linux/include/linux/ |
A D | posix-timers.h | 143 unsigned int scheduled; member
|
/linux/drivers/rtc/ |
A D | interface.c | 412 time64_t now, scheduled; in __rtc_set_alarm() local 419 scheduled = rtc_tm_to_time64(&alarm->time); in __rtc_set_alarm() 427 if (scheduled <= now) in __rtc_set_alarm()
|
/linux/drivers/soc/fsl/qbman/ |
A D | Kconfig | 65 across a series of FQs scheduled to different portals (and cpus), with
|