Searched refs:eventfd (Results 1 – 25 of 30) sorted by relevance
12
| /qemu/backends/ |
| H A D | cryptodev-lkcf.c | 98 int eventfd; member
116 eventfd_read(lkcf->eventfd, &nevent); in cryptodev_lkcf_handle_response()
220 lkcf->eventfd = eventfd(0, 0); in cryptodev_lkcf_init()
221 if (lkcf->eventfd < 0) { in cryptodev_lkcf_init()
247 lkcf->eventfd, cryptodev_lkcf_handle_response, NULL, lkcf); in cryptodev_lkcf_init()
264 close(lkcf->eventfd); in cryptodev_lkcf_cleanup()
442 eventfd_write(task->lkcf->eventfd, 1); in cryptodev_lkcf_execute_task()
|
| /qemu/util/ |
| H A D | event_notifier-posix.c | 41 ret = eventfd(0, EFD_NONBLOCK | EFD_CLOEXEC); in event_notifier_init()
|
| /qemu/subprojects/libvduse/ |
| H A D | libvduse.c | 915 fd = eventfd(0, EFD_NONBLOCK | EFD_CLOEXEC); in vduse_queue_enable()
945 struct vduse_vq_eventfd eventfd; in vduse_queue_disable() local
953 eventfd.index = vq->index; in vduse_queue_disable()
954 eventfd.fd = VDUSE_EVENTFD_DEASSIGN; in vduse_queue_disable()
955 ioctl(dev->fd, VDUSE_VQ_SETUP_KICKFD, &eventfd); in vduse_queue_disable()
|
| /qemu/docs/specs/ |
| H A D | ivshmem-spec.rst | 130 When configured for interrupts, the peers share eventfd objects in
142 - creates eventfd file descriptors for the interrupt vectors,
233 An ivshmem device configured for interrupts receives eventfd file
|
| /qemu/docs/system/devices/ |
| H A D | ivshmem-flat.rst | 21 distribute the proper shared memory file descriptor and the eventfd(s) to notify
|
| /qemu/linux-user/mips/ |
| H A D | syscall-args-o32.c.inc | 320 [ 319] = 1, /* eventfd */
|
| H A D | syscall_o32.tbl | 333 319 o32 eventfd sys_eventfd
|
| /qemu/hw/misc/ |
| H A D | ivshmem-pci.c | 354 int eventfd = event_notifier_get_fd(n); in watch_vector_notifier() local
359 qemu_set_fd_handler(eventfd, ivshmem_vector_notify, in watch_vector_notifier()
|
| /qemu/docs/devel/ |
| H A D | multi-process.rst | 133 virtio code by setting up an eventfd file descriptor that the vhost
143 The QEMU virtio setup code configures the KVM driver with an eventfd
144 that triggers the device interrupt in the guest when the eventfd is
593 from KVM. The issue with the eventfd mechanism used by vhost user is
883 an *eventfd* is created, a virtual interrupt is allocated by
885 the eventfd with ``kvm_irqchip_add_irqfd_notifier()``.
|
| /qemu/hw/i386/kvm/ |
| H A D | xen_evtchn.c | 592 ha.u.evtchn.deliver.eventfd.port = 0; in assign_kernel_eventfd()
593 ha.u.evtchn.deliver.eventfd.fd = fd; in assign_kernel_eventfd()
2034 xc->fd = eventfd(0, EFD_CLOEXEC); in xen_be_evtchn_open()
|
| /qemu/linux-user/mips64/ |
| H A D | syscall_n64.tbl | 289 278 n64 eventfd sys_eventfd
|
| H A D | syscall_n32.tbl | 293 282 n32 eventfd sys_eventfd
|
| /qemu/linux-headers/asm-x86/ |
| H A D | kvm.h | 607 } eventfd; member
|
| /qemu/linux-user/x86_64/ |
| H A D | syscall_64.tbl | 296 284 common eventfd sys_eventfd
|
| /qemu/linux-user/xtensa/ |
| H A D | syscall.tbl | 329 306 common eventfd sys_eventfd
|
| /qemu/linux-user/hppa/ |
| H A D | syscall.tbl | 344 304 common eventfd sys_eventfd
|
| /qemu/linux-user/sh4/ |
| H A D | syscall.tbl | 333 323 common eventfd sys_eventfd
|
| /qemu/linux-user/microblaze/ |
| H A D | syscall.tbl | 333 323 common eventfd sys_eventfd
|
| /qemu/linux-user/m68k/ |
| H A D | syscall.tbl | 329 319 common eventfd sys_eventfd
|
| /qemu/linux-user/alpha/ |
| H A D | syscall.tbl | 409 478 common eventfd sys_eventfd
|
| /qemu/linux-user/arm/ |
| H A D | syscall.tbl | 369 351 common eventfd sys_eventfd
|
| /qemu/linux-user/i386/ |
| H A D | syscall_32.tbl | 338 323 i386 eventfd sys_eventfd
|
| /qemu/linux-user/sparc/ |
| H A D | syscall.tbl | 380 313 common eventfd sys_eventfd
|
| /qemu/linux-user/s390x/ |
| H A D | syscall.tbl | 328 318 common eventfd sys_eventfd sys_eventfd
|
| /qemu/linux-user/ppc/ |
| H A D | syscall.tbl | 400 307 common eventfd sys_eventfd
|
12