Searched refs:eventfds (Results 1 – 4 of 4) sorted by relevance
79 EventNotifier *eventfds; member259 EventNotifier *n = &s->peers[s->vm_id].eventfds[vector]; in ivshmem_vector_notify()279 EventNotifier *n = &s->peers[s->vm_id].eventfds[vector]; in ivshmem_vector_unmask()308 EventNotifier *n = &s->peers[s->vm_id].eventfds[vector]; in ivshmem_vector_mask()370 &s->peers[posn].eventfds[i]); in ivshmem_add_eventfd()380 &s->peers[posn].eventfds[i]); in ivshmem_del_eventfd()399 event_notifier_cleanup(&s->peers[posn].eventfds[i]); in close_peer_eventfds()402 g_free(s->peers[posn].eventfds); in close_peer_eventfds()418 s->peers[i].eventfds = g_new0(EventNotifier, s->vectors); in resize_peers()447 EventNotifier *n = &s->peers[s->vm_id].eventfds[vector]; in setup_interrupt()[all …]
597 interrupt happens. Users could set eventfds to driver via598 ioctl (DFL_FPGA_*_SET_IRQ), and then poll/select on these eventfds waiting for
236 /* Setup IRQs... eventfds, VFIO_DEVICE_SET_IRQS */
835 application does, where the QEMU process sets up *eventfds* that cause