| /qemu/qapi/ |
| H A D | char.json | 195 # Configuration shared across all chardev backends
211 # Configuration info for file chardevs.
231 # Configuration info for device and pipe chardevs.
245 # Configuration info for (stream) socket chardevs.
309 # Configuration info for datagram socket chardevs.
325 # Configuration info for mux chardevs.
338 # Configuration info for hub chardevs.
351 # Configuration info for stdio chardevs.
365 # Configuration info for spice vm channel chardevs.
379 # Configuration info for spice port chardevs.
[all …]
|
| H A D | tpm.json | 127 # A union referencing different TPM backend types' configuration
131 # - 'passthrough' The configuration options for the TPM
133 # - 'emulator' The configuration options for TPM emulator backend
154 # @options: The TPM (backend) type configuration options
|
| /qemu/docs/interop/ |
| H A D | qemu-ga.rst | 27 qemu-ga will read a system configuration file on startup (located at
29 configuration options on the command line. For the same key, the last
30 option wins, but the lists accumulate (see below for configuration
33 If an allowed RPCs list is defined in the configuration, then all
36 If a blocked RPCs list is defined in the configuration, then all
39 If both allowed and blocked RPCs lists are defined in the configuration,
44 of RPCs will blocked, regardless of what the general configuration
54 Configuration file path (the default is |CONFDIR|\ ``/qemu-ga.conf``,
115 Dump the configuration in a format compatible with ``qemu-ga.conf``
126 The syntax of the ``qemu-ga.conf`` configuration file follows the
[all …]
|
| /qemu/docs/specs/ |
| H A D | fw_cfg.rst | 2 QEMU Firmware Configuration (fw_cfg) Device
22 A write to this register sets the index of a firmware configuration
29 Bit14 of the selector register indicates whether the configuration
33 register. In other words, configuration write mode is enabled when
45 Bit15 of the selector register indicates whether the configuration
47 generic configuration item. A value of 1 means the item is specific
48 to a particular architecture. In other words, generic configuration
50 architecture specific configuration items are accessed with a selector
68 configuration data item. The specific item is selected by writing to
75 Each firmware configuration item has a maximum length of data
[all …]
|
| H A D | fsi.rst | 14 processor to perform configuration or debugging. FSI has long existed in POWER
24 an internal Local Bus (LBUS) which is described by the CFAM configuration
29 slave's configuration registers appear in address space of the CFAM to
48 of the object model to automatically generate the CFAM configuration block.
49 The configuration block presents engines in the order they are attached to the
|
| /qemu/ |
| H A D | .gitlab-ci.yml | 2 # This is the GitLab CI configuration file for the mainstream QEMU
5 # !!! DO NOT ADD ANY NEW CONFIGURATION TO THIS FILE !!!
11 # configuration path", on your GitLab CI namespace:
12 # https://docs.gitlab.com/ee/ci/pipelines/settings.html#custom-cicd-configuration-path
17 # user-configurable options, modifiable via configuration variables.
|
| H A D | .readthedocs.yml | 2 # Read the Docs configuration file
16 configuration: docs/conf.py
|
| /qemu/linux-headers/linux/ |
| H A D | vduse.h | 23 * struct vduse_dev_config - basic configuration of a VDUSE device
31 * @config_size: the size of the configuration space
32 * @config: the buffer of the configuration space
94 * struct vduse_config_data - data used to update configuration space
95 * @offset: the offset from the beginning of configuration space
96 * @length: the length to write to configuration space
100 * configuration space.
108 /* Set device configuration space */
113 * that device configuration space has changed.
118 * struct vduse_vq_config - basic configuration of a virtqueue
[all …]
|
| /qemu/docs/system/openrisc/ |
| H A D | or1k-sim.rst | 5 also the standard SoC configuration.
27 Linux guest kernel configuration
34 Hardware configuration information
39 addresses, interrupt lines and other configuration of the various devices
|
| H A D | virt.rst | 36 Linux guest kernel configuration
42 Hardware configuration information
47 lines and other configuration of the various devices in the system.
|
| /qemu/tests/qemu-iotests/ |
| H A D | 283 | 36 this thing, so all parents of source node are handled. A configuration with
39 test create an example of such configuration and checks that a backup is then
42 The configuration:
66 configuration is default permission propagation scheme. It may be altered by
67 different block drivers, so backup will run in invalid configuration. But
69 preceding this test creation), starting backup on such configuration led to
|
| /qemu/include/hw/display/ |
| H A D | bcm2835_fb.h | 25 * Configuration information about the fb which the guest can program
61 * @config: configuration info for the framebuffer
75 * @config: configuration info for the framebuffer
86 * Validates the configuration information provided by the guest and
|
| /qemu/docs/devel/ |
| H A D | kconfig.rst | 40 Unlike Linux, there is no user interface to edit the configuration, which
43 configuration and dependencies can be treated as a black box when building
44 QEMU; the default configuration that QEMU ships with should be okay in
68 The ``config`` keyword introduces a new configuration element. In the example
101 you from building such a configuration.
112 A configuration element can have any number of default values (usually,
167 of directives that cooperate so that a default configuration includes
267 # Default configuration for alpha-softmmu
282 the default configuration by uncommenting lines in the first group,
|
| /qemu/include/hw/virtio/ |
| H A D | vhost.h | 159 * negotiation of backend interface. Configuration of the VirtIO
241 * DOC: vhost device configuration handling
243 * The VirtIO device configuration space is used for rarely changing
244 * or initialisation time parameters. The configuration can be updated
246 * change the configuration over time the vhost handler should
254 * vhost_dev_get_config() - fetch device configuration
265 * vhost_dev_set_config() - set device configuration
268 * @offset: offset into configuration space
272 * By use of @offset/@size a subset of the configuration space can be
286 * If the device is expected to change configuration a notifier can be
|
| /qemu/include/net/ |
| H A D | net.h | 196 * qemu_find_nic_info: Obtain NIC configuration information
202 * Search for a NIC configuration matching the NIC model constraints.
207 * qemu_configure_nic_device: Apply NIC configuration to a given device
212 * Search for a NIC configuration for the provided device, using the
214 * configuration using qdev_set_nic_properties() and return %true.
217 * regardless of whether there is a configuration for it. This tends
226 * qemu_create_nic_device: Create a NIC device if a configuration exists for it
231 * Search for a NIC configuration for the provided device type. If found,
|
| /qemu/docs/system/ppc/ |
| H A D | ppce500.rst | 13 * Configuration, Control, and Status Register (CCSR)
25 Hardware configuration information
30 information about the addresses, interrupt lines and other configuration of
86 64-bit mode, simply configure the kernel using the defconfig configuration:
95 then manually select the following configuration:
110 in 32-bit mode, use the same 64-bit configuration steps except the defconfig
|
| /qemu/docs/system/arm/ |
| H A D | orangepi.rst | 16 * Generic Interrupt Controller configuration
83 simply configure the kernel using the sunxi_defconfig configuration:
91 configuration item. Start the kconfig configuration tool:
97 Navigate to the following item, enable it and save your configuration:
187 for development/testing to select the following configuration setting in U-Boot:
219 the orangepi_pc_defconfig configuration as described in the previous section.
|
| /qemu/subprojects/libvduse/ |
| H A D | libvduse.h | 153 * @size: the size to write to configuration space
154 * @offset: the offset from the beginning of configuration space
157 * Update device configuration space and inject a config interrupt.
223 * @config_size: the size of the configuration space
224 * @config: the buffer of the configuration space
|
| /qemu/include/standard-headers/linux/ |
| H A D | virtio_pci.h | 74 /* A 16-bit vector for configuration changes. */
80 * configuration space */
98 /* The bit of the ISR which indicates a device configuration change. */
107 /* Common configuration */
113 /* Device specific configuration */
115 /* PCI configuration access */
119 /* PCI vendor data configuration */
|
| /qemu/docs/system/s390x/ |
| H A D | bootdevices.rst | 121 configuration files. See the `PXELINUX Configuration page
122 <https://wiki.syslinux.org/wiki/index.php?title=PXELINUX#Configuration>`__
123 for details how to set up the configuration file on your TFTP server.
124 The supported configuration file entries are ``DEFAULT``, ``LABEL``,
|
| /qemu/docs/system/ |
| H A D | virtio-net-failover.rst | 32 requires no configuration in the guest. When a guest is live-migrated to
41 The primary device can be hotplugged or be part of the startup configuration
65 devices are present in the configuration, migration will go into this state.
|
| /qemu/hw/net/ |
| H A D | eepro100.c | 275 /* Configuration bytes. */
276 uint8_t configuration[22]; member
524 s->configuration[6] |= BIT(4); in e100_pci_reset()
527 s->configuration[6] |= BIT(5); in e100_pci_reset()
531 if (s->configuration[6] & BIT(2)) { in e100_pci_reset()
533 assert(s->configuration[6] & BIT(5)); in e100_pci_reset()
535 if (s->configuration[6] & BIT(5)) { in e100_pci_reset()
544 if (s->configuration[6] & BIT(5)) { in e100_pci_reset()
708 * Number of data should check configuration!!! in dump_statistics()
776 if (s->has_extended_tcb_support && !(s->configuration[6] & BIT(4))) { in tx_command()
[all …]
|
| /qemu/docs/system/riscv/ |
| H A D | sifive_u.rst | 29 Please note the real world HiFive Unleashed board has a fixed configuration of
36 Hardware configuration information
41 information about the addresses, interrupt lines and other configuration of
116 64-bit mode, simply configure the kernel using the defconfig configuration:
162 in 32-bit mode, use the rv32_defconfig configuration. A patch is required to
230 A sample configuration file for a 128 MiB SD card image is:
322 configuration of U-Boot:
|
| /qemu/docs/ |
| H A D | multiseat.txt | 63 For vnc some additional configuration on the command line is needed.
107 check the configuration:
131 configuration:
140 fine without any manual guest configuration.
|
| /qemu/docs/system/i386/ |
| H A D | tdx.rst | 34 Feature Configuration
62 ``struct kvm_tdx_capabilities``, which tells the supported configuration of
72 QEMU also supports the configuration of individual attribute bits that are
80 configuration for TDX, and it's a future work to enable it in QEMU when KVM adds
|