Home
last modified time | relevance | path

Searched refs:semaphores (Results 1 – 24 of 24) sorted by relevance

/linux-4.4.14/drivers/gpu/drm/i915/
Di915_params.c30 .semaphores = -1,
70 module_param_named_unsafe(semaphores, i915.semaphores, int, 0400);
71 MODULE_PARM_DESC(semaphores,
Di915_drv.c556 if (i915.semaphores >= 0) in i915_semaphore_is_enabled()
557 return i915.semaphores; in i915_semaphore_is_enabled()
Di915_drv.h1159 struct intel_rps_client semaphores, mmioflips; member
2649 int semaphores; member
Dintel_ringbuffer.c2660 i915.semaphores = 0; in intel_init_render_ring_buffer()
2667 i915.semaphores = 0; in intel_init_render_ring_buffer()
Di915_debugfs.c2360 dev_priv->rps.semaphores.boosts, in i915_rps_boost_info()
2361 list_empty(&dev_priv->rps.semaphores.link) ? "" : ", active"); in i915_rps_boost_info()
Di915_gem.c3142 &i915->rps.semaphores); in __i915_gem_object_sync()
Dintel_pm.c7338 INIT_LIST_HEAD(&dev_priv->rps.semaphores.link); in intel_pm_setup()
/linux-4.4.14/Documentation/
Dpercpu-rw-semaphore.txt1 Percpu rw semaphores
4 Percpu rw semaphores is a new read-write semaphore design that is
7 The problem with traditional read-write semaphores is that when multiple
Dmemory-barriers.txt1792 (*) semaphores
1793 (*) R/W semaphores
1899 Locks and semaphores may not provide any guarantee of ordering on UP compiled
/linux-4.4.14/drivers/gpu/drm/radeon/
Dradeon_sync.c47 sync->semaphores[i] = NULL; in radeon_sync_create()
169 sync->semaphores[count++] = semaphore; in radeon_sync_rings()
219 radeon_semaphore_free(rdev, &sync->semaphores[i], fence); in radeon_sync_free()
Dradeon.h609 struct radeon_semaphore *semaphores[RADEON_NUM_SYNCS]; member
/linux-4.4.14/drivers/gpu/drm/amd/amdgpu/
Damdgpu_sync.c52 sync->semaphores[i] = NULL; in amdgpu_sync_create()
324 sync->semaphores[count++] = semaphore; in amdgpu_sync_rings()
382 amdgpu_semaphore_free(adev, &sync->semaphores[i], fence); in amdgpu_sync_free()
Damdgpu.h662 struct amdgpu_semaphore *semaphores[AMDGPU_NUM_SYNCS]; member
/linux-4.4.14/drivers/staging/wilc1000/
DTODO6 - replace all semaphores with mutexes or completions
/linux-4.4.14/drivers/media/pci/cx18/
Dcx18-scb.h245 u32 semaphores[8]; /* Semaphores */ member
/linux-4.4.14/Documentation/locking/
Dmutex-design.txt13 behave similarly to binary semaphores, and were introduced in 2006[1]
84 number of workloads. Note that this technique is also used for rw-semaphores.
/linux-4.4.14/Documentation/RCU/
Drcuref.txt13 reader/writer spinlocks or semaphores are straightforward:
DwhatisRCU.txt424 o Use some solid scheme (such as locks or semaphores) to
/linux-4.4.14/Documentation/infiniband/
Dcore_locking.txt106 semaphores that could cause deadlock if a consumer calls back into
/linux-4.4.14/Documentation/scsi/
DChangeLog.ips26 4.80.14 - Take all semaphores off stack
/linux-4.4.14/arch/arc/
DKconfig190 hardware semaphores, shared memory,....
/linux-4.4.14/Documentation/PCI/
Dpci-error-recovery.txt132 to complete; it can take semaphores, schedule, etc... everything but
/linux-4.4.14/Documentation/sound/alsa/
DALSA-Configuration.txt1128 semaphores (e.g. on some ASUS laptops)
/linux-4.4.14/
DCREDITS3111 D: shm fs, SYSV semaphores, af_unix