Home
last modified time | relevance | path

Searched full:issue (Results 1 – 25 of 150) sorted by relevance

123456

/qemu/docs/specs/
H A Dvmw_pvscsi-spec.rst18 The registers area is used to raise hypervisor interrupts and issue device
29 are registers to issue device commands (with optional short data),
30 issue device interrupts, and control interrupt masking.
81 a. Issue ``PVSCSI_CMD_ADAPTER_RESET`` command
83 c. Issue ``PVSCSI_CMD_SETUP_MSG_RING`` command with no additional data,
86 d. Issue ``PVSCSI_CMD_SETUP_RINGS`` command, provide rings configuration
88 e. Issue ``PVSCSI_CMD_SETUP_MSG_RING`` command again, provide
97 c. Issue ``PVSCSI_CMD_ADAPTER_RESET`` command
103 b. Issue ``PVSCSI_REG_OFFSET_KICK_RW_IO`` for R/W operations
109 a. Issue ``PVSCSI_CMD_ABORT_CMD`` command
/qemu/.gitlab/issue_templates/
H A Dbug.md2 This is the upstream QEMU issue tracker.
16 If this is a security issue, please consult
61 The line below ensures that proper tags are added to the issue.
H A Dfeature_request.md2 This is the upstream QEMU issue tracker.
29 The line below ensures that proper tags are added to the issue.
/qemu/docs/devel/migration/
H A DCPR.rst56 * Issue the ``migrate`` command. It is recommended the URI be a
66 * Issue the ``migrate-incoming`` command.
188 * Issue the ``migrate`` command, containing a main channel and
209 When using ``-incoming defer``, you must issue the migrate command to
214 main migration channel until you issue the migrate incoming command.
271 accepting the main migration channel. Again note you must issue the
272 migrate command to old QEMU before you can issue any monitor
H A Dpostcopy.rst22 To enable postcopy, issue this command on the monitor (both source and
207 QEMU instances. On the other hand, when issue happens QEMU on both sides
213 - When network issue occurs, both QEMU will go into **POSTCOPY_PAUSED**
/qemu/hw/intc/
H A Drx_icu.c94 int issue; in rxicu_set_irq() local
107 issue = level; in rxicu_set_irq()
111 issue = (level == 0 && src->level == 1); in rxicu_set_irq()
115 issue = (level == 1 && src->level == 0); in rxicu_set_irq()
119 issue = ((level ^ src->level) & 1); in rxicu_set_irq()
125 if (issue == 0 && src->sense == TRG_LEVEL) { in rxicu_set_irq()
134 if (issue) { in rxicu_set_irq()
/qemu/docs/devel/
H A Dconflict-resolution.rst22 a mutual friend, and/or someone with background on the issue, but not
26 if the problem requires immediate escalation, report the issue to the QEMU
41 Escalating an issue to the QEMU leadership committee may result in actions
H A Dcode-of-conduct.rst44 This includes IRC, the mailing lists, the issue tracker, community
/qemu/tests/vm/
H A Dubuntuvm.py37 # First command we issue is fix for slow ssh login.
53 # Issue the install commands.
H A Dconf_example_aarch64.yml47 # To install a different set of packages, provide a command to issue
/qemu/tests/qemu-iotests/tests/
H A Dexport-incoming-iothread4 # Regression test for issue 945:
67 # Regression test for issue 945: This should not fail an assertion
H A Dmirror-change-copy-mode171 # Issue enough requests for a few seconds only touching the first half
179 # Now issue a synchronous write in the second half of the image and
/qemu/tests/qemu-iotests/
H A D21639 # request and re-issue a new one to its child, which this time is a
45 # its child and therefore is not hit by this issue.
H A D151288 Throttle the source node, then issue a whole bunch of external requests
330 # (i.e. one less than 5). We expect the mirror job to issue background
376 Issue requests on the mirror source node right as the mirror is
395 # Give qemu-img bench time to start up and issue requests
H A D03256 # actually loop a while and issue many I/O requests for the lower layer
/qemu/accel/tcg/
H A Dbackend-ldst.h32 * for the guest memory model, issue a host memory barrier.
/qemu/docs/interop/
H A Dbitmaps.rst497 #. At a later point, issue incremental backups from ``bitmap0``.
513 #. At a later point, issue incremental backups from ``bitmap0``.
750 #. Issue an incremental backup command:
823 #. Issue a new incremental backup command. The only difference here is that we
920 #. Issue a new incremental backup command. Apart from the new destination
1130 #. Issue a multi-drive incremental push backup transaction:
1387 #. Issue the transaction to start a backup of both drives.
1484 To repair this, issue a new incremental backup across both drives. The result
1515 #. Issue the multi-drive incremental backup transaction:
H A Dqmp-spec.rst64 Right when connected the Server will issue a greeting message, which signals
126 the other. The client therefore receives command responses in issue
154 There are two possible responses which the Server will issue as the result
/qemu/docs/system/
H A Dtls.rst23 At a minimum it is necessary to setup a certificate authority, and issue
107 information for each server, and use it to issue server certificates.
162 the information for each client, and use it to issue client
/qemu/python/
H A DPACKAGE.rst31 Please report bugs on the `QEMU issue tracker
/qemu/include/hw/xen/interface/
H A Dphysdev.h32 * must issue PHYSDEVOP_eoi. The semantics of PHYSDEVOP_eoi change slightly
40 * guest must issue PHYSDEVOP_eoi. This hypercall is very similar to
/qemu/include/qemu/
H A Datomic128.h55 * The guest may issue a large atomic operation and then access those
/qemu/include/system/
H A Dspdm-socket.h58 * This will issue a shutdown command to the server.
/qemu/include/chardev/
H A Dchar-fe.h87 * @sync_state: whether to issue event callback with updated state
267 * Issue a device specific ioctl to a backend. This function is thread-safe.
/qemu/include/exec/
H A Dhelper-proto.h.inc11 * Work around an issue with --enable-lto, in which GCC's ipa-split pass

123456