Home
last modified time | relevance | path

Searched full:via (Results 1 – 25 of 728) sorted by relevance

12345678910>>...30

/qemu/include/qemu/
H A Dmemalign.h21 * The memory allocated through this function must be freed via
22 * qemu_vfree() (and not via free()).
33 * The memory allocated through this function must be freed via
34 * qemu_vfree() (and not via free()).
41 * This function must be used to free memory allocated via qemu_memalign()
/qemu/
H A DREADME.rst27 It is commonly invoked indirectly via the libvirt library when using
49 Linux platforms, OS-X, Win32 (via the Mingw64 toolchain) and a variety
60 Additional information can also be found online via the QEMU website:
84 Additional information on submitting patches can be found online via
136 should be reported via:
140 If using QEMU via an operating system vendor pre-built binary package, it
143 reported via GitLab.
169 found online via the QEMU website:
/qemu/include/crypto/
H A Dtlscredsanon.h45 * via object_new_propv():
62 * Or via QMP:
65 * <title>Creating anonymous TLS credential objects via QMP</title>
82 * Or via the CLI:
85 * <title>Creating anonymous TLS credential objects via CLI</title>
H A Dtlscredsx509.h49 * via object_new_propv():
66 * Or via QMP:
69 * <title>Creating x509 TLS credential objects via QMP</title>
86 * Or via the CLI:
89 * <title>Creating x509 TLS credential objects via CLI</title>
H A Dtlscredspsk.h43 * via object_new_propv():
59 * Or via QMP:
62 * <title>Creating TLS-PSK credential objects via QMP</title>
77 * Or via the CLI:
80 * <title>Creating TLS-PSK credential objects via CLI</title>
H A Dsecret.h44 * be provided directly via the 'data' property, or
45 * indirectly via the 'file' property. In the latter
47 * via the usual /dev/fdset/NN syntax that QEMU uses.
59 * via the 'data' property it is strongly recommended
104 * When encrypting, the data can still be provided via an
/qemu/include/hw/isa/
H A Dvt82c686.h10 #define TYPE_VIA_AC97 "via-ac97"
11 #define TYPE_VIA_IDE "via-ide"
12 #define TYPE_VIA_MC97 "via-mc97"
/qemu/contrib/gitdm/
H A Daliases48 "Ed Swierk via Qemu-devel" eswierk@skyportsystems.com
49 "Ian McKellar via Qemu-devel" ianloic@google.com
50 "Julia Suvorova via Qemu-devel" jusual@mail.ru
51 "Justin Terry (VM) via Qemu-devel" juterry@microsoft.com
/qemu/include/hw/ppc/
H A Dspapr_drc.h55 * for values exposed to the guest (via DRC indexes for
78 * set via set-indicator RTAS calls
90 * set via set-indicator RTAS calls
108 * set via set-indicator RTAS calls
125 * returned via get-sensor-state RTAS calls
185 /* device pointer, via link property */
/qemu/hw/misc/
H A Dmac_via.c2 * QEMU m68k Macintosh VIA device support
155 * defines the 'Video IRQ' as 0x40 for the 'EVR' VIA work-alike.
230 * right bit in the VIA chip (6522 Versatile Interface Adapter).
239 /* partial address decode. 0xYYXX : XX part for RBV, YY part for VIA */
240 /* Note: 15 VIA regs, 8 RBV regs */
242 #define vBufB 0x0000 /* [VIA/RBV] Register B */
243 #define vBufAH 0x0200 /* [VIA only] Buffer A, with handshake. DON'T USE! */
244 #define vDirB 0x0400 /* [VIA only] Data Direction Register B. */
245 #define vDirA 0x0600 /* [VIA only] Data Direction Register A. */
246 #define vT1CL 0x0800 /* [VIA only] Timer one counter low. */
[all …]
/qemu/target/s390x/
H A Dcpu_features_def.h.inc22 /* Features exposed via the STFL(E) instruction. */
127 /* Features exposed via SCLP SCCB Byte 80 - 98 (bit numbers relative to byte-80) */
133 /* Features exposed via SCLP SCCB Byte 116 - 119 (bit numbers relative to byte-116) */
139 /* Features exposed via SCLP SCCB Facilities byte 134 (bit numbers relative to byte-134) */
142 /* Features exposed via SCLP CPU info. */
152 * Features exposed via no feature bit (but e.g., instruction sensing)
159 /* Features exposed via the PLO instruction. */
223 /* Features exposed via the PTFF instruction. */
237 /* Features exposed via the KMAC instruction. */
260 /* Features exposed via the KMC instruction. */
[all …]
/qemu/docs/system/arm/
H A Dorangepi.rst36 - Graphical output via HDMI, GPU and/or the Display Engine
49 based SoC, which loads the bootloader from a SD card, specified via the -sd argument
71 via the '-global' argument, for example:
162 Instead of providing a custom Linux kernel via the -kernel command you may also
164 a real board would do using the BootROM. Simply pass the selected image via the -sd
173 a lot of userland programs via systemd. Depending on the host hardware and OS,
176 give the following kernel parameters via U-Boot (or via -append):
H A Dmps2.rst55 - AN536 does not support runtime control of CPU reset and halt via
58 interfaces via the SCC CFG_REG1 register.
60 base address via the SCC CFG_REG6 and CFG_REG7 register config,
66 held in halt via the initial SCC CFG_REG0 register setting. You can
H A Dbananapi_m2u.rst35 - Graphical output via HDMI, GPU and/or the Display Engine
48 based SoC, which loads the bootloader from a SD card, specified via the -sd
95 Instead of providing a custom Linux kernel via the -kernel command you may also
97 a real board would do using the BootROM. Simply pass the selected image via the -sd
/qemu/hw/audio/
H A Dvia-ac97.c2 * VIA south bridges sound support
148 "via-ac97: Unimplemented codec register 0x%x\n", addr); in codec_write()
162 "via-ac97: DMA error reading SGD table\n"); in fetch_sgd()
242 s->vo = AUD_open_out(&s->card, s->vo, "via-ac97.out", s, out_cb, &as); in open_voice_out()
288 qemu_log_mask(LOG_UNIMP, "via-ac97: Unimplemented register read 0x%" in sgd_read()
370 qemu_log_mask(LOG_UNIMP, "via-ac97: Unimplemented register write 0x%" in sgd_write()
429 if (!AUD_register_card ("via-ac97", &s->card, errp)) { in via_ac97_realize()
446 memory_region_init_io(&s->sgd, o, &sgd_ops, s, "via-ac97.sgd", 256); in via_ac97_realize()
448 memory_region_init_io(&s->fm, o, &fm_ops, s, "via-ac97.fm", 4); in via_ac97_realize()
450 memory_region_init_io(&s->midi, o, &midi_ops, s, "via-ac97.midi", 4); in via_ac97_realize()
[all …]
/qemu/hw/ide/
H A Dvia.c95 memory_region_init(&d->bmdma_bar, OBJECT(d), "via-bmdma-container", 16); in bmdma_setup_bar()
100 "via-bmdma", 4); in bmdma_setup_bar()
209 &d->bus[0], "via-ide0-data", 8); in via_ide_realize()
213 &d->bus[0], "via-ide0-cmd", 4); in via_ide_realize()
217 &d->bus[1], "via-ide1-data", 8); in via_ide_realize()
221 &d->bus[1], "via-ide1-cmd", 4); in via_ide_realize()
255 /* Reason: only works as function of VIA southbridge */ in via_ide_class_init()
/qemu/docs/system/ppc/
H A Dppce500.rst17 * 1 Pericom pt7c4338 RTC via I2C
19 * Power-off functionality via one GPIO pin
21 * VirtIO devices via PCI bus
37 * The /memory reg size should match QEMU’s selected ram_size via ``-m``
51 The CPU type can be specified via the ``-cpu`` command line. If not specified,
77 automatically loads the kernel image specified by the -kernel parameter via
/qemu/include/hw/ssi/
H A Dssi.h90 * reference to it. Errors are reported via @errp and by returning
93 * This function is useful if you have created @dev via qdev_new()
100 * initialized it via some variant on object_initialize_child() then
103 * via the child<> property, and so the reference-count-drop done here
/qemu/util/
H A Dhost-utils.c92 * Returns quotient via plow and phigh.
93 * Also returns the remainder via the function return value.
155 * Returns quotient via plow and phigh.
156 * Also returns the remainder via the function return value.
272 * Returns the remainder via r.
335 * Returns quotient via plow and phigh.
336 * Also returns the remainder via the function return value.
401 * Returns quotient via plow and phigh.
402 * Also returns the remainder via the function return value.
/qemu/docs/system/devices/
H A Dvhost-user.rst16 device that connects via a socket to the vhost-user *daemon*.
89 This is a separate process that is connected to by QEMU via a socket
101 achieved via the ``memory-backend-file``, ``memory-backend-memfd``, or
104 will be passed via the socket as part of the protocol negotiation.
H A Dvirtio-pmem.rst48 Virtio pmem devices can be hotplugged via the QEMU monitor. First, the
49 memory backing has to be added via 'object_add'; afterwards, the virtio
50 pmem device can be added via 'device_add'.
/qemu/include/hw/s390x/
H A Ds390-pci-bus.h182 * configured state/to this state via sclp configure/deconfigure
186 * state and enabled via clp enable/disable
187 * enabled: device is ready for use; transition to disabled via clp disable;
190 * error state via mpcifc
191 * error: an error occurred; transition back to enabled via mpcifc
192 * permanent error: an unrecoverable error occurred; transition to standby via
/qemu/docs/system/i386/
H A Dsgx.rst18 SGX feature is exposed to guest via SGX CPUID. Looking at SGX CPUID, we can
53 to physical EPC. Because physical EPC is protected via range registers,
82 e.g. via ``-cpu <model>,+sgx`` or ``-cpu <model>,+sgx,+sgxlc``.
85 ATTRIBUTES, etc... can be restricted via CPUID flags. Be aware that enforcing
88 controlled via -cpu are prefixed with "sgx", e.g.::
110 in hardware cannot be forced on via '-cpu'.
/qemu/tests/tcg/multiarch/gdbstub/
H A Dtest-qxfer-auxv-read.py3 # Test auxiliary vector is loaded via gdbstub
5 # This is launched via tests/guest-debug/run-test.py
H A Dtest-thread-breakpoint.py3 # Test auxiliary vector is loaded via gdbstub
5 # This is launched via tests/guest-debug/run-test.py

12345678910>>...30