/qemu/hw/ppc/ |
H A D | pnv_chiptod.c | 158 static void chiptod_receive_ttype(PnvChipTOD *chiptod, uint32_t trigger) in chiptod_receive_ttype() argument 160 switch (trigger) { in chiptod_receive_ttype() 176 " TTYPE %u\n", trigger); in chiptod_receive_ttype() 182 uint32_t trigger) in chiptod_power9_broadcast_ttype() argument 192 chiptod_receive_ttype(chiptod, trigger); in chiptod_power9_broadcast_ttype() 198 uint32_t trigger) in chiptod_power10_broadcast_ttype() argument 208 chiptod_receive_ttype(chiptod, trigger); in chiptod_power10_broadcast_ttype()
|
/qemu/hw/intc/ |
H A D | aspeed_vic.c | 145 val = s->trigger; in aspeed_vic_read() 302 s->trigger = 0; in aspeed_vic_reset() 334 VMSTATE_UINT64(trigger, AspeedVICState),
|
/qemu/hw/core/ |
H A D | ptimer.c | 158 bool trigger = true; in ptimer_tick() local 186 trigger = (delta_adjust == DELTA_ADJUST); in ptimer_tick() 194 if (trigger) { in ptimer_tick()
|
/qemu/include/hw/intc/ |
H A D | aspeed_vic.h | 37 uint64_t trigger; member
|
/qemu/include/hw/timer/ |
H A D | stellaris-gptm.h | 46 qemu_irq trigger; member
|
/qemu/include/hw/ppc/ |
H A D | pnv_chiptod.h | 47 void (*broadcast_ttype)(PnvChipTOD *sender, uint32_t trigger);
|
/qemu/.gitlab-ci.d/cirrus/ |
H A D | README.rst | 9 offering: more specifically, we use the `cirrus-run`_ script to trigger Cirrus 44 general you'll want to be able to trigger Cirrus CI builds from non-protected
|
/qemu/hw/timer/ |
H A D | stellaris-gptm.c | 71 qemu_irq_pulse(s->trigger); in gptm_tick() 279 qdev_init_gpio_out(dev, &s->trigger, 1); in stellaris_gptm_init()
|
/qemu/python/ |
H A D | setup.cfg | 195 .[fuse] # Workaround to trigger tox venv rebuild 196 .[tui] # Workaround to trigger tox venv rebuild
|
/qemu/include/standard-headers/linux/ |
H A D | input.h | 455 struct ff_trigger trigger; member
|
/qemu/docs/devel/ |
H A D | block-coroutine-wrapper.rst | 26 trigger the generation:
|
H A D | tcg-icount.rst | 56 might potentially trigger an I/O event, at which point we will need an
|
H A D | clocks.rst | 412 ``clock_update_ns()`` or ``clock_update_hz()`` function. It will trigger 430 Because updating a clock may trigger any side effects through 538 will trigger side effects to other devices in an unknown state.
|
H A D | multiple-iothreads.rst | 104 are thread-safe. They can be used to trigger activity in an ``IOThread``.
|
/qemu/docs/system/s390x/ |
H A D | protvirt.rst | 57 (stage3a) that uses the new diag308 subcodes 8 and 10 to trigger the
|
/qemu/hw/i386/ |
H A D | trace-events | 61 …, int tri, int vec, int deliver, uint32_t dest, int dest_mode) "index %d trigger %d vector %d deli… 70 …uint16_t sid, int index, int trig, int target) "sid 0x%"PRIx16" index %d trigger %d (should be: %d…
|
/qemu/qapi/ |
H A D | migration.json | 751 # @throttle-trigger-threshold: The ratio of bytes_dirty_period and 752 # bytes_xfer_period to trigger throttling. It is expressed as 899 'throttle-trigger-threshold', 932 # @throttle-trigger-threshold: The ratio of bytes_dirty_period and 933 # bytes_xfer_period to trigger throttling. It is expressed as 1085 '*throttle-trigger-threshold': 'uint8', 1146 # @throttle-trigger-threshold: The ratio of bytes_dirty_period and 1147 # bytes_xfer_period to trigger throttling. It is expressed as 1292 '*throttle-trigger-threshold': 'uint8', 1923 # Xen uses this command to notify replication to trigger a checkpoint.
|
H A D | job.json | 190 # Manually trigger completion of an active job in the READY or STANDBY
|
/qemu/docs/system/i386/ |
H A D | microvm.rst | 118 The recommended way to trigger a guest-initiated shut down is by
|
/qemu/docs/devel/testing/ |
H A D | fuzzing.rst | 47 Now the only thing left to do is wait for the fuzzer to trigger potential 67 trigger many debug/error messages, or create output on the serial console.
|
H A D | blkdebug.rst | 23 Error injection allows test cases to trigger I/O errors at specific points.
|
/qemu/docs/ |
H A D | COLO-FT.txt | 90 the heartbeat stops responding, the secondary node will trigger a failover 110 HeartBeat has not been implemented yet, so you need to trigger failover process
|
/qemu/docs/tools/ |
H A D | qemu-nbd.rst | 266 malicious guest may have prepared the image to attempt to trigger
|
/qemu/docs/system/ |
H A D | security.rst | 149 and/or trigger spawning of external processes.
|
/qemu/docs/devel/migration/ |
H A D | vfio.rst | 107 Similarly, a migration state change handler is used to trigger a transition of
|