Home
last modified time | relevance | path

Searched full:back (Results 1 – 25 of 563) sorted by relevance

12345678910>>...23

/qemu/docs/interop/
H A Dvhost-user.rst27 *back-end*. The *front-end* is the application that shares its virtqueues, in
28 our case QEMU. The *back-end* is the consumer of the virtqueues.
30 In the current implementation QEMU is the *front-end*, and the *back-end*
33 or a block device back-end processing read & write to a virtual
34 disk. In order to facilitate interoperability between various back-end
38 The *front-end* and *back-end* can be either a client (i.e. connecting) or
55 available, QEMU will automatically fall back to pipe2 or, as a last
80 - Bit 2 is the reply flag - needs to be sent on each reply from the back-end
124 back-end will process. This is a free-running index that is not
140 back-end will process. This is a free-running index that is not
[all …]
/qemu/include/hw/virtio/
H A Dvhost.h360 * vhost_supports_device_state(): Checks whether the back-end supports
381 * the back-end for the purpose of migration. Data is to be transferred
387 * @fd is the back-end's end of the pipe: The write FD for SAVE, and the
389 * back-end, i.e. closes it in the front-end.
391 * The back-end may optionally reply with an FD of its own, if this
393 * stored in *reply_fd. The back-end will discard the FD sent to it,
395 * the back-end.
400 * from the back-end and stored by the front-end in the
404 * the back-end to restore the saved state.
408 * @fd: Back-end's end of the pipe through which to transfer state; note
[all …]
/qemu/docs/system/
H A Ddevice-emulation.rst26 A front end is often paired with a back end, which describes how the
53 Device Back End
56 The back end describes how the data from the emulated device will be
57 processed by QEMU. The configuration of the back end is usually
63 partition. Back ends can sometimes be stacked to implement features
66 While the choice of back end is generally transparent to the guest,
68 the back end is unable to support it.
H A Dvirtio-net-failover.rst30 networking device by falling back to a virtio-net device for the duration of
35 system the primary device will be automatically plugged back and the
/qemu/include/hw/xen/interface/io/
H A Dring.h75 * mytag_back_ring_t - The 'back' half of the ring.
84 * Initializing the back follows similarly (note that only the front
124 /* "Back" end's private variables */ \
143 * BACK_RING_whatever works on the "back end" of a ring: here
268 xen_wmb(); /* back sees requests /before/ updated producer index */ \
283 * notifying the back (if the back checks for new requests when it queues
310 xen_wmb(); /* back sees requests /before/ updated producer index */ \
312 xen_mb(); /* back sees new requests /before/ we check req_event */ \
/qemu/common-user/host/s390x/
H A Dsafe-syscall.inc.S41 stg %r1,0(%r15) /* store back chain */
78 lg %r15,0(%r15) /* load back chain */
91 2: lg %r15,0(%r15) /* load back chain */
/qemu/include/chardev/
H A Dchar-fe.h11 * struct CharBackend - back end as seen by front end
227 * will send data from the front end to the back end. This function
241 * send data from the front end to the back end. Unlike @qemu_chr_fe_write,
242 * this function will block if the back end cannot consume all of the data
255 * Read data to a buffer from the back end.
H A Dchar.h185 * Write data from the back end to the front end. Before issuing this call,
196 * Implementation of back end writing. Used by replay module.
213 * Send an event from the back end to the front end.
/qemu/rust/qemu-api/src/
H A Dchardev.rs37 /// back-end that is used for example by a device. Compared to the
221 /// will send data from the front end to the back end. Unlike
222 /// `write`, this function will block if the back end cannot
235 /// will send data from the front end to the back end. Unlike
236 /// `write`, this function will block if the back end cannot
/qemu/tests/qtest/
H A Dnuma-test.c451 " 'level': 1, 'associativity': \"direct\", 'policy': \"write-back\"," in pc_hmat_build_cfg()
457 " 'level': 4, 'associativity': \"direct\", 'policy': \"write-back\"," in pc_hmat_build_cfg()
468 " 'level': 0, 'associativity': \"none\", 'policy': \"write-back\"," in pc_hmat_build_cfg()
479 " 'level': 1, 'associativity': \"direct\", 'policy': \"write-back\"," in pc_hmat_build_cfg()
483 " 'level': 1, 'associativity': \"direct\", 'policy': \"write-back\"," in pc_hmat_build_cfg()
488 " 'level': 2, 'associativity': \"direct\", 'policy': \"write-back\"," in pc_hmat_build_cfg()
493 " 'level': 0, 'associativity': \"direct\", 'policy': \"write-back\"," in pc_hmat_build_cfg()
497 " 'level': 1, 'associativity': \"direct\", 'policy': \"write-back\"," in pc_hmat_build_cfg()
536 " 'level': 1, 'associativity': \"direct\", 'policy': \"write-back\"," in pc_hmat_off_cfg()
581 " 'level': 1, 'associativity': \"direct\", 'policy': \"write-back\"," in pc_hmat_erange_cfg()
H A Dvmcoreinfo-test.c37 /* read vmcoreinfo and read back the host format */ in test_vmcoreinfo_write_basic()
58 /* now read back the values we wrote and compare that they are the same */ in test_vmcoreinfo_write_basic()
H A Dtest-netfilter.c68 /* add back the netdev */ in remove_netdev_with_one_netfilter()
166 /* add back the netdev */ in remove_netdev_with_multi_netfilter()
/qemu/hw/nvme/
H A Dnguid.c93 * string does not start with the separator and they are not back to in nvme_nguid_is_valid()
94 * back "--". in nvme_nguid_is_valid()
136 * When converted back to string this implementation will use a raw hex number
/qemu/hw/virtio/
H A Dvhost-user-fs.c320 "Error saving back-end state of %s device %s " in vuf_save_state()
344 "Error loading back-end state of %s device %s " in vuf_load_state()
366 error_report("Back-end of %s device %s (tag: \"%s\") does not support " in vuf_check_migration_support()
399 .name = "back-end",
401 .name = "virtio-fs back-end state",
/qemu/include/authz/
H A Dbase.h67 * @errp should never be fed back to the user being
90 * @errp should never be fed back to the user being
/qemu/audio/
H A Dsndioaudio.c171 * call-back called when one of the descriptors
243 * put back to sndio back-end a buffer returned by sndio_get_buffer_out()
295 * call-back called when one of our descriptors becomes writable
305 * call-back called when one of our descriptors becomes readable
/qemu/docs/devel/migration/
H A Dpostcopy.rst234 postcopy migration on both sides and go back to **POSTCOPY_ACTIVE**
257 c) Note that ``-mem-path /dev/hugepages`` will fall back to allocating normal
282 userfaultfd back to QEMU together with a mapping table that allows
283 fault addresses in the clients address space to be converted back to
/qemu/docs/system/devices/
H A Dvhost-user.rst3 vhost-user back ends
6 vhost-user back ends are way to service the request of VirtIO devices
/qemu/tests/unit/
H A Dtest-bitmap.c34 /* Shift back 200 bits back */ in check_bitmap_copy_with_offset()
/qemu/util/
H A Dcoroutine-sigaltstack.c98 /* Initialize longjmp environment and switch back the caller */ in coroutine_bootstrap()
136 * Ok, the caller has siglongjmp'ed back to us, so now prepare in coroutine_trampoline()
225 * Inform the system that we are back off the signal stack by in qemu_coroutine_new()
/qemu/target/m68k/
H A Dop_helper.c336 /* write back 1 / push data 0 */ in m68k_interrupt_all()
339 /* write back 1 address */ in m68k_interrupt_all()
342 /* write back 2 data */ in m68k_interrupt_all()
345 /* write back 2 address */ in m68k_interrupt_all()
348 /* write back 3 data */ in m68k_interrupt_all()
351 /* write back 3 address */ in m68k_interrupt_all()
357 /* write back 1 status */ in m68k_interrupt_all()
360 /* write back 2 status */ in m68k_interrupt_all()
363 /* write back 3 status */ in m68k_interrupt_all()
/qemu/hw/nvram/
H A Dds1225y.c87 /* Write back nvram contents */ in nvram_post_load()
90 /* Write back contents, as 'wb' mode cleaned the file */ in nvram_post_load()
/qemu/hw/9pfs/
H A Dcoth.h49 * yield in qemu thread and re-enter back \
57 /* re-enter back to qemu thread */ \
/qemu/tests/tcg/aarch64/gdbstub/
H A Dtest-mte.py75 # Read the known values back and check if they remain the same.
91 # And read back the tags of the last two granules in page so
/qemu/docs/devel/
H A Dtcg.rst41 current TB, going through the TB epilogue, and then back to the
54 multiple TBs to be chained directly, without having to go back to the
110 the destination TB, without going back to the main loop.

12345678910>>...23