Home
last modified time | relevance | path

Searched refs:change (Results 1 – 25 of 138) sorted by relevance

123456

/qemu/tests/qemu-iotests/
A D133.out7 qemu-io: Cannot change the option 'node-name'
8 qemu-io: Cannot change the option 'node-name'
9 qemu-io: Cannot change the option 'node-name'
16 qemu-io: Cannot change the option 'driver'
17 qemu-io: Cannot change the option 'driver'
18 qemu-io: Cannot change the option 'driver'
A D228.out13 --- change-backing-file ---
17 {"execute": "change-backing-file", "arguments": {"backing-file": "null-co://", "device": "node0", "…
24 {"execute": "change-backing-file", "arguments": {"backing-file": "TEST_DIR/PID-base.img", "device":…
31 {"execute": "change-backing-file", "arguments": {"backing-file": "file:TEST_DIR/PID-base.img", "dev…
A D161.out15 *** Stream and then change an option on the backing file
34 *** Commit and then change an option on the backing file
A D173.out24 'execute': 'change-backing-file'
/qemu/hw/xtensa/
A Dmx_pic.c188 uint32_t change = 0; in xtensa_mx_pic_ext_reg_write() local
194 change = mx->mieng & v; in xtensa_mx_pic_ext_reg_write()
202 change = ~mx->mieng & v; in xtensa_mx_pic_ext_reg_write()
210 change = mx->miasg & v; in xtensa_mx_pic_ext_reg_write()
218 change = ~mx->miasg & v; in xtensa_mx_pic_ext_reg_write()
226 change = mx->mipipart ^ v; in xtensa_mx_pic_ext_reg_write()
234 change = mx->runstall ^ v; in xtensa_mx_pic_ext_reg_write()
240 if (change & (1u << cpu)) { in xtensa_mx_pic_ext_reg_write()
256 if (change) { in xtensa_mx_pic_ext_reg_write()
/qemu/hw/intc/
A Daspeed_intc.c143 uint32_t change; in aspeed_intc_write() local
195 change = s->regs[addr] ^ data; in aspeed_intc_write()
196 if (change & data) { in aspeed_intc_write()
197 s->mask[irq] &= ~change; in aspeed_intc_write()
198 trace_aspeed_intc_unmask(change, s->mask[irq]); in aspeed_intc_write()
200 s->mask[irq] |= change; in aspeed_intc_write()
201 trace_aspeed_intc_mask(change, s->mask[irq]); in aspeed_intc_write()
A Dspapr_xive_kvm.c794 xive->change = qemu_add_vm_change_state_handler( in kvmppc_xive_connect()
865 if (xive->change) { in kvmppc_xive_disconnect()
866 qemu_del_vm_change_state_handler(xive->change); in kvmppc_xive_disconnect()
867 xive->change = NULL; in kvmppc_xive_disconnect()
/qemu/docs/system/devices/
A Digb.rst42 As these devices are very similar, if you make a change for igb and the same
43 change can be applied to e1000e and e1000, please do so.
45 Please do not forget to run tests before submitting a change. As tests included
47 the change to confirm it works in an integrated system.
/qemu/hw/input/
A Dtrace-events7 adb_device_kbd_request_change_addr(int devaddr) "change addr to 0x%x"
8 adb_device_kbd_request_change_addr_and_handler(int devaddr, int handler) "change addr and handler t…
14 adb_device_mouse_request_change_addr(int devaddr) "change addr to 0x%x"
15 adb_device_mouse_request_change_addr_and_handler(int devaddr, int handler) "change addr and handler…
/qemu/subprojects/packagefiles/
A Dbilge-impl-1.63.0.patch39 …back variant must have exactly one field"; help = "use only one field or change to a unit variant")
42 …back variant must have exactly one field"; help = "use only one field or change to a unit variant")
/qemu/docs/devel/
A Dtcg.rst22 The target CPUs have many internal states which change the way they
25 CPU cannot change in it. The state is recorded in the Translation
115 * The change in CPU state must be constant, e.g., a direct branch and
119 may change, causing the code at the destination address to change.
179 mappings change, all caches in QEMU are physically indexed. This
183 change, chaining is only performed when the destination of the jump
A Dreplay.rst110 Two functions are used for this purpose; because these actions change
133 do not change the virtual machine state. For this reason real time
147 All virtual devices should use virtual clock for timers that change the guest
151 Virtual devices can also use realtime clock for the events that do not change
222 after that stop should not break the replay by the unneeded guest state change.
237 that perform operations with virtual hardware. These operations may change
238 system's state (e.g., change some register or generate interrupt) and
A Dclocks.rst115 * change" section below for more information).
149 change it using ``clock_set_ns()`` or ``clock_set_hz()``.
152 change (for example the main clock source of a board), then you'll have
260 It is not possible to disconnect a clock or to change the clock connection
278 You can change the multiplier and divider of a clock at runtime,
287 ``clock_propagate()``. If you make a runtime change to the
411 A device can change its outputs using the ``clock_update()``,
424 change the clock value by doing:
478 try to change the clock period or set a callback to the clock. This
/qemu/qapi/
A Djob.json108 # @change: see @block-job-change (since 8.2)
114 'finalize', 'change' ] }
173 # JOB_STATUS_CHANGE event. Usually, the status will change to
249 # of the job. This value can arbitrarily change while the job is
A Dblock.json348 # -> { "execute": "blockdev-change-medium",
357 # -> { "execute": "blockdev-change-medium",
367 # -> { "execute": "blockdev-change-medium",
/qemu/target/xtensa/
A Ddbg_helper.c39 uint32_t change = v ^ env->sregs[IBREAKENABLE]; in HELPER() local
43 if (change & (1 << i)) { in HELPER()
/qemu/docs/specs/
A Dvmgenid.rst18 guest operating system notices the change, and is then able to react as
147 change the contents of the memory at runtime, specifically when starting a
174 shown above in the iasl dump). Note that this change is not propagated
181 Since BIOS or UEFI does not necessarily run when we wish to change the GUID,
184 As spelled out in the specification, any change to the GUID executes an
/qemu/docs/
A DCOLO-FT.txt149 change the IP Addresses if you want to run it on two hosts. Initially
155 You don't need to change any IP's here, because 0.0.0.0 listens on any
182 size should be the same as primary.qcow2. Again, you don't need to change
228 {"execute": "x-blockdev-change", "arguments":{"parent": "colo-disk0", "node": "replication0" } }
239 to change the idle checkpoint period time
253 {"execute": "x-blockdev-change", "arguments":{ "parent": "colo-disk0", "child": "children.1"} }
291 {"execute": "x-blockdev-change", "arguments":{ "parent": "colo-disk0", "node": "replication0" } }
320 {"execute": "x-blockdev-change", "arguments":{ "parent": "colo-disk0", "node": "replication0" } }
/qemu/net/
A Dvmnet_int.h49 VMChangeStateEntry *change; member
/qemu/python/qemu/machine/
A DREADME.rst7 SDK and it is subject to change at any time.
/qemu/
A Dhmp-commands.hx211 .name = "change",
219 ``change`` *device* *setting*
225 (qemu) change ide1-cd0 /path/to/some.iso
244 ``change vnc password`` [*password*]
250 (qemu) change vnc password
741 .help = "change mouse button state (1=L, 2=M, 4=R)",
1392 Request VM to change its memory allocation to *value* (in MB).
1413 .help = "change watchdog action",
1611 .name = "chardev-change",
1614 .help = "change chardev",
[all …]
/qemu/include/block/
A Dblockjob_int.h76 void (*change)(BlockJob *job, BlockJobChangeOptions *opts, Error **errp); member
/qemu/include/hw/virtio/
A Dvirtio-blk.h62 VMChangeStateEntry *change; member
/qemu/docs/system/arm/
A Daspeed.rst130 * ``fmc-model`` to change the default FMC Flash model. FW needs
133 * ``spi-model`` to change the default SPI Flash model.
201 The ``boot-emmc`` option can be set or unset, to change the default
239 * ``bmc-console`` to change the default console device. Most of the
244 To change the boot console and use device ``UART3`` (``/dev/ttyS2``
/qemu/docs/system/
A Dkeys.rst.inc2 the following table to change modes. By default the modifier is Ctrl-Alt

Completed in 52 milliseconds

123456