Home
last modified time | relevance | path

Searched refs:memory_lock (Results 1 - 8 of 8) sorted by relevance

/kernel/linux/linux-5.10/drivers/vfio/pci/
H A Dvfio_pci_rdwr.c45 down_read(&vdev->memory_lock); \
47 up_read(&vdev->memory_lock); \
55 up_read(&vdev->memory_lock); \
72 down_read(&vdev->memory_lock); \
74 up_read(&vdev->memory_lock); \
82 up_read(&vdev->memory_lock); \
390 if (!down_read_trylock(&vdev->memory_lock)) in vfio_pci_ioeventfd_handler()
393 up_read(&vdev->memory_lock); in vfio_pci_ioeventfd_handler()
401 up_read(&vdev->memory_lock); in vfio_pci_ioeventfd_handler()
H A Dvfio_pci.c1089 up_write(&vdev->memory_lock); in vfio_pci_ioctl()
1273 * We need to get memory_lock for each device, but devices in vfio_pci_ioctl()
1276 * memory_lock. in vfio_pci_ioctl()
1289 ret = down_write_trylock(&tmp->memory_lock); in vfio_pci_ioctl()
1309 up_write(&tmp->memory_lock); in vfio_pci_ioctl()
1465 * The memory_lock semaphore is used by both code paths calling in vfio_pci_zap_and_vma_lock()
1476 * Therefore we can only hold the memory_lock write lock when in vfio_pci_zap_and_vma_lock()
1479 * vma_lock, thus memory_lock is nested under vma_lock. in vfio_pci_zap_and_vma_lock()
1482 * followed by memory_lock read lock, while already holding in vfio_pci_zap_and_vma_lock()
1549 down_write(&vdev->memory_lock); in vfio_pci_zap_and_down_write_memory_lock()
[all...]
H A Dvfio_pci_private.h144 struct rw_semaphore memory_lock; member
H A Dvfio_pci_config.c398 /* Caller should hold memory_lock semaphore */
587 down_write(&vdev->memory_lock); in vfio_basic_config_write()
608 up_write(&vdev->memory_lock); in vfio_basic_config_write()
622 up_write(&vdev->memory_lock); in vfio_basic_config_write()
863 up_write(&vdev->memory_lock); in vfio_exp_config_write()
945 up_write(&vdev->memory_lock); in vfio_af_config_write()
/kernel/linux/linux-6.6/drivers/vfio/pci/
H A Dvfio_pci_rdwr.c45 down_read(&vdev->memory_lock); \
47 up_read(&vdev->memory_lock); \
55 up_read(&vdev->memory_lock); \
72 down_read(&vdev->memory_lock); \
74 up_read(&vdev->memory_lock); \
82 up_read(&vdev->memory_lock); \
392 if (!down_read_trylock(&vdev->memory_lock)) in vfio_pci_ioeventfd_handler()
395 up_read(&vdev->memory_lock); in vfio_pci_ioeventfd_handler()
403 up_read(&vdev->memory_lock); in vfio_pci_ioeventfd_handler()
H A Dvfio_pci_core.c290 * The vdev power related flags are protected with 'memory_lock' in vfio_pci_runtime_pm_entry()
295 up_write(&vdev->memory_lock); in vfio_pci_runtime_pm_entry()
302 up_write(&vdev->memory_lock); in vfio_pci_runtime_pm_entry()
376 * The vdev power related flags are protected with 'memory_lock' in vfio_pci_runtime_pm_exit()
379 down_write(&vdev->memory_lock); in vfio_pci_runtime_pm_exit()
381 up_write(&vdev->memory_lock); in vfio_pci_runtime_pm_exit()
411 down_write(&vdev->memory_lock); in vfio_pci_core_runtime_suspend()
421 up_write(&vdev->memory_lock); in vfio_pci_core_runtime_suspend()
444 down_write(&vdev->memory_lock); in vfio_pci_core_runtime_resume()
449 up_write(&vdev->memory_lock); in vfio_pci_core_runtime_resume()
[all...]
H A Dvfio_pci_config.c399 /* Caller should hold memory_lock semaphore */
591 down_write(&vdev->memory_lock); in vfio_basic_config_write()
612 up_write(&vdev->memory_lock); in vfio_basic_config_write()
626 up_write(&vdev->memory_lock); in vfio_basic_config_write()
709 down_write(&vdev->memory_lock); in vfio_lock_and_set_power_state()
712 up_write(&vdev->memory_lock); in vfio_lock_and_set_power_state()
900 up_write(&vdev->memory_lock); in vfio_exp_config_write()
982 up_write(&vdev->memory_lock); in vfio_af_config_write()
/kernel/linux/linux-6.6/include/linux/
H A Dvfio_pci_core.h98 struct rw_semaphore memory_lock; member

Completed in 16 milliseconds