| /qemu/docs/system/ |
| H A D | target-riscv.rst | 11 several different machines. The reason we support so many is that
14 many different companies with different devices, and these SoCs are
41 extract the file system and use that with a different kernel which
78 When using the ``sifive_u`` or ``virt`` machine there are three different
|
| H A D | target-arm.rst | 14 nearly fifty different machines. The reason we support so many is that
17 many different companies with different devices, and these SoCs are
23 implement so many different machines.
51 extract the filesystem and use that with a different kernel which
|
| H A D | confidential-guest-support.rst | 11 These mechanisms have different names and different modes of
|
| H A D | target-openrisc.rst | 11 this reason QEMU does not need to support many different boards to support the
37 different kernel which boots on a system that QEMU does emulate.)
|
| /qemu/docs/devel/migration/ |
| H A D | compatibility.rst | 9 different versions. The easy case is when they are the same version.
10 The difficult one is when they are different versions.
12 There are two things that are different, but they have very similar
71 different. Notice also that the machine type needs to be pc-5.1,
94 we have a problem when we try to migrate between different QEMU
117 version. But if we want a different value for a previous version, we
220 A device with different features on both sides
225 different features on both sides of the migration. That can be
226 because the devices are different, because the kernel driver of both
227 devices have different features, whatever.
[all …]
|
| /qemu/tests/vm/ |
| H A D | conf_example_aarch64.yml | 13 # Password for root user can be different from guest.
25 # 4 NUMA nodes and 2 different NUMA distances.
47 # To install a different set of packages, provide a command to issue
|
| H A D | conf_example_x86.yml | 13 # Password for root user can be different from guest.
26 # 4 NUMA nodes and 2 different NUMA distances.
|
| /qemu/include/system/ |
| H A D | confidential-guest-support.h | 47 * different mechanisms have different interdependencies requiring
48 * initialization in different places, often in arch or machine
|
| H A D | host_iommu_device.h | 62 * Different types of host devices (e.g., VFIO or VDPA device) or devices
63 * with different backend (e.g., VFIO legacy container or IOMMUFD backend)
64 * will have different implementations of the HostIOMMUDeviceClass.
|
| /qemu/hw/xen/ |
| H A D | xen_pt_graphics.c | 300 * In real world different GPU should have different PCH. But actually
301 * the different PCH DIDs likely map to different PCH SKUs. We do the
302 * same thing for the GPU. For PCH, the different SKUs are going to be
303 * all the same silicon design and implementation, just different
308 * Most of these different PCH features probably don't matter to the
|
| /qemu/docs/interop/ |
| H A D | dbus.rst | 46 different trust level.
53 helpers as different UID from QEMU and set appropriate policies.
55 Depending on the use case, you may choose different scenarios:
|
| /qemu/docs/devel/ |
| H A D | kconfig.rst | 9 time different targets can share large amounts of code. For example,
11 card, even though the boards use different PCI host bridges, and they
12 can run the same code to emulate a SCSI disk while using different
14 disk to their guests, but with three different virtio guest interfaces.
113 if more than one default is present, they will have different
139 declares its dependencies in different ways:
|
| /qemu/scripts/simplebench/ |
| H A D | img_bench_templater.py | 58 Use the following syntax in the template to create the various different test
61 column templating: {var1|var2|...} - test will use different values in
62 different columns. You may use several {} constructions in the test, in this
|
| /qemu/docs/system/devices/ |
| H A D | canokey.rst | 16 For different platforms, CanoKey has different implementations,
60 If you want to install libcanokey-qemu in a different place,
|
| H A D | igb.rst | 26 with a different operating system other than DPDK, Linux, and Windows or if you
32 Using igb should be nothing different from using another network device. See
|
| H A D | keyboard.rst | 18 select keyboard layout, giving up to 64 different layouts. Not all
32 keytable file is used for different dip switch settings. The information
|
| /qemu/tests/qemu-iotests/ |
| H A D | 172 | 99 # different index, you get both of them. However, as soon as you use any
100 # '-device floppy', even to a different slot, the default drive is disabled.
215 echo === Try passing different drive size with image ===
222 echo === Try passing different block sizes ===
|
| H A D | 048 | 74 # Compare images with different size
86 # Compare images with different content
|
| /qemu/tests/tcg/arm/ |
| H A D | commpage.c | 6 * between different CPUs with potentially different capabilities. It
|
| /qemu/tests/migration-stress/guestperf/ |
| H A D | comparison.py | 58 # Looking at effect of starting post-copy at different
72 # Looking at effect of auto-converge with different
163 # different compression algorithms
|
| /qemu/include/exec/ |
| H A D | memattrs.h | 22 * confusion if different parts of QEMU used the same bit for
23 * different semantics.
|
| /qemu/include/hw/cpu/ |
| H A D | cluster.h | 34 * Arm big.LITTLE system) they should be in different clusters. If the CPUs do
36 * controller processor) they should be in different clusters.
|
| /qemu/scripts/ |
| H A D | archive-source.sh | 6 # export the source files, in order to be built in a different environment,
28 # different to the host OS.
|
| /qemu/docs/system/arm/ |
| H A D | xlnx-versal-virt.rst | 13 different parts with different speed grades, amounts of PL and
196 To use a different index value, N, from default of 0, add:
214 To use a different index value, N, from default of 1, add:
|
| H A D | vexpress.rst | 48 - QEMU will default to creating one CPU unless you pass a different
70 recommended (and also useful if you build a lot of different targets).
|