/qemu/docs/devel/ |
H A D | vfio-iommufd.rst | 7 With the introduction of iommufd, the Linux kernel provides a generic 12 To support both interfaces in the QEMU VFIO device, introduce a base container 90 Interactions with the ``/dev/iommu`` are abstracted by a new iommufd 94 be linked with an iommufd object. It gets a new optional property 103 Note the ``/dev/iommu`` and VFIO cdev can be externally opened by a 104 management layer. In such a case the fd is passed, the fd supports a 105 string naming the fd or a number, for example: 146 BAR region yet. Below warning shows for assigned PCI device, it's not a bug. 156 ``vfio-pci`` device checks sysfsdev property to decide if backend is a mdev. 158 like a real PCI device. There is an error as below if user wants to enable
|
H A D | blkverify.txt | 5 This document describes how to use the blkverify protocol to test that a block 10 of the executable. Other times obscure errors are raised by a program inside 23 The "raw" device is a raw image, a flat file, that has identical starting 25 read/write operations correctly and not corrupt data. It can be used as a 28 After a mirrored read operation completes, blkverify will compare the data and 58 $ ./qemu-io -c 'read 0 512' blkverify:a.img:b.img 61 A more realistic scenario is verifying the installation of a guest OS:
|
/qemu/docs/system/arm/ |
H A D | sabrelite.rst | 4 Boundary Devices SABRE Lite i.MX6 Development Board is a low-cost development 29 Please note above list is a complete superset the QEMU SABRE Lite machine can 30 support. For a normal use case, a device tree blob that represents a real world 31 SABRE Lite board, only exposes a subset of devices to the guest software. 37 for loading a Linux kernel, U-Boot bootloader or ELF executable. 42 Linux mainline v5.10 release is tested at the time of writing. To build a Linux 67 U-Boot mainline v2020.10 release is tested at the time of writing. To build a
|
/qemu/docs/specs/ |
H A D | acpi_hest_ghes.rst | 79 "error_status_address" fields of the HEST table with a pointer to the 83 "read_ack_register" fields of the HEST table with a pointer to the 87 addresses in the "error_block_address" fields with a pointer to the 90 (8) QEMU defines a third and write-only fw_cfg blob which is called 93 blob contains a 8-byte entry. QEMU generates a single WRITE_POINTER command 97 (9) When QEMU gets a SIGBUS from the kernel, QEMU writes CPER into corresponding 99 interrupt (in case of arm/virt machine it's Synchronous External Abort) as a 110 migrated to a newer QEMU.
|
H A D | acpi_nvdimm.rst | 11 _SB scope with a _HID of "ACPI0012". For each NVDIMM present or intended 18 functions specific to a particular NVDIMM implementation. 20 This is an example from ACPI 6.0, a platform contains one NVDIMM:: 41 It is a control method that enables devices to provide device specific 49 A Buffer containing a UUID (16 Bytes) 60 If Function Index = 0, a Buffer containing a function index bitfield. 68 It evaluates to a buffer returning data in the format of a series of NFIT 74 A Buffer containing a list of NFIT Type structure entries. 82 QEMU uses 4 bytes IO Port starting from 0x0a18 and a RAM-based memory page 86 QEMU uses BIOS Linker/loader feature to ask BIOS to allocate a memory [all …]
|
/qemu/docs/interop/ |
H A D | dbus.rst | 25 Using a bus, helper processes can discover and communicate with each 27 easier to apprehend and debug than a mesh. However, it is wise to 33 A QEMU D-Bus bus should be private to a single VM. Thus, only 45 carefully validate any information they received from a peer with a 52 processes that are connected to it. It is thus a good idea to run 76 ``org.qemu.Helper1`` service, a dbus-daemon policy may contain: 92 could be allowed to send a message to ``svirt_t``, but ``virtiofs_t`` 93 wouldn't be allowed to send a message to ``virtiofs_t``.
|
H A D | dbus-vmstate.rst | 6 on a QEMU D-Bus bus. (refer to the :doc:`dbus` document for 18 1Mb. The state must be saved quickly (a fraction of a second). (D-Bus 19 imposes a time limit on reply anyway, and migration would fail if data 23 helpers by setting its ``id-list`` property, with a comma-separated
|
/qemu/tests/qapi-schema/ |
H A D | qapi-schema-test.json | 4 # This file is a stress test of supported qapi constructs that must 13 # Commands allowed to return a non-dictionary: 80 # by intentionally using two branches that both have a C member 'a_b' 85 'data': { 'intb': 'int', '*a-b': 'bool' } } 119 'data': [ 'value-a', 'value-b' ] } 133 'base': { 'type-a': 'TestUnionEnumA' }, 134 'discriminator': 'type-a', 145 'data': { 'value-a': 'TestUnionTypeA', 189 # Returning a non-dictionary requires a name from the whitelist 190 { 'command': 'guest-get-time', 'data': {'a': 'int', '*b': 'int' }, [all …]
|
/qemu/docs/system/i386/ |
H A D | sgx.rst | 7 Intel Software Guard eXtensions (SGX) is a set of instructions and mechanisms 29 By default, QEMU does not assign EPC to a VM, i.e. fully enabling SGX in a VM 31 memory types, e.g. hugetlbfs, EPC is exposed as a memory backend. 38 QEMU does not artificially restrict the number of EPC sections exposed to a 54 the size of the physical EPC must be a power of two (though software sees 55 a subset of the full EPC, e.g. 92M or 128M) and the EPC must be naturally 56 aligned. KVM SGX's virtual EPC is purely a software construct and only 134 Launching a guest 137 To launch a SGX guest: 146 Utilizing SGX in the guest requires a kernel/OS with SGX support. [all …]
|
/qemu/target/arm/tcg/ |
H A D | translate.h | 488 void gen_cmtst_i64(TCGv_i64 d, TCGv_i64 a, TCGv_i64 b); 489 void gen_ushl_i32(TCGv_i32 d, TCGv_i32 a, TCGv_i32 b); 490 void gen_sshl_i32(TCGv_i32 d, TCGv_i32 a, TCGv_i32 b); 491 void gen_ushl_i64(TCGv_i64 d, TCGv_i64 a, TCGv_i64 b); 492 void gen_sshl_i64(TCGv_i64 d, TCGv_i64 a, TCGv_i64 b); 495 TCGv_i64 a, TCGv_i64 b, MemOp esz); 501 TCGv_i64 a, TCGv_i64 b, MemOp esz); 507 TCGv_i64 a, TCGv_i64 b, MemOp esz); 513 TCGv_i64 a, TCGv_i64 b, MemOp esz); 523 void gen_srshr32_i32(TCGv_i32 d, TCGv_i32 a, int32_t sh); [all …]
|
/qemu/tests/decode/ |
H A D | succ_named_field.decode | 4 # field using a named_field 8 # Ditto, via a format. Here a field in the format 9 # references a named field defined in the insn pattern:
|
/qemu/target/mips/tcg/ |
H A D | vr54xx_translate.c | 37 static bool trans_mult_acc(DisasContext *ctx, arg_r *a, in trans_mult_acc() argument 43 gen_load_gpr(t0, a->rs); in trans_mult_acc() 44 gen_load_gpr(t1, a->rt); in trans_mult_acc() 48 gen_store_gpr(t0, a->rd); in trans_mult_acc()
|
/qemu/tests/tcg/i386/ |
H A D | test-avx.c | 64 static void compare_state(const reg_state *a, const reg_state *b) in compare_state() argument 68 if (a->mm[i] != b->mm[i]) { in compare_state() 73 if (a->r[i] != b->r[i]) { in compare_state() 78 if (memcmp(&a->ymm[i], &b->ymm[i], 32)) { in compare_state() 79 dump_ymm("ymm", i, &b->ymm[i], a->ff); in compare_state() 83 if (memcmp(&a->mem0[i], &a->mem[i], 32)) { in compare_state() 84 dump_ymm("mem", i, &a->mem[i], a->ff); in compare_state() 87 if (a->flags != b->flags) { in compare_state()
|
/qemu/docs/config/ |
H A D | mach-virt-graphical.cfg | 14 # The guest will have a selection of VirtIO devices 16 # and will be accessed through a graphical console. 23 # such as the PL011 UART, plus a PCI Express Root Bus; the 30 # This configuration file adds a number of other useful 71 # There are two parts to the firmware: a read-only image 73 # guests, and a read/write variable store that is owned 184 # We use virtio-scsi here so that we can (hot)plug a large 245 # We add a virtualization-friendly USB 3.0 controller and 246 # a USB keyboard / USB tablet combo so that graphical 270 # If you're running the guest on a remote, potentially [all …]
|
/qemu/qapi/ |
H A D | ui.json | 25 # An action to take on changing a password on a connection with active 173 # Capture the contents of a screen and write it to a file. 228 # Information about a SPICE server 375 # Emitted when a SPICE client establishes a connection 625 # Information about a vnc server 692 # Returns: a list of @VncInfo2 719 # Emitted when a VNC client establishes a connection 989 # @data: a numeric key code 1009 # Represents a keyboard key. 1081 # Type of a multi-touch event. [all …]
|
/qemu/migration/ |
H A D | multifd-zero-page.c | 26 static void swap_page_offset(ram_addr_t *pages_offset, int a, int b) in swap_page_offset() argument 30 if (a == b) { in swap_page_offset() 34 temp = pages_offset[a]; in swap_page_offset() 35 pages_offset[a] = pages_offset[b]; in swap_page_offset()
|
/qemu/docs/ |
H A D | igd-assign.txt | 8 In this mode the IGD device is added as a *secondary* (ie. non-primary) 33 * The VM machine type must support a PCI host bridge at 00.0 (standard) 34 * The VM machine type must provide or allow to be created a special 37 * The IGD device must have a VGA ROM, either provided via the romfile 41 * The IGD device must be a SandyBridge or newer model device. 45 has been assigned to a VM. It's therefore generally recommended to prevent 53 blacklisting i915 or using pci-stub/vfio-pci to take ownership of IGD as a 57 a catch-all, video=vesafb:off,efifb:off. Error messages such as: 61 are a good indicator that such a problem exists. The host files /proc/iomem 111 within a VM is undefined. [all …]
|
/qemu/hw/arm/ |
H A D | aspeed_ast2400.c | 139 Aspeed2400SoCState *a = ASPEED2400_SOC(s); in aspeed_soc_ast2400_get_irq() local 142 return qdev_get_gpio_in(DEVICE(&a->vic), sc->irqmap[dev]); in aspeed_soc_ast2400_get_irq() 147 Aspeed2400SoCState *a = ASPEED2400_SOC(obj); in aspeed_ast2400_soc_init() local 159 object_initialize_child(obj, "cpu[*]", &a->cpu[i], in aspeed_ast2400_soc_init() 174 object_initialize_child(obj, "vic", &a->vic, TYPE_ASPEED_VIC); in aspeed_ast2400_soc_init() 249 Aspeed2400SoCState *a = ASPEED2400_SOC(dev); in aspeed_ast2400_soc_realize() local 271 object_property_set_link(OBJECT(&a->cpu[i]), "memory", in aspeed_ast2400_soc_realize() 273 if (!qdev_realize(DEVICE(&a->cpu[i]), NULL, errp)) { in aspeed_ast2400_soc_realize() 294 if (!sysbus_realize(SYS_BUS_DEVICE(&a->vic), errp)) { in aspeed_ast2400_soc_realize() 298 sysbus_connect_irq(SYS_BUS_DEVICE(&a->vic), 0, in aspeed_ast2400_soc_realize() [all …]
|
/qemu/docs/system/devices/ |
H A D | vhost-user.rst | 7 outside of QEMU itself. To do this there are a number of things 15 a ``chardev`` option which specifies the ID of the ``--chardev`` 16 device that connects via a socket to the vhost-user *daemon*. 68 The vhost-user-device is a generic development device intended for 89 This is a separate process that is connected to by QEMU via a socket 90 following the :ref:`vhost_user_proto`. There are a number of daemons 92 meets the specification for a given device can be used. 102 objects. A reference to a file-descriptor which can access this object
|
/qemu/tests/tcg/openrisc/ |
H A D | test_lf_div.c | 5 float a, b, c; in main() local 13 : "=r"(a) in main() 16 if (a != result) { in main()
|
H A D | test_lf_sub.c | 5 float a, b, c; in main() local 13 : "=r"(a) in main() 16 if (a != result) { in main()
|
H A D | test_lf_mul.c | 5 float a, b, c; in main() local 13 : "=r"(a) in main() 16 if (a != result) { in main()
|
H A D | test_lf_rem.c | 5 float a, b, c; in main() local 23 : "=r"(a) in main() 26 if (a != result) { in main()
|
/qemu/tests/qemu-iotests/ |
H A D | 249.out | 8 === Send a write command to a drive opened in read-only mode (1) 23 === Send a write command to a drive opened in read-only mode (2) 42 === Send a write command to a drive opened in read-only mode (3)
|
H A D | 068.out | 3 === Saving and reloading a VM state to/from a qcow2 image () === 14 === Saving and reloading a VM state to/from a qcow2 image (-object iothread,id=iothread0 -set devic…
|