| /openbmc/qemu/docs/devel/ |
| H A D | multi-process.rst | 57 emulation. i.e., the control process would also be the CPU emulation
58 process. In a later phase, CPU emulation could be separated from the
68 Another is the modular nature of QEMU device emulation code provides
69 interface points where the QEMU functions that perform device emulation
70 can be separated from the QEMU functions that manage the emulation of
74 QEMU device emulation
77 QEMU uses an object oriented SW architecture for device emulation code.
84 The object model is hierarchical, so device emulation code names its
92 In order to separate the device emulation code from the CPU emulation
94 a couple of existing QEMU features that can run emulation code
[all …]
|
| H A D | secure-coding-practices.rst | 17 virtualization or emulation. They are simply C programming bugs. Therefore
45 The most sensitive attack surface is device emulation. All hardware register
74 moments. Device emulation code must not assume that the guest follows the
79 A related issue is that device emulation code must be prepared for unexpected
82 certain device registers. Device emulation code must handle the case where the
101 Guests with multiple vCPUs may modify guest RAM while device emulation code is
102 running. Device emulation code must copy in descriptors and other guest RAM
105 crash when a vCPU thread modifies guest RAM while device emulation is
|
| /openbmc/qemu/docs/system/ |
| H A D | target-mips.rst | 20 The Malta emulation supports the following devices:
34 The Boston board emulation supports the following devices:
41 The ACER Pica emulation supports:
51 The MIPS Magnum R4000 emulation supports:
63 The Fuloong 2E emulation supports:
73 The Loongson-3 virtual platform emulation supports:
83 The mipssim pseudo board emulation provides an environment similar to
90 - MIPSnet network emulation
112 Start system emulation of Malta board with nanoMIPS I7200 CPU::
|
| H A D | index.rst | 8 for full system emulation (as opposed to user-mode emulation).
17 device-emulation
|
| H A D | target-m68k.rst | 9 The M5208EVB emulation includes the following devices:
17 The AN5206 emulation includes the following devices:
|
| H A D | target-xtensa.rst | 14 The sim pseudo board emulation provides an environment similar to one
21 The Avnet LX60/LX110/LX200 emulation supports:
|
| H A D | target-rx.rst | 24 Start emulation of rx-virt::
33 Start emulation of rx-virt::
|
| /openbmc/linux/Documentation/driver-api/thermal/ |
| H A D | exynos_thermal_emulation.rst | 12 Exynos 4x12 (4212, 4412) and 5 series provide emulation mode for thermal
13 management unit. Thermal emulation mode supports software debug for
24 automatically enable emulation mode and current temperature will be
31 Exynos emulation mode requires synchronous of value changing and
33 next temperature, then you have to enable emulation mode at the same
39 Disabling emulation mode only requires writing value 0 to sysfs node.
60 emulation : 0 50 | 70 | 20 | 0
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | legacy_instructions.rst | 6 emulation of instructions which have been deprecated, or obsoleted in
8 hooks to support emulation. Where available it also allows turning on
11 The emulation mode can be controlled by writing to sysctl nodes
24 Uses software emulation. To aid migration of software, in this mode
39 architecture. Deprecated instructions should default to emulation
42 Note: Instruction emulation may not be possible in all cases. See
|
| /openbmc/qemu/target/loongarch/ |
| H A D | README | 12 - System emulation
14 …nce docs/system/loongarch/loongson3.rst to get the information about system emulation of LoongArch.
16 - Linux-user emulation
18 …We already support Linux user emulation. We can use LoongArch cross-tools to build LoongArch execu…
23 see System emulation.
|
| /openbmc/qemu/tcg/tci/ |
| H A D | README | 64 user mode emulation.
88 System emulation
95 Linux user mode emulation
104 running i386 and x86_64 system emulation and Linux user mode.
107 because I run it in a mips malta emulation, so it is an interpreted
108 emulation in an emulation.
112 (tested in a ppc emulation).
|
| /openbmc/linux/arch/arm64/kernel/ |
| H A D | trace-events-emulation.h | 3 #define TRACE_SYSTEM emulation
35 #define TRACE_INCLUDE_FILE trace-events-emulation
|
| /openbmc/u-boot/board/emulation/qemu-x86/ |
| H A D | MAINTAINERS | 4 F: board/emulation/qemu-x86/
11 F: board/emulation/qemu-x86/
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | best-practices.rst | 39 - Care should be taken with device emulation code so that newer
40 emulation code can work with older firmware to allow forward migration.
43 to older systems with older device emulation code will work.
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | stellaris.rst | 4 The Luminary Micro Stellaris LM3S811EVB emulation includes the following
16 The Luminary Micro Stellaris LM3S6965EVB emulation includes the
|
| H A D | sx1.rst | 4 The Siemens SX1 models v1 and v2 (default) basic emulation. The
5 emulation includes the following elements:
|
| /openbmc/linux/Documentation/mm/ |
| H A D | remap_file_pages.rst | 25 The syscall is deprecated and replaced it with an emulation now. The
26 emulation creates new VMAs instead of nonlinear mappings. It's going to
29 One side effect of emulation (apart from performance) is that user can hit
|
| /openbmc/qemu/docs/system/openrisc/ |
| H A D | emulation.rst | 4 QEMU's TCG emulation includes support for the OpenRISC or1200 implementation of
12 In addition to the instruction subsets the QEMU TCG emulation also has support
|
| /openbmc/openbmc/poky/meta/recipes-extended/minicom/ |
| H A D | minicom_2.9.bb | 1 SUMMARY = "Text-based modem control and terminal emulation program"
3 DESCRIPTION = "Minicom is a text-based modem control and terminal emulation program for Unix-like o…
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | can.rst | 3 The CAN bus emulation provides mechanism to connect multiple
31 to work on CAN hardware emulation on QEMU.
33 Examples how to use CAN emulation for SJA1000 based boards
47 (2) CAN bus PCM-3680I PCI (dual SJA1000 channel) emulation::
58 (3) CAN bus MIOe-3680 PCI (dual SJA1000 channel) emulation::
112 The PCIe board emulation is provided for now (the device identifier is
182 …(4) `RTLWS 2015 article about the project and its use with CANopen emulation <http://cmp.felk.cvut…
|
| /openbmc/linux/arch/m68k/ifpsp060/ |
| H A D | isp.doc | 38 isp.sa provides full emulation support for these instructions.
119 the entry code jumps to the appropriate emulation code within the code section.
182 If the emulation code provided by the 060ISP is sufficient for the
191 If the "core" emulation routines of either "cas" or "cas2" perform some
193 supply new emulation code. This new emulation code should reside within
194 the functions _060_real_cas() or _060_real_cas2(). When this new emulation
|
| /openbmc/qemu/docs/user/ |
| H A D | main.rst | 7 The following OS are supported in user space emulation:
16 QEMU user space emulation has the following notable features:
94 Run the emulation with one guest instruction per translation block.
95 This slows down emulation a lot, but can be useful in some situations,
237 Run the emulation with one guest instruction per translation block.
238 This slows down emulation a lot, but can be useful in some situations,
|
| /openbmc/qemu/docs/specs/ |
| H A D | riscv-iommu.rst | 6 QEMU implements a RISC-V IOMMU emulation based on the RISC-V IOMMU spec
9 The emulation includes a PCI reference device, riscv-iommu-pci, that QEMU
16 This device implements the RISC-V IOMMU emulation as recommended by the section
34 does not have support for features like VFIO passthrough. The IOMMU emulation
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | locks.rst | 18 The old flock(2) emulation in the kernel was swapped for proper BSD
20 release of the 2.1.x kernel series, support for the old emulation has
33 Because sendmail was unable to use the old flock() emulation, many sendmail
|
| /openbmc/linux/Documentation/arch/arm/ |
| H A D | swp_emulation.rst | 1 Software emulation of deprecated SWP instruction (CONFIG_SWP_EMULATE)
14 the last process to trigger the emulation to be invocated. For example::
|