| /qemu/hw/misc/ |
| H A D | mac_via.c | 59 * as CHRP on SE/30,II,IIx,IIcx,IIci.
60 * on IIfx, "0 means an active request"
65 * signal from port B of the SCC appear on
67 * [Macintosh Family] On the SE/30, this
70 * on II,IIx,IIcx,IIci,IIfx this is a bit
77 * state-control line SEL" on all but IIfx
80 * [Macintosh Family] On SE/30,II,IIx,IIcx
82 * map in the address decoders as it is on
85 * On the IIci,IIfx it is another bit of the
90 * on the PA7 input pin (CHRP). Output.
[all …]
|
| /qemu/docs/system/ |
| H A D | target-riscv.rst | 13 CPUs are generally built into "system-on-chip" (SoC) designs created by
30 operating system or firmware images intended to run on one machine
31 will not run at all on any other. This is often surprising for new
36 If you already have a system image or a kernel that works on hardware
40 will almost certainly not boot on QEMU. (You might be able to
42 boots on a system that QEMU does emulate.)
49 need to compile Linux with a suitable configuration for running on
|
| H A D | target-arm.rst | 16 are generally built into "system-on-chip" (SoC) designs created by
40 operating system or firmware images intended to run on one machine
41 will not run at all on any other. This is often surprising for new
46 If you already have a system image or a kernel that works on hardware
50 will almost certainly not boot on QEMU. (You might be able to
52 boots on a system that QEMU does emulate.)
59 need to compile Linux with a suitable configuration for running on
|
| H A D | authz.rst | 12 finer grained authorization on clients post-authentication.
30 This is done by setting the property ``verify-peer=yes`` on the
43 provided. The format of this username will vary depending on the choice
61 based on an exact match against a single identity. This is useful when it is
123 it on the command line will require use of the JSON syntax for ``-object``.
129 This is a variant on the previous driver that allows for a more dynamic
167 The object can be created on the command line using
172 filename=/etc/qemu/myvm-vnc.acl,refresh=on
218 On the command line it can be created using
236 The property to set in the network service will vary depending on the type of
|
| /qemu/tests/qemu-iotests/ |
| H A D | 216 | 4 # Copy-on-read tests using a COR filter node
31 log('=== Copy-on-read across nodes ===')
34 # The old copy-on-read mechanism without a filter node cannot request
67 # vm.add_drive_raw('if=none,node-name=node0,copy-on-read=on,driver=raw,' \
78 driver='copy-on-read',
82 'driver': 'copy-on-read',
|
| H A D | 042.out | 5 No errors were found on the image.
8 No errors were found on the image.
11 No errors were found on the image.
14 No errors were found on the image.
|
| H A D | 182 | 52 _launch_qemu -drive file=$TEST_IMG,if=none,id=drive0,file.locking=on \
58 -drive file=$TEST_IMG,if=none,id=drive0,file.locking=on \
90 'locking': 'on'
116 'locking': 'on'
151 _launch_qemu -drive file=$TEST_IMG,if=none,file.locking=on
159 # When quitting qemu, it will try to drop its locks on the test image.
161 # However, that is not fatal, so it should just move on.
|
| H A D | 257 | 258 - on-success: This is the "incremental" style mode. Bitmaps are
259 synchronized to what was copied out only on success.
269 - bitmap: Backups based on bitmap manifest.
374 if ((bsync_mode == 'on-success' and not failure) or
430 # don't rely on this to be true!
434 # Always keep the last backup on success or when using 'always'
481 None: ['on-success', 'always', 'never', None],
482 'bitmap404': ['on-success', 'always', 'never', None],
486 None: ['on-success', 'always', 'never', None],
487 'bitmap404': ['on-success', 'always', 'never', None],
[all …]
|
| H A D | 026 | 52 # count on error.
85 for once in on off; do
108 # l2_load is not called on allocation, so issue a second write
143 for once in on off; do
183 for once in on off; do
214 once = "on"
224 echo === Avoid freeing preallocated zero clusters on failure ===
231 once = "on"
|
| /qemu/contrib/ivshmem-server/ |
| H A D | ivshmem-server.h | 22 * qemu is able to transform an event on a eventfd into a PCI MSI-x
86 * Returns: 0 on success, or a negative value on error
99 * Returns: 0 on success, or a negative value on error
141 * Returns: 0 on success, or a negative value on error
157 * Dump information of this ivshmem server and its peers on stdout
|
| /qemu/hw/ide/ |
| H A D | Kconfig | 10 depends on IDE_BUS
14 depends on PCI
20 depends on ISA_BUS
54 depends on PCI
|
| /qemu/tests/functional/ |
| H A D | test_ppc64_hv.py | 22 # that on the machine then run a QEMU guest inside it in KVM mode,
24 # QEMU packages are downloaded and installed on each test. That's not a
52 cmd = "xorriso -osirrox on -indev %s -cpx %s %s" % (iso, path, filename)
110 '-machine pseries,x-vof=on,accel=kvm '
113 '-drive file=/dev/nvme0n1,format=raw,readonly=on '
132 self.vm.add_args("-machine", "x-vof=on,cap-nested-hv=on")
144 self.vm.add_args("-machine", "x-vof=on,cap-nested-hv=on,cap-ccf-assist=off")
|
| /qemu/include/standard-headers/linux/ |
| H A D | vmclock-abi.h | 13 * ±50PPM, or 4 seconds a day). This frequency also varies over time on the
18 * its accuracy is limited by the precision of the NTP synchronization on the
21 * So any calibration (NTP, PTP, etc.) which the guest has done on the source
22 * host before migration is invalid, and needs to be redone on the new host.
37 * and wait for NTP to recover. This mode does, of course, rely on the
53 * device with the CID "VMCLOCK", modelled on the "VMGENID" device except for
84 * counter is disrupted, for example on live migration. This lets
110 * In particular, a timestamp based on a counter reading taken
113 * period fields, shall never be later than a timestamp based on
143 * This field is based on the VIRTIO_RTC_LEAP_xxx values as defined
|
| /qemu/include/io/ |
| H A D | channel.h | 92 HANDLE event; /* For use with GSource on Win32 */
212 * @nfds: pointer filled with number of elements in @fds on return
234 * to call close() on each file descriptor and to
235 * call g_free() on the array pointer in @fds.
241 * Returns: the number of bytes read, or -1 on error,
285 * Returns: the number of bytes sent, or -1 on error,
320 * occurs without data, or -1 on error
347 * Returns: 0 if all bytes were read, or -1 on error
372 * Returns: 0 if all bytes were written, or -1 on error
456 * without data, or -1 on error
[all …]
|
| /qemu/docs/system/devices/ |
| H A D | virtio-pmem.rst | 8 on regular (i.e non-NVDIMM) storage.
20 NVDIMM emulation on regular (i.e. non-NVDIMM) host storage does not
23 on non-NVDIMM host storage.
28 A virtio pmem device backed by a memory-backend-file can be created on
55 (qemu) object_add memory-backend-file,id=mem2,share=on,mem-path=virtio_pmem2.img,size=4G
61 Guest data persistence on non-NVDIMM requires guest userspace applications
|
| /qemu/docs/system/arm/ |
| H A D | stm32.rst | 9 The STM32F1 series is based on ARM Cortex-M3 core. The following machines are
10 based on this chip :
14 The STM32F2 series is based on ARM Cortex-M3 core. The following machines are
15 based on this chip :
19 The STM32F4 series is based on ARM Cortex-M4F core, as well as the STM32L4
21 The following machines are based on this ARM Cortex-M4F chip :
|
| H A D | xlnx-versal-virt.rst | 5 (System on Chip) that combine traditional hardened CPUs and I/O
32 - OCM (256KB of On Chip Memory)
33 - XRAM (4MB of on chip Accelerator RAM)
44 ``-m`` argument. If a DTB is provided on the command line then QEMU will
67 When loading an OS, we turn on QEMU's PSCI implementation with SMC
124 Boot Linux as DOM0 on Xen via U-Boot:
152 Boot Linux as Dom0 on Xen via ARM Trusted Firmware and U-Boot:
230 on this Xilinx Versal Virt board.
234 Versal CANFD controller is developed based on SocketCAN and QEMU CAN bus
238 To connect both CANFD0 and CANFD1 on the same bus:
[all …]
|
| H A D | sx1.rst | 7 - Texas Instruments OMAP310 System-on-chip (ARM925T core)
12 - On-chip LCD controller
14 - On-chip Real Time Clock
18 - Three on-chip UARTs
|
| /qemu/storage-daemon/ |
| H A D | qemu-storage-daemon.c | 90 " [,cache.direct=on|off][,cache.no-flush=on|off]\n" in help()
91 " [,read-only=on|off][,auto-read-only=on|off]\n" in help()
92 " [,force-share=on|off][,detect-zeroes=on|off|unmap]\n" in help()
103 " [,writable=on|off][,bitmap=<name>]\n" in help()
109 " [,growable=on|off][,writable=on|off][,allow-other=on|off|auto]\n" in help()
115 " addr.type=unix,addr.path=<socket-path>[,writable=on|off]\n" in help()
120 " addr.type=fd,addr.str=<fd>[,writable=on|off]\n" in help()
128 " ,name=<vduse-name>[,writable=on|off]\n" in help()
136 " --monitor [chardev=]name[,mode=control][,pretty[=on|off]]\n" in help()
234 * in the order they are given on the command lines. This means that things in process_options()
|
| /qemu/docs/ |
| H A D | qdev-device-use.txt | 3 === Specifying Bus and Address on Bus ===
9 A device typically has a device address on its parent bus. For buses
23 Example: device i440FX-pcihost is on the root bus, and provides a PCI
53 to use, and the drive's address on that bus. Details depend on TYPE.
75 Additionally, readonly=on goes into HOST-OPTS.
99 disk on it:
120 notify. It can be set to on (default) or off.
140 (RMB) bit. USB thumbdrives usually set removable=on, while USB hard
172 The appropriate DEVNAME depends on the machine type. For type "pc":
212 -chardev socket,host=HOST,port=PORT,OPTS...,telnet=on
[all …]
|
| /qemu/docs/about/ |
| H A D | removed-features.rst | 66 use ``-nic ...`` (e.g. for on-board NICs) or use ``-netdev ...,id=n`` together
93 ``-device ...,netdev=x``), or ``-nic user,bootp=/some/file`` (for on-board NICs).
104 (for on-board NICs). The new syntax allows different settings to be provided
112 ``-device ...,netdev=x``), or ``-nic user,smb=/some/dir`` (for on-board NICs).
176 chunk on the host side (like bind it to a host node, setting bind policy, ...),
181 means to actually manage node RAM on the host side. Use parameter ``memdev``
216 ``-machine enforce-config-section=on|off`` (removed in 5.2)
220 ``-global migration.send-configuration={on|off}`` option.
230 The ``-realtime mlock=on|off`` argument has been replaced by the
231 ``-overcommit mem-lock=on|off`` argument.
[all …]
|
| /qemu/include/qemu/ |
| H A D | memalign.h | 16 * Allocate memory on an aligned boundary (i.e. the returned
19 * On success, returns allocated memory; on failure, returns NULL.
43 * subtle bugs on Windows hosts.)
57 * Analog of g_autofree, but qemu_vfree is called on cleanup instead of g_free.
|
| /qemu/target/arm/ |
| H A D | arm-powerctl.c | 67 /* Initialize the cpu we are turning on */ in arm_set_cpu_on_async_work()
130 "[ARM]%s: CPU %" PRId64 " is already on\n", in arm_set_cpu_on()
161 * If another CPU has powered the target on we are in the state in arm_set_cpu_on()
162 * ON_PENDING and additional attempts to power on the CPU should in arm_set_cpu_on()
168 "[ARM]%s: CPU %" PRId64 " is already powering on\n", in arm_set_cpu_on()
195 /* Initialize the cpu we are turning on */ in arm_set_cpu_on_and_reset_async_work()
221 "[ARM]%s: CPU %" PRId64 " is already on\n", in arm_set_cpu_on_and_reset()
227 * If another CPU has powered the target on we are in the state in arm_set_cpu_on_and_reset()
228 * ON_PENDING and additional attempts to power on the CPU should in arm_set_cpu_on_and_reset()
234 "[ARM]%s: CPU %" PRId64 " is already powering on\n", in arm_set_cpu_on_and_reset()
|
| /qemu/util/ |
| H A D | userfaultfd.c | 65 * Returns: 0 on success, negative value in case of an error
205 * Returns 0 on success, negative value in case of error
211 * @dont_wake: do not wake threads waiting on wr-protected page
221 /* DONTWAKE is meaningful only on protection release */ in uffd_change_protection()
243 * Returns 0 on success, -errno in case of an error
249 * @dont_wake: do not wake threads waiting on missing page
277 * Returns 0 on success, -errno in case of an error
282 * @dont_wake: do not wake threads waiting on missing page
304 * uffd_wakeup: wake up threads waiting on page UFFD-managed page fault resolution
306 * Wake up threads waiting on any page/pages from the designated range.
[all …]
|
| /qemu/qapi/ |
| H A D | block-core.json | 81 # @lazy-refcounts: on or off; only valid for compat >= 1.1
281 # @actual-size: actual size on disk in bytes of the image
484 # @backing_file: the name of the backing file (for copy-on-write)
490 # are on the migration source instance after migration completes and on the
611 # @persistent: true if the bitmap was stored on disk, is scheduled to
612 # be stored on disk, or both. (since 4.0)
713 # supports it and the VM is configured to stop on errors
733 # The size requirements depend on the new image file format. File
800 # "detect_zeroes": "on",
954 # @rd_total_time_ns: Total time spent on reads in nanoseconds
[all …]
|