| /qemu/include/hw/misc/ |
| H A D | stm32l4x5_rcc_internals.h | 439 /* Same mapping as: CFGR_SW */
451 /* Same mapping as: PLLCFGR_PLLSRC */
496 /* Same mapping as: BDCR_RTCSEL */
519 /* Same mapping as: CCIPR_USART1SEL */
530 /* Same mapping as: CCIPR_USART2SEL */
541 /* Same mapping as: CCIPR_USART3SEL */
552 /* Same mapping as: CCIPR_UART4SEL */
563 /* Same mapping as: CCIPR_UART5SEL */
574 /* Same mapping as: CCIPR_LPUART1SEL */
585 /* Same mapping as: CCIPR_I2C1SEL */
[all …]
|
| /qemu/docs/specs/ |
| H A D | ppc-spapr-numa.rst | 43 considering that the same resource can have multiple connections to the
60 same performance boundaries are expected to have relative NUMA distance
62 to the same first boundary will have the shortest distance from each
95 P1 and P2 have the same third NUMA level, MOD1: Distance between them = 40
98 distance attributes for the same associativity arrays, as the following
118 In a hypothetical platform where all resources inside the same hardware module
119 is considered to be on the same performance boundary:
133 P1 and P2 belongs to the same first order boundary. The distance between then
206 have to accept that a large array of values will be translated to the same
225 Will both be translated to the same values internally:
[all …]
|
| H A D | rapl-msr.rst | 42 Each core belonging to the same Package reading the MSR_PKG_ENERGY_STATUS (i.e
43 "rdmsr 0x611") will retrieve the same value. The value represents the energy
44 for the whole package. Whatever Core reading it will get the same value and a
81 belongs to the same package will return the same value when accessing the
124 It is important that the socket path is the same as the one
|
| /qemu/target/arm/tcg/ |
| H A D | neon-dp.decode | 21 # VFP/Neon register fields; same as vfp.decode
36 # 3-reg-same grouping:
40 &3same vm vn vd q size
42 @3same .... ... . . . size:2 .... .... .... . q:1 . . .... \
43 &3same vm=%vm_dp vn=%vn_dp vd=%vd_dp
46 &3same vm=%vm_dp vn=%vn_dp vd=%vd_dp q=0
50 # This converts this encoding to the same MO_8/16/32/64 values that the
55 &3same vm=%vm_dp vn=%vn_dp vd=%vd_dp size=%3same_fp_size
57 &3same vm=%vm_dp vn=%vn_dp vd=%vd_dp q=0 size=%3same_fp_size
59 VHADD_S_3s 1111 001 0 0 . .. .... .... 0000 . . . 0 .... @3same
[all …]
|
| /qemu/docs/devel/migration/ |
| H A D | compatibility.rst | 8 target. There are two cases, they are the same version or they are
9 different versions. The easy case is when they are the same version.
29 First of all, migration is only supposed to work if you use the same
31 configuration needs to be the same also on source and destination.
37 start with the trivial ones, QEMU is the same on source and
47 Exactly the same case than the previous one, but for 5.1.
54 we have the same QEMU version in both sides (qemu-5.2) but we are using
62 both sides are the same QEMU and both sides have exactly the same
89 If qemu-5.1 and qemu-5.2 were the same, there will not be any
130 queue. In qemu-5.2 it has the same number of queues as the number of
[all …]
|
| H A D | CPR.rst | 5 VM is migrated to a new QEMU instance on the same host. It is
10 Because QEMU is restarted on the same host, with access to the same
153 on the same host with minimal guest pause time, by preserving guest
158 The user starts new QEMU on the same host as old QEMU, with command-
159 line arguments to create the same machine, plus the ``-incoming``
219 In these examples, we simply restart the same version of QEMU, but
|
| /qemu/hw/watchdog/ |
| H A D | watchdog.c | 50 case WATCHDOG_ACTION_RESET: /* same as 'system_reset' in monitor */ in watchdog_perform_action()
55 case WATCHDOG_ACTION_SHUTDOWN: /* same as 'system_powerdown' in monitor */ in watchdog_perform_action()
60 case WATCHDOG_ACTION_POWEROFF: /* same as 'quit' command in monitor */ in watchdog_perform_action()
64 case WATCHDOG_ACTION_PAUSE: /* same as 'stop' command in monitor */ in watchdog_perform_action()
|
| /qemu/tests/functional/ |
| H A D | test_mem_addr_space.py | 75 access up to a maximum of 64GiB of memory. Rest is the same as the case
93 same options as the failing case above with pse36 cpu feature.
109 Test is same as above but now with pae cpu feature turned on.
111 with the same options as the case above.
127 Pentium2 has 36 bits of addressing, so its same as pentium
213 Same as q35-7.0 AMD case except that here we check that QEMU can
230 Same as q35-7.1 AMD case except that here we check that QEMU can
247 Same parameters as test_phybits_low_tcg_q35_71_amd() but use
292 Same as above but by setting maxram between 976 GiB and 992 Gib,
331 Same as above but here we do not reserve any cxl memory window. Hence,
[all …]
|
| /qemu/tests/qapi-schema/ |
| H A D | doc-good.out | 109 The _one_ {and only}, description on the same line
149 description starts on the same line
150 remainder indented the same
166 description starts on the same line
|
| H A D | doc-good.txt | 47 The _one_ {and only}, description on the same line
146 description starts on the same line remainder indented the same "b"
181 description starts on the same line remainder indented differently
|
| H A D | doc-good.json | 67 # @one: The _one_ {and only}, description on the same line
134 # @i: description starts on the same line
135 # remainder indented the same
157 # @arg2: description starts on the same line
|
| /qemu/docs/ |
| H A D | pci_expander_bridge.txt | 6 PXB is a "light-weight" host bridge in the same PCI domain
31 …- 2 NUMA nodes for the guest, 0 and 1. (both mapped to the same NUMA node in host, but you can and…
48 …It is a regular PCI Device that resides on the piix host-bridge bus and its bus uses the same PCI …
50 The interrupts from devices behind the PXB are routed through this device the same as if it were a
|
| H A D | throttle.txt | 42 It is possible to set limits for both IOPS and bps at the same time,
45 iops-read nor iops-write can be set. The same applies to bps-total and
55 We can do the same using QMP. In this case all these parameters are
167 they all share the same limits.
191 I/O requests on several drives of the same group they will be
198 - I/O limits are shared within the same group, so new values will
200 words: if different limits are applied to members of the same
261 'throttle' block filter. This filter uses the exact same throttling
267 Different filters can use the same group so the limits are shared as
|
| /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
40 # Check whether the thread we're in after the interruption is the same we
47 Test if interrupting the code always lands us on the same thread when
|
| /qemu/target/riscv/insn_trans/ |
| H A D | trans_svinval.c.inc | 28 /* Do the same as sfence.vma currently */
57 /* Do the same as hfence.vvma currently */
70 /* Do the same as hfence.gvma currently */
|
| /qemu/tcg/tci/ |
| H A D | README | 29 the same same numeric values and semantics as used by TCG), and up
70 host and target with same or different endianness.
105 A cross compiled QEMU for i386 host also works with the same basic tests.
|
| /qemu/tests/qemu-iotests/ |
| H A D | 251 | 72 # same reason.
142 # basically the same way, the same warnings as in the previous step
147 # "status_fail_offset_1" in the output is the same as
|
| H A D | 051.out | 276 …ttling.iops-total=5678: 'throttling.iops-total' and its alias 'iops' can't be used at the same time
279 …tling.iops-read=5678: 'throttling.iops-read' and its alias 'iops_rd' can't be used at the same time
282 …ing.iops-write=5678: 'throttling.iops-write' and its alias 'iops_wr' can't be used at the same time
285 …hrottling.bps-total=5678: 'throttling.bps-total' and its alias 'bps' can't be used at the same time
288 …rottling.bps-read=5678: 'throttling.bps-read' and its alias 'bps_rd' can't be used at the same time
291 …ttling.bps-write=5678: 'throttling.bps-write' and its alias 'bps_wr' can't be used at the same time
294 …total-max=5678: 'throttling.iops-total-max' and its alias 'iops_max' can't be used at the same time
297 …ead-max=5678: 'throttling.iops-read-max' and its alias 'iops_rd_max' can't be used at the same time
300 …te-max=5678: 'throttling.iops-write-max' and its alias 'iops_wr_max' can't be used at the same time
303 …s-total-max=5678: 'throttling.bps-total-max' and its alias 'bps_max' can't be used at the same time
[all …]
|
| H A D | 082 | 64 # If the same -o key is specified more than once, the last one wins
77 # Adding the help option to the same -o option
123 # If the same -o key is specified more than once, the last one wins
136 # Adding the help option to the same -o option
182 # If the same -o key is specified more than once, the last one wins
195 # Adding the help option to the same -o option
|
| H A D | 240 | 55 iotests.log('==Attach two SCSI disks using the same block device and the same iothread==')
69 iotests.log('==Attach two SCSI disks using the same block device but different iothreads==')
89 iotests.log('==Attach a SCSI disks using the same block device as a NBD server==')
|
| H A D | 240.out | 18 .==Attach two SCSI disks using the same block device and the same iothread==
35 .==Attach two SCSI disks using the same block device but different iothreads==
56 .==Attach a SCSI disks using the same block device as a NBD server==
|
| H A D | 153.out | 379 == Two devices with the same image (read-only=off - read-only=off) ==
383 == Two devices with the same image (read-only=off - read-only=on) ==
387 == Two devices with the same image (read-only=off - read-only=on,force-share=on) ==
389 == Two devices with the same image (read-only=on - read-only=off) ==
393 == Two devices with the same image (read-only=on - read-only=on) ==
395 == Two devices with the same image (read-only=on - read-only=on,force-share=on) ==
397 == Two devices with the same image (read-only=on,force-share=on - read-only=off) ==
399 == Two devices with the same image (read-only=on,force-share=on - read-only=on) ==
401 == Two devices with the same image (read-only=on,force-share=on - read-only=on,force-share=on) ==
408 == Two devices sharing the same file in backing chain ==
|
| /qemu/docs/system/riscv/ |
| H A D | sifive_u.rst | 32 is also possible to create a 32-bit variant with the same peripherals except
79 and connected to the same subnet, they all have the same MAC address hence
100 same as what is programmed in the hardware. The QEMU one is a simplified
101 version, but it provides the same functionality as the hardware.
207 a 32-bit project to build the 32-bit VxWorks image, and use exact the same
281 Assume U-Boot binaries are put in the same directory as the config file,
358 Use the same command line options to boot the 32-bit U-Boot S-mode image:
|
| /qemu/docs/system/devices/ |
| H A D | ivshmem.rst | 18 If desired, interrupts can be sent between guest VMs accessing the same
34 allows guests using the same server to communicate via interrupts.
47 At most one of the devices sharing the same memory can be master. The
|
| /qemu/tests/uefi-test-tools/UefiTestToolsPkg/Include/Guid/ |
| H A D | BiosTablesTest.h | 58 // table, in 8-byte little endian representation. Rsdp20 is the same, for the
70 // the SMBIOS 3.0 (64-bit) Entry Point Structure from the same specification,
71 // in the same representation. Each of these fields may be zero
|