Home
last modified time | relevance | path

Searched full:protocol (Results 1 – 25 of 362) sorted by relevance

12345678910>>...15

/qemu/tests/qemu-iotests/
H A D266.out7 …", "arguments": {"driver": "file", "filename": "TEST_DIR/PID-t.vpc", "node-name": "protocol-node"}}
12 …, "arguments": {"job-id": "job0", "options": {"driver": "vpc", "file": "protocol-node", "size": 67…
29 …", "arguments": {"driver": "file", "filename": "TEST_DIR/PID-t.vpc", "node-name": "protocol-node"}}
34 …, "arguments": {"job-id": "job0", "options": {"driver": "vpc", "file": "protocol-node", "force-siz…
51 …", "arguments": {"driver": "file", "filename": "TEST_DIR/PID-t.vpc", "node-name": "protocol-node"}}
56 …, "arguments": {"job-id": "job0", "options": {"driver": "vpc", "file": "protocol-node", "force-siz…
72 …", "arguments": {"driver": "file", "filename": "TEST_DIR/PID-t.vpc", "node-name": "protocol-node"}}
77 …, "arguments": {"job-id": "job0", "options": {"driver": "vpc", "file": "protocol-node", "force-siz…
92 …", "arguments": {"driver": "file", "filename": "TEST_DIR/PID-t.vpc", "node-name": "protocol-node"}}
97 …, "arguments": {"job-id": "job0", "options": {"driver": "vpc", "file": "protocol-node", "size": 0}…
[all …]
H A D26636 'file': 'protocol-node',
50 'file': 'protocol-node',
65 'file': 'protocol-node',
80 'file': 'protocol-node',
91 'file': 'protocol-node',
101 'file': 'protocol-node',
111 'file': 'protocol-node',
132 node_name='protocol-node',
H A D1264 # Tests handling of colons in filenames (which may be confused with protocol
39 # This is the default protocol (and we want to test the difference between
40 # colons which separate a protocol prefix from the rest and colons which are
48 # A colon after a slash is not a protocol prefix separator
96 # -- but behavior for that case is a bit strange. Protocol-prefixed paths are
102 # (The root of the issue is the use of a relative path with a protocol prefix.
H A D30893 # Return the length of the protocol file
94 # $1: Protocol node export mount point
125 # Separate blockdev-add calls for format and protocol so we can remove
131 'node-name': 'node-protocol',
141 'file': 'node-protocol'
267 # Here, we need to export the protocol node -- the format layer may
282 # Now export the protocol node
287 'node-protocol'
333 'node-protocol'
/qemu/docs/
H A Drdma.txt18 * RDMA Migration Protocol Description
135 RDMA Protocol Description:
144 protocol now, consisting of infiniband SEND messages.
186 which is described by a formal protocol. Each SEND message has a
196 in a single message without any need to change the protocol itself
197 so that the protocol is compatible against multiple versions of QEMU.
198 Version #1 requires that all server implementations of the protocol must
226 After ram block exchange is completed, we have two protocol-level
267 this protocol before the actual migration begins. This information includes
278 its own protocol information during the migration process.
[all …]
/qemu/hw/display/
H A Dapple-gfx.h20 @protocol PGDevice;
21 @protocol PGDisplay;
22 @protocol MTLDevice;
23 @protocol MTLTexture;
24 @protocol MTLCommandQueue;
/qemu/docs/devel/testing/
H A Dqtest.rst13 clock stepping), with a special purpose "qtest" protocol. Refer to
14 :ref:`qtest-protocol` for more details of the protocol.
81 .. _qtest-protocol:
83 QTest Protocol
87 :doc: QTest Protocol
/qemu/docs/interop/
H A Dvhost-user.rst4 Vhost-user Protocol
19 This protocol is aiming to complement the ``ioctl`` interface used to
26 The protocol defines 2 sides of the communication, *front-end* and
187 When the ``VHOST_USER_PROTOCOL_F_XEN_MMAP`` protocol feature has been
380 The protocol for vhost-user is based on the existing implementation of
398 The section on ``REPLY_ACK`` protocol extension.
421 Any protocol extensions are gated by protocol feature bits, which
423 older back-ends don't support negotiating protocol features, a feature
434 This reserved feature bit was reused by the vhost-user protocol to add
435 vhost-user protocol feature negotiation in a backwards compatible
[all …]
H A Dnbd.rst1 QEMU NBD protocol support
4 QEMU supports the NBD protocol, and has an internal NBD client (see
9 The NBD protocol is specified here:
13 protocol realization in QEMU.
19 NBD protocol specification, and also defines an additional metadata
H A Dvhost-user-gpu.rst2 Vhost-user-gpu Protocol
15 The vhost-user-gpu protocol is aiming at sharing the rendering result
18 server protocol, if you consider QEMU as the display server and the
24 The protocol is sent over a UNIX domain stream socket, since it uses
174 Protocol features
197 Get the supported protocol features bitmask.
204 Enable protocol features using a bitmask.
278 This message requires the ``VHOST_USER_GPU_PROTOCOL_F_EDID`` protocol
288 This message requires the ``VHOST_USER_GPU_PROTOCOL_F_DMABUF2`` protocol
H A Dqmp-spec.rst9 QEMU Machine Protocol Specification
12 The QEMU Machine Protocol (QMP) is a JSON-based
13 protocol which is available for applications to operate QEMU at the
17 the protocol; details of the commands and data structures can
22 Protocol Specification
25 This section details the protocol format. For the purpose of this
41 be in a certain order. However, in real protocol usage they can be in
354 All protocol changes or new features which modify the protocol format in an
438 evolving the basic protocol, and multiple diverging basic protocol
H A Dbarrier.rst1 Barrier client protocol
8 This document briefly describes the protocol as we implement it.
23 Protocol Description
38 ``minor`` = protocol major version number supported by server
40 ``major`` = protocol minor version number supported by server
52 ``minor`` = protocol major version number supported by client
54 ``major`` = protocol minor version number supported by client
424 Protocol violation. Server should disconnect after sending this
H A Dpr-helper.rst4 Persistent reservation helper protocol
17 This document describes the socket protocol used between QEMU's
77 The sense data is always sent to keep the protocol simple, even though
83 If the protocol is violated, the helper closes the socket.
/qemu/ui/
H A Dui-hmp-cmds.c263 const char *protocol = qdict_get_str(qdict, "protocol"); in hmp_set_password() local
280 opts.protocol = qapi_enum_parse(&DisplayProtocol_lookup, protocol, in hmp_set_password()
286 if (opts.protocol == DISPLAY_PROTOCOL_VNC) { in hmp_set_password()
298 const char *protocol = qdict_get_str(qdict, "protocol"); in hmp_expire_password() local
307 opts.protocol = qapi_enum_parse(&DisplayProtocol_lookup, protocol, in hmp_expire_password()
313 if (opts.protocol == DISPLAY_PROTOCOL_VNC) { in hmp_expire_password()
467 const char *protocol = qdict_get_str(qdict, "protocol"); in hmp_client_migrate_info() local
475 qmp_client_migrate_info(protocol, hostname, in hmp_client_migrate_info()
H A Dui-qmp-cmds.c36 if (opts->protocol == DISPLAY_PROTOCOL_SPICE) { in qmp_set_password()
44 assert(opts->protocol == DISPLAY_PROTOCOL_VNC); in qmp_set_password()
48 " when 'protocol' is 'vnc'"); in qmp_set_password()
92 if (opts->protocol == DISPLAY_PROTOCOL_SPICE) { in qmp_expire_password()
98 assert(opts->protocol == DISPLAY_PROTOCOL_VNC); in qmp_expire_password()
187 void qmp_client_migrate_info(const char *protocol, const char *hostname, in qmp_client_migrate_info() argument
193 if (strcmp(protocol, "spice") == 0) { in qmp_client_migrate_info()
213 error_setg(errp, QERR_INVALID_PARAMETER_VALUE, "protocol", "'spice'"); in qmp_client_migrate_info()
/qemu/linux-user/sparc/
H A Dtarget_errno_defs.h23 #define TARGET_EPROTOTYPE 41 /* Protocol wrong type for socket */
25 #define TARGET_ENOPROTOOPT 42 /* Protocol not available */
27 #define TARGET_EPROTONOSUPPORT 43 /* Protocol not supported */
33 #define TARGET_EPFNOSUPPORT 46 /* Protocol family not supported */
35 #define TARGET_EAFNOSUPPORT 47 /* Address family not supported by protocol */
113 #define TARGET_EPROTO 86 /* Protocol error */
139 #define TARGET_EUNATCH 99 /* Protocol driver not attached */
/qemu/linux-user/mips/
H A Dtarget_errno_defs.h28 #define TARGET_EUNATCH 42 /* Protocol driver not attached */
76 #define TARGET_EPROTO 71 /* Protocol error */
124 #define TARGET_EPROTOTYPE 98 /* Protocol wrong type for socket */
126 #define TARGET_ENOPROTOOPT 99 /* Protocol not available */
128 #define TARGET_EPROTONOSUPPORT 120 /* Protocol not supported */
134 #define TARGET_EPFNOSUPPORT 123 /* Protocol family not supported */
136 #define TARGET_EAFNOSUPPORT 124 /* Address family not supported by protocol */
/qemu/linux-user/generic/
H A Dtarget_errno_defs.h60 #define TARGET_EUNATCH 49 /* Protocol driver not attached */
82 #define TARGET_EPROTO 71 /* Protocol error */
102 #define TARGET_EPROTOTYPE 91 /* Protocol wrong type for socket */
103 #define TARGET_ENOPROTOOPT 92 /* Protocol not available */
104 #define TARGET_EPROTONOSUPPORT 93 /* Protocol not supported */
107 #define TARGET_EPFNOSUPPORT 96 /* Protocol family not supported */
108 #define TARGET_EAFNOSUPPORT 97 /* Address family not supported by protocol */
/qemu/include/qemu/
H A Dsockets.h16 int qemu_socket(int domain, int type, int protocol);
22 * @protocol: specifies a particular protocol to be used with the socket
26 * of the specified type, and using the optionally specified protocol.
31 int qemu_socketpair(int domain, int type, int protocol, int sv[2]);
/qemu/python/qemu/qmp/
H A D__init__.py2 QEMU Monitor Protocol (QMP) development library & tooling.
5 asynchronously with QMP protocol servers, as implemented by QEMU, the
29 from .protocol import (
H A Dprotocol.py2 Generic Asynchronous Message-based Protocol Support
6 that implements the core mechanisms of a simple send/receive protocol,
59 """Protocol session runstate."""
169 AsyncProtocol implements a generic async message-based protocol.
171 This protocol assumes the basic unit of information transfer between
177 It is designed to be extended by a specific protocol which provides
186 A protocol implementation can override this call, inserting
200 will log to 'qemu.qmp.protocol', but each individual connection
202 then log to 'qemu.qmp.protocol.${name}'.
293 protocol-level failure occurs while establishing a new
[all …]
/qemu/include/gdbstub/
H A Dsyscalls.h12 /* For gdb file i/o remote protocol open flags. */
21 /* For gdb file i/o remote protocol errno values */
43 /* For gdb file i/o remote protocol lseek whence. */
86 * for the F request packet in the GDB remote protocol. A limited set of
/qemu/docs/specs/
H A Divshmem-spec.rst157 The next section describes the protocol in detail.
173 The ivshmem Client-Server Protocol
177 server. This section details the protocol between the two.
189 1. The protocol version number, currently zero. The client should
225 * The protocol changed incompatibly in QEMU 2.5. Before, messages
228 * The protocol is poorly designed.
230 The ivshmem Client-Client Protocol
/qemu/qapi/
H A Ddump.json70 # @protocol: the filename or file descriptor of the vmcore. The
73 # 1. file: the protocol starts with "file:", and the following
75 # 2. fd: the protocol starts with "fd:", and the following string
100 # "arguments": { "paging": false, "protocol": "fd:dump" } }
104 'data': { 'paging': 'bool', 'protocol': 'str', '*detach': 'bool',
/qemu/hw/block/
H A Dxen_blkif.h8 * Not a real protocol. Used to generate ring structs which contain
11 * avoid using switch(protocol) in a number of places.
20 /* i386 protocol version */
47 /* x86_64 protocol version */

12345678910>>...15