| /qemu/docs/ |
| H A D | bypass-iommu.txt | 7 devices in the system can only support go through vIOMMU or not, which
9 coexist of devices go through vIOMMU and devices not. This is useful to
10 passthrough devices with no-iommu mode and devices go through vIOMMU in
18 the attached devices will go through vIOMMU by default.
47 - a pxb host bridge which go through SMMUv3
61 - a pxb host bridge which go through iommu
88 so that the devices will by default go through iommu if there exist one.
|
| /qemu/tests/migration-stress/guestperf/ |
| H A D | plot.py | 137 from plotly import graph_objs as go unknown
138 return go.Scatter(x=xaxis,
178 from plotly import graph_objs as go unknown
181 go.Scatter(x=threads[tid]["xaxis"],
203 from plotly import graph_objs as go unknown
204 return go.Scatter(x=xaxis,
251 from plotly import graph_objs as go unknown
252 return go.Scatter(x=xaxis,
309 from plotly import graph_objs as go unknown
312 go.Scatter(x=threads[tid]["xaxis"],
[all …]
|
| /qemu/include/hw/s390x/ |
| H A D | event-facility.h | 96 typedef struct GO { struct
107 } QEMU_PACKED GO; argument
115 GO go; member
|
| /qemu/docs/devel/migration/ |
| H A D | postcopy.rst | 115 'packaging' the device data into a blob that's read in one go.
208 will go into a paused state. It'll need a recovery phase to continue a
213 - When network issue occurs, both QEMU will go into **POSTCOPY_PAUSED**
222 Source QEMU will go into **POSTCOPY_RECOVER_SETUP** state trying to
226 channel, they will go into **POSTCOPY_RECOVER** state, some handshake
234 postcopy migration on both sides and go back to **POSTCOPY_ACTIVE**
|
| /qemu/include/system/ |
| H A D | reset.h | 42 * so first all objects go through the enter phase, then all objects
43 * go through the hold phase, and then finally all go through the
|
| /qemu/rust/hw/timer/hpet/src/ |
| H A D | fw_cfg.rs | 41 // SAFETY: all accesses go through these methods, which guarantee in assign_hpet_id()
61 // SAFETY: all accesses go through these methods, which guarantee in update_hpet_cfg()
|
| /qemu/tests/qemu-iotests/tests/ |
| H A D | block-status-cache | 98 # would return a data range, and this would then go into the cache,
103 # will go to the driver, which will return a result that reports the
104 # whole image to be a single data area. This result will then go into
|
| /qemu/docs/system/ |
| H A D | virtio-net-failover.rst | 34 handler and traffic will go through the virtio-net device. On the target
65 devices are present in the configuration, migration will go into this state.
|
| H A D | qemu-manpage.rst | 6 parts of the documentation that go in the manpage as well as the
|
| /qemu/docs/devel/ |
| H A D | stable-process.rst | 11 a four-number version is released, if a single urgent fix needs to go
19 What should go into a stable release?
|
| H A D | tcg-plugins.rst | 91 All code will go through a translation phase although not all
130 when CPUs go into and return from sleep states when waiting for
|
| H A D | submitting-a-patch.rst | 166 for fixing this bug" (they can go below the ``---`` line in the email so
167 they don't go into the final commit message). Make sure the body of the
231 lists too, but all patches must go to qemu-devel, possibly with a Cc:
347 this and happy for it to go into QEMU". The process is modelled after
453 All patches submitted to the QEMU project go through a code review
455 go through a number of iterations before being picked up by
544 line, and this will go into the git changelog when the patch is
|
| /qemu/tests/docker/dockerfiles/debian-microblaze-cross.d/ |
| H A D | build-toolchain.sh | 79 # We won't go through the extra step of building shared libraries
90 # Go back and build the compiler runtime
|
| /qemu/include/hw/pci/ |
| H A D | pcie_regs.h | 5 * Those constants and macros should go to Linux pci_regs.h
6 * Once they're merged, they will go away.
|
| /qemu/rust/ |
| H A D | .gitignore | 2 # artifacts will go to the meson build directory.
|
| /qemu/tests/qapi-schema/ |
| H A D | features-too-many.err | 1 features-too-many.json: In command 'go-fish':
|
| H A D | features-too-many.json | 2 { 'command': 'go-fish',
|
| /qemu/include/qapi/qmp/ |
| H A D | qerror.h | 16 * These macros will go away, please don't use in new code, and do not
|
| /qemu/ |
| H A D | README.rst | 102 automate everything, so you may want to go through the above steps
105 For installation instructions, please go to:
|
| /qemu/docs/interop/ |
| H A D | dbus-vmstate.rst | 9 Upon migration, QEMU will go through the queue of
|
| /qemu/tests/tcg/multiarch/gdbstub/ |
| H A D | interrupt.py | 16 Check that, if thread is resumed, we go back to the same thread when the
|
| /qemu/block/ |
| H A D | graph-lock.c | 198 * decrease and the reader will go to sleep. in bdrv_graph_co_rdlock()
214 * reader_count and go to sleep. in bdrv_graph_co_rdlock()
|
| /qemu/target/arm/ |
| H A D | arm-powerctl.c | 186 /* We are good to go */ in arm_set_cpu_on()
242 /* We are good to go */ in arm_set_cpu_on_and_reset()
|
| /qemu/docs/devel/testing/ |
| H A D | acpi-bits.rst | 116 be made in the appropriate test file. For example, new acpi tests can go
137 Commits (a), (b) and (c) preferably should go under separate commits so that
|
| /qemu/include/user/ |
| H A D | guest-host.h | 41 /* All direct uses of g2h and h2g need to go away for usermode softmmu. */
|