Home
last modified time | relevance | path

Searched full:communication (Results 1 – 25 of 90) sorted by relevance

1234

/qemu/docs/system/i386/
H A Dnitro-enclave.rst9 on Firecracker microvm with a vhost-vsock device for communication with the
21 must be run alongside nitro-enclave for the vsock communication to work.
59 applications' vsock communication works. For example, the nitro-enclave VM's init
65 VM for successful communication with the enclave VM.
H A Dhyperv.rst87 When enabled, this enlightenment provides additional communication facilities
219 When enabled, this enlightenment provides additional communication facilities
221 This new communication is used by Windows Kernel debugger rather than sending
/qemu/docs/devel/
H A Duefi-vars.rst22 Communication with the firmware code running in SMM mode works by
32 communication with the host uses a virtual device, which essentially
H A Dcode-of-conduct.rst8 but it can also lead to communication issues and unhappiness.
46 community uses for communication. This code of conduct also applies
/qemu/docs/
H A Dspice-port-fqdn.txt1 A Spice port channel is an arbitrary communication between the Spice
/qemu/include/hw/char/
H A Drenesas_sci.h2 * Renesas Serial Communication Interface
/qemu/include/qemu/
H A Dcrc32c.h8 * and 32 Parity Bits",IEEE Transactions on Communication,
/qemu/include/hw/misc/
H A Dbcm2835_mbox_defs.h21 /* Layout of the private address space used for communication between
H A Dmps2-scc.h13 * This is a model of the Serial Communication Controller (SCC)
H A Dmips_itu.h2 * Inter-Thread Communication Unit emulation.
/qemu/include/system/
H A Dkvm_xen.h19 /* QEMU plays the rôle of dom0 for "interdomain" communication. */
/qemu/docs/system/
H A Dtarget-rx.rst15 - Serial Communication Interface x 1CH (SCI0)
/qemu/include/hw/uefi/
H A Dvar-service-api.h4 * uefi-vars device - API of the virtual device for guest/host communication.
/qemu/include/hw/xen/interface/io/
H A Dxenbus.h14 * The state of either end of the Xenbus, i.e. the current communication
/qemu/docs/system/devices/
H A Divshmem-flat.rst14 device to be used together with the traditional ivshmem, enabling communication
/qemu/include/hw/remote/
H A Dmpqemu-link.h2 * Communication channel between QEMU and remote device process
/qemu/hw/net/can/
H A Dtrace-events9 xlnx_can_rx_discard(uint32_t status) "Controller is not enabled for bus communication. Status Regis…
/qemu/gdbstub/
H A Duser.c53 * ACTIVE -> DISABLED : On communication error.
55 * DEACTIVATING -> DISABLED : On communication error.
59 * INACTIVE -> DISABLED : On communication error.
61 * ENABLING -> DISABLED : On communication error.
/qemu/docs/interop/
H A Dvhost-user.rst22 space process on the same host. It uses communication over a Unix
26 The protocol defines 2 sides of the communication, *front-end* and
39 server (listening) in the socket communication.
377 Communication chapter
385 The communication consists of the *front-end* sending message requests and
700 The back-end relies on the back-end communication channel (see :ref:`Back-end
701 communication <backend_communication>` section below) to send IOTLB miss
722 Back-end communication
725 An optional communication channel is provided if the back-end declares
732 using this fd communication channel.
[all …]
H A Dvhost-user-gpu.rst182 New messages and communication changes are negotiated thanks to the
186 Communication chapter
/qemu/docs/tools/
H A Dqemu-pr-helper.rst25 accept incoming connections for communication with QEMU.
H A Dqemu-vmsr-helper.rst24 socket which will accept incoming connections for communication with QEMU.
/qemu/docs/system/ppc/
H A Dpowernv.rst19 * XSCOM, serial communication sideband bus to configure chiplets.
25 * iBT device to handle BMC communication, with the internal BMC simulator
/qemu/migration/
H A Dmultifd.h194 /* communication channel */
250 /* communication channel */
/qemu/pc-bios/
H A Dedk2-licenses.txt289 electronic, verbal, or written communication sent to the
291 to communication on electronic mailing lists, source code
295 communication that is conspicuously marked or otherwise
510 electronic, verbal, or written communication sent to the
512 to communication on electronic mailing lists, source code
516 communication that is conspicuously marked or otherwise

1234