/qemu/ |
H A D | MAINTAINERS | 4022 F: block/export/virtio-blk-handler.c 4023 F: block/export/virtio-blk-handler.h
|
/qemu/block/export/ |
H A D | meson.build | 4 blockdev_ss.add(files('vhost-user-blk-server.c', 'virtio-blk-handler.c')) 10 blockdev_ss.add(files('vduse-blk.c', 'virtio-blk-handler.c'))
|
H A D | vduse-blk.c | 30 VirtioBlkHandler handler; member 76 VirtioBlkHandler *handler = &vblk_exp->handler; in vduse_blk_virtio_process_req() local 84 in_len = virtio_blk_process_req(handler, in_iov, in vduse_blk_virtio_process_req() 308 vblk_exp->handler.blk = exp->blk; in vduse_blk_exp_create() 309 vblk_exp->handler.serial = g_strdup(vblk_opts->serial ?: ""); in vduse_blk_exp_create() 310 vblk_exp->handler.logical_block_size = logical_block_size; in vduse_blk_exp_create() 311 vblk_exp->handler.writable = opts->writable; in vduse_blk_exp_create() 386 g_free(vblk_exp->handler.serial); in vduse_blk_exp_create() 405 g_free(vblk_exp->handler.serial); in vduse_blk_exp_delete()
|
H A D | vhost-user-blk-server.c | 38 VirtioBlkHandler handler; member 63 VirtioBlkHandler *handler = &vexp->handler; in vu_blk_virtio_process_req() local 70 in_len = virtio_blk_process_req(handler, in_iov, out_iov, in vu_blk_virtio_process_req() 135 if (!vexp->handler.writable) { in vu_blk_get_features() 267 BlockDriverState *bs = blk_bs(vexp->handler.blk); in vu_blk_exp_resize() 347 vexp->handler.blk = exp->blk; in vu_blk_exp_create() 348 vexp->handler.serial = g_strdup("vhost_user_blk"); in vu_blk_exp_create() 349 vexp->handler.logical_block_size = logical_block_size; in vu_blk_exp_create() 350 vexp->handler.writable = opts->writable; in vu_blk_exp_create() 364 g_free(vexp->handler.serial); in vu_blk_exp_create() [all …]
|
H A D | virtio-blk-handler.c | 53 virtio_blk_discard_write_zeroes(VirtioBlkHandler *handler, struct iovec *iov, in virtio_blk_discard_write_zeroes() argument 56 BlockBackend *blk = handler->blk; in virtio_blk_discard_write_zeroes() 90 if (unlikely(!virtio_blk_sect_range_ok(blk, handler->logical_block_size, in virtio_blk_discard_write_zeroes() 132 int coroutine_fn virtio_blk_process_req(VirtioBlkHandler *handler, in virtio_blk_process_req() argument 138 BlockBackend *blk = handler->blk; in virtio_blk_process_req() 179 if (is_write && !handler->writable) { in virtio_blk_process_req() 191 handler->logical_block_size, in virtio_blk_process_req() 219 size_t size = MIN(strlen(handler->serial) + 1, in virtio_blk_process_req() 222 iov_from_buf(in_iov, in_num, 0, handler->serial, size); in virtio_blk_process_req() 228 if (!handler->writable) { in virtio_blk_process_req() [all …]
|
H A D | virtio-blk-handler.h | 31 int coroutine_fn virtio_blk_process_req(VirtioBlkHandler *handler,
|
/qemu/block/ |
H A D | file-posix.c | 3576 ThreadPoolFunc *handler; in raw_do_pwrite_zeroes() local 3629 handler = handle_aiocb_write_zeroes_unmap; in raw_do_pwrite_zeroes() 3631 handler = handle_aiocb_write_zeroes; in raw_do_pwrite_zeroes() 3634 return raw_thread_pool_submit(handler, &acb); in raw_do_pwrite_zeroes()
|
/qemu/bsd-user/ |
H A D | signal.c | 889 abi_ulong handler; in handle_pending_signal() local 900 handler = TARGET_SIG_IGN; in handle_pending_signal() 903 handler = sa->_sa_handler; in handle_pending_signal() 910 if (handler == TARGET_SIG_DFL) { in handle_pending_signal() 923 } else if (handler == TARGET_SIG_IGN) { in handle_pending_signal() 925 } else if (handler == TARGET_SIG_ERR) { in handle_pending_signal()
|
/qemu/docs/devel/ |
H A D | control-flow-integrity.rst | 81 signal handler may have been provided by an external library or even plugged
|
H A D | multi-process.rst | 535 install an address space handler at that address which forwards the MSI 866 changes to the route. This handler will broadly follow the VFIO
|
H A D | qapi-code-gen.rst | 559 When a command is executed in-band, its handler runs in the main 562 When a command is executed out-of-band, its handler runs in a 565 An OOB-capable command handler must satisfy the following conditions: 573 handler code. 593 Member 'coroutine' tells the QMP dispatcher whether the command handler 595 the command handler is called from coroutine context and may yield while 611 Since the command handler may assume coroutine context, any callers 613 In particular, HMP commands calling such a QMP command handler must be
|
H A D | tcg-plugins.rst | 86 events. Generally plugins will register a handler for the *atexit* 152 (e.g. entering a exception handler).
|
H A D | writing-monitor-commands.rst | 633 The case of writing a HMP info handler that calls a no-parameter QMP query 635 purpose HMP info handler for this scenario. All that is required to expose 637 '.cmd_info_hrt' field to point to the QMP handler, and leave the '.cmd'
|
/qemu/docs/devel/migration/ |
H A D | dirty-limit.rst | 63 sleeps in the path of the KVM_EXIT_DIRTY_RING_FULL exception handler, that
|
H A D | vfio.rst | 83 The VFIO migration code uses a VM state change handler to change the VFIO 87 Similarly, a migration state change handler is used to trigger a transition of
|
/qemu/docs/interop/ |
H A D | vhost-user.rst | 1918 by the management layer, or to a log handler).
|
/qemu/docs/specs/ |
H A D | acpi_cpu_hotplug.rst | 7 ACPI BIOS GPE.2 handler is dedicated for notifying OS about CPU hot-add 23 with GPE.2 event set. CPU present map is read by ACPI BIOS GPE.2 handler
|
H A D | acpi_hw_reduced_hotplug.rst | 13 from GPIO events. All interrupts are listed in _CRS and the handler
|
H A D | acpi_mem_hotplug.rst | 4 ACPI BIOS GPE.3 handler is dedicated for notifying OS about memory hot-add
|
H A D | acpi_nvdimm.rst | 171 ACPI BIOS GPE.4 handler is dedicated for notifying OS about nvdimm device
|
H A D | acpi_pci_hotplug.rst | 18 Read by ACPI BIOS GPE.1 handler to notify OS of injection 26 Read by ACPI BIOS GPE.1 handler to notify OS of removal
|
H A D | edu.rst | 106 needs to update the acknowledge register at the end of the IRQ handler
|
H A D | vmgenid.rst | 185 ACPI notification. The exact handler to use is not specified, so the vmgenid
|
/qemu/docs/system/ |
H A D | cpu-hotplug.rst | 140 Interrupt (SCI) and calls the ACPI handler for the affected vCPU
|
H A D | virtio-net-failover.rst | 34 handler and traffic will go through the virtio-net device. On the target
|