/qemu/rust/qemu-api/src/ |
H A D | prelude.rs | 7 pub use crate::bitops::IntegerExt; 9 pub use crate::cell::BqlCell; 10 pub use crate::cell::BqlRefCell; 12 pub use crate::errno; 14 pub use crate::qdev::DeviceMethods; 16 pub use crate::qom::InterfaceType; 17 pub use crate::qom::IsA; 18 pub use crate::qom::Object; 19 pub use crate::qom::ObjectCast; 20 pub use crate::qom::ObjectDeref; [all …]
|
H A D | assertions.rs | 30 /// # use qemu_api::assert_same_type; 31 /// # use std::ops::Deref; 39 /// # use qemu_api::assert_same_type; 64 /// # use qemu_api::assert_field_type; 75 /// # use qemu_api::assert_field_type; 110 /// # use qemu_api::assert_match; 139 /// # use qemu_api::static_assert; 144 /// # use qemu_api::static_assert;
|
H A D | callbacks.rs | 5 use std::{mem, ptr::NonNull}; 17 /// parameters and resolved at compile-time. A typical use is a function 23 /// but they only have a single opaque that they can use. The `FnCall` 24 /// trait makes it possible to use that opaque for `self` or any other 58 /// # use qemu_api::callbacks::FnCall; 74 /// # use qemu_api::callbacks::FnCall; 85 /// # use qemu_api::callbacks::FnCall; 100 /// # use qemu_api::callbacks::FnCall; 122 /// function type, which can be used to catch incorrect use of `()` 128 /// # use qemu_api::callbacks::FnCall; [all …]
|
H A D | errno.rs | 10 use std::{convert::TryFrom, io, io::ErrorKind}; 23 use ErrorKind::*; in from() 52 use ErrorKind::*; in from() 105 use super::Errno; 171 use traits::{GetErrno, MergeErrno}; 179 /// # use qemu_api::errno::into_io_result; 180 /// # use std::io::ErrorKind; 195 /// # use qemu_api::errno::into_io_result; 207 /// # use qemu_api::errno::into_neg_errno; 208 /// # use std::io::{self, ErrorKind}; [all …]
|
/qemu/docs/system/ |
H A D | cpu-models-mips.rst.inc | 9 The following CPU models are supported for use on MIPS32 hosts. 10 Administrators / applications are recommended to use the CPU model that 11 matches the generation of the host CPUs in use. In a deployment with a 13 compatibility is required, use the newest CPU model that is compatible 41 The following CPU models are supported for use on MIPS64 hosts. 42 Administrators / applications are recommended to use the CPU model that 43 matches the generation of the host CPUs in use. In a deployment with a 45 compatibility is required, use the newest CPU model that is compatible 85 The following CPU models are supported for use on nanoMIPS hosts. 86 Administrators / applications are recommended to use the CPU model that [all …]
|
H A D | security.rst | 13 QEMU supports many different use cases, some of which have stricter security 18 Virtualization Use Case 21 The virtualization use case covers cloud and virtual private server (VPS) 23 use cases rely on hardware virtualization extensions to execute guest code 36 real-world use cases and treated as security bugs if this is the case. 38 Non-virtualization Use Case 41 The non-virtualization use case covers emulation using the Tiny Code Generator 43 the non-virtualization use case should meet the same security requirements as 44 the virtualization use case. However, for historical reasons much of the 45 non-virtualization use case code was not written with these security [all …]
|
H A D | gdb.rst | 13 In order to use gdb, launch QEMU with the ``-s`` and ``-S`` options. 17 TCP port to use or to use something other than TCP for the gdbstub 18 connection, use the ``-gdb dev`` option instead of ``-s``. See 35 Then you can use gdb normally. For example, type 'c' to launch the 40 Here are some useful tips in order to use gdb on system code: 42 1. Use ``info reg`` to display all the CPU registers. 44 2. Use ``x/10i $eip`` to display the code at the PC position. 46 3. Use ``set architecture i8086`` to dump 16 bit code. Then use 140 An alternate method for connecting gdb to the QEMU gdbstub is to use 146 instruct the gdbserver to use that device: [all …]
|
H A D | qemu-block-drivers.rst.inc | 20 space. Use ``qemu-img info`` to know the real size used by the 37 QEMU image format, the most versatile format. Use it to have smaller 47 Determines the qcow2 version to use. ``compat=0.10`` uses the 69 use to unlock the LUKS key slot is given by the ``encrypt.key-secret`` 89 The use of this is no longer supported in system emulators. Support only 106 Name of the encryption mode to use. Currently defaults to ``xts``. 116 Name of the hash algorithm to use with the initialization vector generator 121 Name of the hash algorithm to use for PBKDF algorithm 126 Amount of time, in milliseconds, to use for PBKDF algorithm per key slot. 234 The use of this is no longer supported in system emulators. Support only [all …]
|
H A D | target-arm.rst | 6 QEMU can emulate both 32-bit and 64-bit Arm CPUs. Use the 8 You can use either ``qemu-system-arm`` or ``qemu-system-aarch64`` 18 then built into machines which can vary still further even if they use 36 model you want to use with the ``-M`` or ``--machine`` option; 49 use that board model. If it is not listed, then unfortunately your image 51 extract the filesystem and use that with a different kernel which 56 disk, etc., and just want to run Linux, the best option is to use the 58 real hardware and is designed for use in virtual machines. You'll
|
H A D | target-riscv.rst | 6 QEMU can emulate both 32-bit and 64-bit RISC-V CPUs. Use the 15 then built into machines which can vary still further even if they use 26 model you want to use with the ``-M`` or ``--machine`` option; 39 use that board model. If it is not listed, then unfortunately your image 41 extract the file system and use that with a different kernel which 46 disk, etc., and just want to run Linux, the best option is to use the 48 real hardware and is designed for use in virtual machines. You'll
|
H A D | target-openrisc.rst | 21 want to use with the ``-M`` or ``--machine`` option; the default machine is 28 the kernel. The kernel can then use this to configure itself for the machine. 34 help`` output. If it is listed, then you can probably use that board model. If 36 on QEMU. (You might be able to extract the filesystem and use that with a 41 and just want to run Linux, the best option is to use the ``virt`` board. This 43 use in virtual machines. You'll need to compile Linux with a suitable
|
/qemu/docs/devel/ |
H A D | style.rst | 9 Please use the script checkpatch.pl in the scripts directory to check 34 * The confusion surrounding 'use tabs to indent, spaces to justify' is gone. 38 to use tab stops of eight positions. 94 that use long function or symbol names. If wrapping the line at 80 columns 105 xterms and use vi in all of them. The best way to punish them is to 126 A number of short naming conventions exist for variables that use 137 Wrapped version of standard library or GLib functions use a ``qemu_`` 159 workarounds we use the suffix ``_compat``. These are generally not 207 of blocks. To avoid accidental re-use it is permissible to declare 242 We use traditional C-style /``*`` ``*``/ comments and avoid // comments. [all …]
|
H A D | rust.rst | 24 However, QEMU's build system also tries to be easy to use for people who 31 * it is also possible to use ``cargo`` for common Rust-specific coding 56 If you are going to use ``cargo`` repeatedly, ``pyvenv/bin/meson devenv`` 66 As shown above, you can use the ``--tests`` option as usual to operate on test 87 * ``&raw`` (stable in 1.82.0). Use ``addr_of!`` and ``addr_of_mut!`` instead, 94 * referencing statics in constants (stable in 1.83.0). For now use a const 101 before QEMU can use them. For now, there is special code in 141 - *complete*: ready for use in new devices; if applicable, the API supports the 144 - *stable*: ready for production use, the API is safe and should not undergo 268 Because of this, QOM objects should almost always use ``&self`` instead [all …]
|
/qemu/docs/about/ |
H A D | removed-features.rst | 57 Use ``-device ...,drive=dr,serial=r,bios-chs-trans=t,addr=a`` instead 66 use ``-nic ...`` (e.g. for on-board NICs) or use ``-netdev ...,id=n`` together 69 vlan did), use ``-nic hubport,hubid=x,...`` or 75 Use ``-machine kernel_irqchip=off`` instead. 80 Use ``-global kvm-pit.lost_tick_policy=discard`` instead. 131 Use ``-no-user-config`` instead. 136 Use ``-rtc driftfix=slew`` instead. 181 means to actually manage node RAM on the host side. Use parameter ``memdev`` 195 Use ``memdev`` with *memory-backend-ram* backend or ``mem`` (if 200 memory devices (pc|nv-dimm) are present use ``info memory-device`` and subtract [all …]
|
H A D | deprecated.rst | 23 should exclusively use a non-deprecated machine type, with use of the most 100 Use argument ``id`` instead. 105 Use argument ``id`` instead. 110 Use argument ``id`` instead. 115 Use argument ``id`` instead. 120 Use argument value ``null`` instead. 125 Use arguments ``base-node`` and ``top-node`` instead. 130 Use the more generic commands ``block-export-add`` and ``block-export-del`` 138 deprecated. Use ``members`` instead. 143 Use ``blockdev-backup`` in combination with ``blockdev-add`` instead. [all …]
|
/qemu/ |
H A D | qemu-options.hx | 3 HXCOMM Use DEFHEADING() to define headings in both help text and rST. 39 " memory-encryption=@var{} memory encryption object to use (default=none)\n" 50 Select the emulated machine by name. Use ``-machine help`` to list 102 Memory encryption object to use. The default is none. 116 To use the cpr-transfer migration mode, you must set aux-ram-share=on. 120 Allows to use a memory backend as main RAM. 131 * as backend id one shall use value of 'default-ram-id', advertised by 135 use ``x-use-canonical-path-for-ramblock-id=off`` backend option 141 -object memory-backend-ram,id=pc.ram,size=512M,x-use-canonical-path-for-ramblock-id=off 224 " select accelerator (kvm, xen, hvf, nvmm, whpx or tcg; use 'help' for a list)\n" [all …]
|
/qemu/pc-bios/dtb/ |
H A D | petalogix-ml605.dts | 68 xlnx,dcache-use-fsl = < 0x00 >; 69 xlnx,dcache-use-writeback = < 0x01 >; 74 xlnx,ecc-use-ce-exception = < 0x00 >; 93 xlnx,icache-use-fsl = < 0x00 >; 116 xlnx,use-barrel = < 0x01 >; 117 xlnx,use-branch-target-cache = < 0x00 >; 118 xlnx,use-dcache = < 0x01 >; 119 xlnx,use-div = < 0x01 >; 120 xlnx,use-ext-brk = < 0x01 >; 121 xlnx,use-ext-nm-brk = < 0x01 >; [all …]
|
H A D | petalogix-s3adsp1800.dts | 59 xlnx,dcache-use-fsl = <0x01>; 75 xlnx,icache-use-fsl = <0x01>; 95 xlnx,use-barrel = <0x01>; 96 xlnx,use-dcache = <0x01>; 97 xlnx,use-div = <0x00>; 98 xlnx,use-ext-brk = <0x01>; 99 xlnx,use-ext-nm-brk = <0x01>; 100 xlnx,use-extended-fsl-instr = <0x00>; 101 xlnx,use-fpu = <0x00>; 102 xlnx,use-hw-mul = <0x01>; [all …]
|
/qemu/pc-bios/ |
H A D | edk2-licenses.txt | 6 Redistribution and use in source and binary forms, with or without 20 license to make, have made, use, offer to sell, sell, import, and otherwise 48 SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 51 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 112 Redistribution and use in source and binary forms, with or without 130 LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 133 ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 146 use in the source control commit log. 183 Your change description should use the standard format for a 241 ("DOCUMENTATION"), INFORMATION AND/OR OTHER MATERIALS FOR USE IN THE [all …]
|
/qemu/scripts/simplebench/ |
H A D | bench-backup.py | 54 raise ValueError("Can't use 'nbd' label for both src and dst") 130 x_perf['use-copy-range'] = True 132 x_perf['use-copy-range'] = False 177 (LABEL:PATH|LABEL|PATH)[,max-workers=N][,use-copy-range=(on|off)][,mirror] 182 use-copy-range set x-perf.use-copy-range of backup job 183 mirror use mirror job instead of backup''', 197 default port 10809). Use it in tests, label is "nbd" 203 Use compressed backup. It automatically means 207 Use test-source.qcow2 images as sources instead of 211 direct: default, use O_DIRECT and aio=native [all …]
|
/qemu/qapi/ |
H A D | audio.json | 19 # @mixing-engine: use QEMU's mixing engine to mix all streams inside 24 # @fixed-settings: use fixed settings for host input/output. When 28 # @frequency: frequency to use when using fixed settings (default 33 # @voices: number of voices to use (default 1) 35 # @format: sample format to use when using fixed settings (default 94 # @dev: the name of the ALSA device to use (default 'default') 98 # @try-poll: attempt to use poll mode, falling back to non-polling 138 # @dev: the name of the sndio device to use (default 'default') 212 # @client-name: the client name to use. The server will modify this 222 # @exact-name: use the exact name requested otherwise JACK [all …]
|
/qemu/include/qapi/ |
H A D | error.h | 20 * - Functions that use Error to report errors have an Error **errp 35 * for errors, it must use ERRP_GUARD(). 59 * This may require use of ERRP_GUARD(); more on that below. 147 * But when all you do with the error is pass it on, please use 167 * This is rarely needed. When @err is a local variable, use of 206 * = Why, when and how to use ERRP_GUARD() = 208 * Without ERRP_GUARD(), use of the @errp parameter is restricted: 214 * To use ERRP_GUARD(), add it right at the beginning of the function. 223 * To convert a function to use ERRP_GUARD(): 229 * beginning of the function. This makes @errp safe to use. [all …]
|
/qemu/tests/qtest/ |
H A D | tpm-tis-util.c | 86 /* request use of locality */ in tpm_tis_test_check_access_reg() 120 /* request use of locality */ in tpm_tis_test_check_access_reg_seize() 136 /* try to request use from 'l' */ in tpm_tis_test_check_access_reg_seize() 140 * requesting use from 'l' was not possible; in tpm_tis_test_check_access_reg_seize() 185 * higher localities can 'seize' access but not 'request use'; in tpm_tis_test_check_access_reg_seize() 189 /* try to 'request use' from 'l' */ in tpm_tis_test_check_access_reg_seize() 193 * requesting use from 'l' was not possible; we should see in tpm_tis_test_check_access_reg_seize() 313 /* request use of locality */ in tpm_tis_test_check_access_reg_release() 320 /* request use of all other localities */ in tpm_tis_test_check_access_reg_release() 326 * request use of locality 'l' -- we MUST see REQUEST USE and in tpm_tis_test_check_access_reg_release() [all …]
|
/qemu/include/hw/core/ |
H A D | sysemu-cpu-ops.h | 38 * and the associated memory transaction attributes to use for the 40 * CPUs which use memory transaction attributes should implement this 46 * @asidx_from_attrs: Callback to return the CPU AddressSpace to use for 82 * Non-configurable CPUs can use the default implementation of this method. 90 * Do not use in new targets, use #DeviceClass::vmsd instead.
|
/qemu/docs/system/devices/ |
H A D | usb.rst | 26 need to use the bus= parameter when adding USB devices. 34 devices. The companion controller setup is more convenient to use 49 You can use the standard ``-device`` switch to add a EHCI controller to 83 you, which you can use like this: 89 Then use ``bus=ehci.0`` to assign your USB devices to that bus. 153 i.e. for three devices you must use 0+1+2. The 0+1+5 numbering from the 181 normally use BrlAPI to display the braille output on a BRLTTY-supported 188 or alternatively, use the following equivalent shortcut: 242 specify some unique id which you can use to refer to the device. 243 You can then use ``device_del`` to unplug the device later. [all …]
|