* [PATCH 0/5] docs/system: Split target-arm.rst
@ 2020-03-09 21:58 Peter Maydell
2020-03-09 21:58 ` [PATCH 1/5] Makefile: Allow for subdirectories in Sphinx manual dependencies Peter Maydell
` (5 more replies)
0 siblings, 6 replies; 18+ messages in thread
From: Peter Maydell @ 2020-03-09 21:58 UTC (permalink / raw)
To: qemu-arm, qemu-devel; +Cc: Niek Linnenbank
This patchseries splits the 'target-arm.rst' file in the System
manual into one file per board or family of boards. It's not
sensible for us to document all 50-odd boards in a single enormous
page, and the split will encourage more detailed and useful per-board
information.
The impetus for doing this split is that it gives somewhere for the
documentation for the upcoming Orangepi board model to live. It also
means we can move arm-cpu-features.rst out of being an orphan unused
file in the docs/ directory.
I've also added some of the text I originally wrote for the wiki as a
general introduction to the Arm system emulation and to how to choose
a board model, plus some apologetic text about how most of our boards
are undocumented.
The last patch in this series smooths out an inconsistency in how we
spell 'Arm' (there was a corporate rebranding back in 2017, so we
have a mix of old-style 'ARM' and new-style 'Arm'); I don't feel very
strongly about this but the inconsistency did look a bit odd in some
of the docs that this series moves around, and it was 5 minutes work
to make docs/ consistent on one style.
Side notes:
(1) I still think it would be nice to be able to generate some of
this from doc comments and/or the board declaration macros; that
would be definitely not 5.0 material, though
(2) Anybody want to tackle the target-x86 part? There's a
docs/microvm.rst which would naturally live in
docs/system/x86/microvm.rst if target-x86.rst was restructured along
the same lines as this series, but it would need something
writing for the other x86 machine types...
thanks
-- PMM
Peter Maydell (5):
Makefile: Allow for subdirectories in Sphinx manual dependencies
docs/system: Split target-arm.rst into sub-documents
docs/system/target-arm.rst: Add some introductory text
docs: Move arm-cpu-features.rst into the system manual
docs: Be consistent about capitalization of 'Arm'
docs/can.txt | 2 +-
docs/devel/atomics.txt | 2 +-
docs/devel/multi-thread-tcg.txt | 8 +-
docs/replay.txt | 2 +-
docs/specs/fw_cfg.txt | 2 +-
Makefile | 2 +-
MAINTAINERS | 9 +
docs/devel/kconfig.rst | 2 +-
docs/devel/loads-stores.rst | 2 +-
docs/devel/tcg.rst | 2 +-
docs/specs/tpm.rst | 6 +-
.../arm/cpu-features.rst} | 12 +-
docs/system/arm/integratorcp.rst | 16 +
docs/system/arm/musicpal.rst | 19 ++
docs/system/arm/nseries.rst | 33 ++
docs/system/arm/palm.rst | 23 ++
docs/system/arm/realview.rst | 34 ++
docs/system/arm/stellaris.rst | 26 ++
docs/system/arm/sx1.rst | 18 ++
docs/system/arm/versatile.rst | 29 ++
docs/system/arm/xscale.rst | 29 ++
docs/system/target-arm.rst | 295 +++++-------------
docs/user/main.rst | 8 +-
23 files changed, 340 insertions(+), 241 deletions(-)
rename docs/{arm-cpu-features.rst => system/arm/cpu-features.rst} (98%)
create mode 100644 docs/system/arm/integratorcp.rst
create mode 100644 docs/system/arm/musicpal.rst
create mode 100644 docs/system/arm/nseries.rst
create mode 100644 docs/system/arm/palm.rst
create mode 100644 docs/system/arm/realview.rst
create mode 100644 docs/system/arm/stellaris.rst
create mode 100644 docs/system/arm/sx1.rst
create mode 100644 docs/system/arm/versatile.rst
create mode 100644 docs/system/arm/xscale.rst
--
2.20.1
^ permalink raw reply [flat|nested] 18+ messages in thread
* [PATCH 1/5] Makefile: Allow for subdirectories in Sphinx manual dependencies
2020-03-09 21:58 [PATCH 0/5] docs/system: Split target-arm.rst Peter Maydell
@ 2020-03-09 21:58 ` Peter Maydell
2020-03-10 14:29 ` Alex Bennée
` (2 more replies)
2020-03-09 21:58 ` [PATCH 2/5] docs/system: Split target-arm.rst into sub-documents Peter Maydell
` (4 subsequent siblings)
5 siblings, 3 replies; 18+ messages in thread
From: Peter Maydell @ 2020-03-09 21:58 UTC (permalink / raw)
To: qemu-arm, qemu-devel; +Cc: Niek Linnenbank
Currently we put 'docs/foo/*.rst' in the Make list of dependencies
for the Sphinx 'foo' manual, which means all the files must be
in the top level of that manual's directory. We'd like to be
able to have subdirectories inside some of the manuals, so add
'docs/foo/*/*.rst' to the dependencies too.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 2e930688942..5dba949947a 100644
--- a/Makefile
+++ b/Makefile
@@ -1081,7 +1081,7 @@ sphinxdocs: $(MANUAL_BUILDDIR)/devel/index.html \
# a single doctree: https://github.com/sphinx-doc/sphinx/issues/2946
build-manual = $(call quiet-command,CONFDIR="$(qemu_confdir)" $(SPHINX_BUILD) $(if $(V),,-q) -W -b $2 -D version=$(VERSION) -D release="$(FULL_VERSION)" -d .doctrees/$1-$2 $(SRC_PATH)/docs/$1 $(MANUAL_BUILDDIR)/$1 ,"SPHINX","$(MANUAL_BUILDDIR)/$1")
# We assume all RST files in the manual's directory are used in it
-manual-deps = $(wildcard $(SRC_PATH)/docs/$1/*.rst) \
+manual-deps = $(wildcard $(SRC_PATH)/docs/$1/*.rst $(SRC_PATH)/docs/$1/*/*.rst) \
$(SRC_PATH)/docs/defs.rst.inc \
$(SRC_PATH)/docs/$1/conf.py $(SRC_PATH)/docs/conf.py
# Macro to write out the rule and dependencies for building manpages
--
2.20.1
^ permalink raw reply related [flat|nested] 18+ messages in thread
* [PATCH 2/5] docs/system: Split target-arm.rst into sub-documents
2020-03-09 21:58 [PATCH 0/5] docs/system: Split target-arm.rst Peter Maydell
2020-03-09 21:58 ` [PATCH 1/5] Makefile: Allow for subdirectories in Sphinx manual dependencies Peter Maydell
@ 2020-03-09 21:58 ` Peter Maydell
2020-03-10 14:29 ` Alex Bennée
2020-03-10 20:53 ` Niek Linnenbank
2020-03-09 21:58 ` [PATCH 3/5] docs/system/target-arm.rst: Add some introductory text Peter Maydell
` (3 subsequent siblings)
5 siblings, 2 replies; 18+ messages in thread
From: Peter Maydell @ 2020-03-09 21:58 UTC (permalink / raw)
To: qemu-arm, qemu-devel; +Cc: Niek Linnenbank
Currently the documentation for Arm system emulator targets is in a
single target-arm.rst. This describes only some of the boards and
often in a fairly abbreviated fashion. Restructure it so that each
board has its own documentation file in the docs/system/arm/
subdirectory.
This will hopefully encourage us to write board documentation that
describes the board in detail, rather than a few brief paragraphs
in a single long page. The table of contents should also help users
to find the board they care about faster.
Once the structure is in place we'll be able to move microvm.rst
from the top-level docs/ directory.
All the text from the old page is retained, except for the final
paragraph ("A Linux 2.6 test image is available on the QEMU web site.
More information is available in the QEMU mailing-list archive."),
which is deleted. The git history shows this was originally added
in reference to the integratorcp board (at that time the only
Arm board that was supported), and has subsequently gradually been
further and further separated from the integratorcp documentation
by the insertion of other board documentation sections. It's
extremely out of date and no longer accurate, since AFAICT there
isn't an integratorcp kernel on the website any more; so better
deleted than retained.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
A subsequent patch will add some text that at least gestures
in the direction of some of the more obvious missing info,
eg 64-bit boards.
---
MAINTAINERS | 9 ++
docs/system/arm/integratorcp.rst | 16 +++
docs/system/arm/musicpal.rst | 19 +++
docs/system/arm/nseries.rst | 33 +++++
docs/system/arm/palm.rst | 23 ++++
docs/system/arm/realview.rst | 34 +++++
docs/system/arm/stellaris.rst | 26 ++++
docs/system/arm/sx1.rst | 18 +++
docs/system/arm/versatile.rst | 29 ++++
docs/system/arm/xscale.rst | 29 ++++
docs/system/target-arm.rst | 225 ++-----------------------------
11 files changed, 249 insertions(+), 212 deletions(-)
create mode 100644 docs/system/arm/integratorcp.rst
create mode 100644 docs/system/arm/musicpal.rst
create mode 100644 docs/system/arm/nseries.rst
create mode 100644 docs/system/arm/palm.rst
create mode 100644 docs/system/arm/realview.rst
create mode 100644 docs/system/arm/stellaris.rst
create mode 100644 docs/system/arm/sx1.rst
create mode 100644 docs/system/arm/versatile.rst
create mode 100644 docs/system/arm/xscale.rst
diff --git a/MAINTAINERS b/MAINTAINERS
index 36d0c6887a9..31a1b423df1 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -155,6 +155,7 @@ F: include/hw/cpu/a*mpcore.h
F: disas/arm.c
F: disas/arm-a64.cc
F: disas/libvixl/
+F: docs/system/target-arm.rst
ARM SMMU
M: Eric Auger <eric.auger@redhat.com>
@@ -615,6 +616,7 @@ F: hw/arm/integratorcp.c
F: hw/misc/arm_integrator_debug.c
F: include/hw/misc/arm_integrator_debug.h
F: tests/acceptance/machine_arm_integratorcp.py
+F: docs/system/arm/integratorcp.rst
MCIMX6UL EVK / i.MX6ul
M: Peter Maydell <peter.maydell@linaro.org>
@@ -673,6 +675,7 @@ M: Peter Maydell <peter.maydell@linaro.org>
L: qemu-arm@nongnu.org
S: Odd Fixes
F: hw/arm/musicpal.c
+F: docs/system/arm/musicpal.rst
nSeries
M: Andrzej Zaborowski <balrogg@gmail.com>
@@ -689,6 +692,7 @@ F: include/hw/display/blizzard.h
F: include/hw/input/tsc2xxx.h
F: include/hw/misc/cbus.h
F: tests/acceptance/machine_arm_n8x0.py
+F: docs/system/arm/nseries.rst
Palm
M: Andrzej Zaborowski <balrogg@gmail.com>
@@ -698,6 +702,7 @@ S: Odd Fixes
F: hw/arm/palm.c
F: hw/input/tsc210x.c
F: include/hw/input/tsc2xxx.h
+F: docs/system/arm/palm.rst
Raspberry Pi
M: Peter Maydell <peter.maydell@linaro.org>
@@ -719,6 +724,7 @@ F: hw/arm/realview*
F: hw/cpu/realview_mpcore.c
F: hw/intc/realview_gic.c
F: include/hw/intc/realview_gic.h
+F: docs/system/arm/realview.rst
PXA2XX
M: Andrzej Zaborowski <balrogg@gmail.com>
@@ -738,6 +744,7 @@ F: hw/misc/max111x.c
F: include/hw/arm/pxa.h
F: include/hw/arm/sharpsl.h
F: include/hw/display/tc6393xb.h
+F: docs/system/arm/xscale.rst
SABRELITE / i.MX6
M: Peter Maydell <peter.maydell@linaro.org>
@@ -773,6 +780,7 @@ L: qemu-arm@nongnu.org
S: Maintained
F: hw/*/stellaris*
F: include/hw/input/gamepad.h
+F: docs/system/arm/stellaris.rst
Versatile Express
M: Peter Maydell <peter.maydell@linaro.org>
@@ -786,6 +794,7 @@ L: qemu-arm@nongnu.org
S: Maintained
F: hw/*/versatile*
F: hw/misc/arm_sysctl.c
+F: docs/system/arm/versatile.rst
Virt
M: Peter Maydell <peter.maydell@linaro.org>
diff --git a/docs/system/arm/integratorcp.rst b/docs/system/arm/integratorcp.rst
new file mode 100644
index 00000000000..3232b43a08b
--- /dev/null
+++ b/docs/system/arm/integratorcp.rst
@@ -0,0 +1,16 @@
+Integrator/CP (``integratorcp``)
+================================
+
+The ARM Integrator/CP board is emulated with the following devices:
+
+- ARM926E, ARM1026E, ARM946E, ARM1136 or Cortex-A8 CPU
+
+- Two PL011 UARTs
+
+- SMC 91c111 Ethernet adapter
+
+- PL110 LCD controller
+
+- PL050 KMI with PS/2 keyboard and mouse.
+
+- PL181 MultiMedia Card Interface with SD card.
diff --git a/docs/system/arm/musicpal.rst b/docs/system/arm/musicpal.rst
new file mode 100644
index 00000000000..35c22212486
--- /dev/null
+++ b/docs/system/arm/musicpal.rst
@@ -0,0 +1,19 @@
+Freecom MusicPal (``musicpal``)
+===============================
+
+The Freecom MusicPal internet radio emulation includes the following
+elements:
+
+- Marvell MV88W8618 ARM core.
+
+- 32 MB RAM, 256 KB SRAM, 8 MB flash.
+
+- Up to 2 16550 UARTs
+
+- MV88W8xx8 Ethernet controller
+
+- MV88W8618 audio controller, WM8750 CODEC and mixer
+
+- 128x64 display with brightness control
+
+- 2 buttons, 2 navigation wheels with button function
diff --git a/docs/system/arm/nseries.rst b/docs/system/arm/nseries.rst
new file mode 100644
index 00000000000..b000b6d13bb
--- /dev/null
+++ b/docs/system/arm/nseries.rst
@@ -0,0 +1,33 @@
+Nokia N800 and N810 tablets (``n800``, ``n810``)
+================================================
+
+Nokia N800 and N810 internet tablets (known also as RX-34 and RX-44 /
+48) emulation supports the following elements:
+
+- Texas Instruments OMAP2420 System-on-chip (ARM 1136 core)
+
+- RAM and non-volatile OneNAND Flash memories
+
+- Display connected to EPSON remote framebuffer chip and OMAP on-chip
+ display controller and a LS041y3 MIPI DBI-C controller
+
+- TI TSC2301 (in N800) and TI TSC2005 (in N810) touchscreen
+ controllers driven through SPI bus
+
+- National Semiconductor LM8323-controlled qwerty keyboard driven
+ through |I2C| bus
+
+- Secure Digital card connected to OMAP MMC/SD host
+
+- Three OMAP on-chip UARTs and on-chip STI debugging console
+
+- Mentor Graphics \"Inventra\" dual-role USB controller embedded in a
+ TI TUSB6010 chip - only USB host mode is supported
+
+- TI TMP105 temperature sensor driven through |I2C| bus
+
+- TI TWL92230C power management companion with an RTC on
+ |I2C| bus
+
+- Nokia RETU and TAHVO multi-purpose chips with an RTC, connected
+ through CBUS
diff --git a/docs/system/arm/palm.rst b/docs/system/arm/palm.rst
new file mode 100644
index 00000000000..0eabf63e0e7
--- /dev/null
+++ b/docs/system/arm/palm.rst
@@ -0,0 +1,23 @@
+Palm Tungsten|E PDA (``cheetah``)
+=================================
+
+The Palm Tungsten|E PDA (codename \"Cheetah\") emulation includes the
+following elements:
+
+- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
+
+- ROM and RAM memories (ROM firmware image can be loaded with
+ -option-rom)
+
+- On-chip LCD controller
+
+- On-chip Real Time Clock
+
+- TI TSC2102i touchscreen controller / analog-digital converter /
+ Audio CODEC, connected through MicroWire and |I2S| busses
+
+- GPIO-connected matrix keypad
+
+- Secure Digital card connected to OMAP MMC/SD host
+
+- Three on-chip UARTs
diff --git a/docs/system/arm/realview.rst b/docs/system/arm/realview.rst
new file mode 100644
index 00000000000..8e08eb5da16
--- /dev/null
+++ b/docs/system/arm/realview.rst
@@ -0,0 +1,34 @@
+Arm Realview boards (``realview-eb``, ``realview-eb-mpcore``, ``realview-pb-a8``, ``realview-pbx-a9``)
+======================================================================================================
+
+Several variants of the ARM RealView baseboard are emulated, including
+the EB, PB-A8 and PBX-A9. Due to interactions with the bootloader, only
+certain Linux kernel configurations work out of the box on these boards.
+
+Kernels for the PB-A8 board should have CONFIG_REALVIEW_HIGH_PHYS_OFFSET
+enabled in the kernel, and expect 512M RAM. Kernels for The PBX-A9 board
+should have CONFIG_SPARSEMEM enabled, CONFIG_REALVIEW_HIGH_PHYS_OFFSET
+disabled and expect 1024M RAM.
+
+The following devices are emulated:
+
+- ARM926E, ARM1136, ARM11MPCore, Cortex-A8 or Cortex-A9 MPCore CPU
+
+- ARM AMBA Generic/Distributed Interrupt Controller
+
+- Four PL011 UARTs
+
+- SMC 91c111 or SMSC LAN9118 Ethernet adapter
+
+- PL110 LCD controller
+
+- PL050 KMI with PS/2 keyboard and mouse
+
+- PCI host bridge
+
+- PCI OHCI USB controller
+
+- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
+ devices
+
+- PL181 MultiMedia Card Interface with SD card.
diff --git a/docs/system/arm/stellaris.rst b/docs/system/arm/stellaris.rst
new file mode 100644
index 00000000000..8af4ad79c79
--- /dev/null
+++ b/docs/system/arm/stellaris.rst
@@ -0,0 +1,26 @@
+Stellaris boards (``lm3s6965evb``, ``lm3s811evb``)
+==================================================
+
+The Luminary Micro Stellaris LM3S811EVB emulation includes the following
+devices:
+
+- Cortex-M3 CPU core.
+
+- 64k Flash and 8k SRAM.
+
+- Timers, UARTs, ADC and |I2C| interface.
+
+- OSRAM Pictiva 96x16 OLED with SSD0303 controller on
+ |I2C| bus.
+
+The Luminary Micro Stellaris LM3S6965EVB emulation includes the
+following devices:
+
+- Cortex-M3 CPU core.
+
+- 256k Flash and 64k SRAM.
+
+- Timers, UARTs, ADC, |I2C| and SSI interfaces.
+
+- OSRAM Pictiva 128x64 OLED with SSD0323 controller connected via
+ SSI.
diff --git a/docs/system/arm/sx1.rst b/docs/system/arm/sx1.rst
new file mode 100644
index 00000000000..321993bc098
--- /dev/null
+++ b/docs/system/arm/sx1.rst
@@ -0,0 +1,18 @@
+Siemens SX1 (``sx1``, ``sx1-v1``)
+=================================
+
+The Siemens SX1 models v1 and v2 (default) basic emulation. The
+emulation includes the following elements:
+
+- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
+
+- ROM and RAM memories (ROM firmware image can be loaded with
+ -pflash) V1 1 Flash of 16MB and 1 Flash of 8MB V2 1 Flash of 32MB
+
+- On-chip LCD controller
+
+- On-chip Real Time Clock
+
+- Secure Digital card connected to OMAP MMC/SD host
+
+- Three on-chip UARTs
diff --git a/docs/system/arm/versatile.rst b/docs/system/arm/versatile.rst
new file mode 100644
index 00000000000..48b6ca0a020
--- /dev/null
+++ b/docs/system/arm/versatile.rst
@@ -0,0 +1,29 @@
+Arm Versatile boards (``versatileab``, ``versatilepb``)
+=======================================================
+
+The ARM Versatile baseboard is emulated with the following devices:
+
+- ARM926E, ARM1136 or Cortex-A8 CPU
+
+- PL190 Vectored Interrupt Controller
+
+- Four PL011 UARTs
+
+- SMC 91c111 Ethernet adapter
+
+- PL110 LCD controller
+
+- PL050 KMI with PS/2 keyboard and mouse.
+
+- PCI host bridge. Note the emulated PCI bridge only provides access
+ to PCI memory space. It does not provide access to PCI IO space. This
+ means some devices (eg. ne2k_pci NIC) are not usable, and others (eg.
+ rtl8139 NIC) are only usable when the guest drivers use the memory
+ mapped control registers.
+
+- PCI OHCI USB controller.
+
+- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
+ devices.
+
+- PL181 MultiMedia Card Interface with SD card.
diff --git a/docs/system/arm/xscale.rst b/docs/system/arm/xscale.rst
new file mode 100644
index 00000000000..19da2eff352
--- /dev/null
+++ b/docs/system/arm/xscale.rst
@@ -0,0 +1,29 @@
+Sharp XScale-based PDA models (``akita``, ``borzoi``, ``spitz``, ``terrier``)
+=============================================================================
+
+The XScale-based clamshell PDA models (\"Spitz\", \"Akita\", \"Borzoi\"
+and \"Terrier\") emulation includes the following peripherals:
+
+- Intel PXA270 System-on-chip (ARM V5TE core)
+
+- NAND Flash memory
+
+- IBM/Hitachi DSCM microdrive in a PXA PCMCIA slot - not in \"Akita\"
+
+- On-chip OHCI USB controller
+
+- On-chip LCD controller
+
+- On-chip Real Time Clock
+
+- TI ADS7846 touchscreen controller on SSP bus
+
+- Maxim MAX1111 analog-digital converter on |I2C| bus
+
+- GPIO-connected keyboard controller and LEDs
+
+- Secure Digital card connected to PXA MMC/SD host
+
+- Three on-chip UARTs
+
+- WM8750 audio CODEC on |I2C| and |I2S| busses
diff --git a/docs/system/target-arm.rst b/docs/system/target-arm.rst
index d2a3b44ce88..c7df6fc1f97 100644
--- a/docs/system/target-arm.rst
+++ b/docs/system/target-arm.rst
@@ -3,215 +3,16 @@
ARM System emulator
-------------------
-Use the executable ``qemu-system-arm`` to simulate a ARM machine. The
-ARM Integrator/CP board is emulated with the following devices:
-
-- ARM926E, ARM1026E, ARM946E, ARM1136 or Cortex-A8 CPU
-
-- Two PL011 UARTs
-
-- SMC 91c111 Ethernet adapter
-
-- PL110 LCD controller
-
-- PL050 KMI with PS/2 keyboard and mouse.
-
-- PL181 MultiMedia Card Interface with SD card.
-
-The ARM Versatile baseboard is emulated with the following devices:
-
-- ARM926E, ARM1136 or Cortex-A8 CPU
-
-- PL190 Vectored Interrupt Controller
-
-- Four PL011 UARTs
-
-- SMC 91c111 Ethernet adapter
-
-- PL110 LCD controller
-
-- PL050 KMI with PS/2 keyboard and mouse.
-
-- PCI host bridge. Note the emulated PCI bridge only provides access
- to PCI memory space. It does not provide access to PCI IO space. This
- means some devices (eg. ne2k_pci NIC) are not usable, and others (eg.
- rtl8139 NIC) are only usable when the guest drivers use the memory
- mapped control registers.
-
-- PCI OHCI USB controller.
-
-- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
- devices.
-
-- PL181 MultiMedia Card Interface with SD card.
-
-Several variants of the ARM RealView baseboard are emulated, including
-the EB, PB-A8 and PBX-A9. Due to interactions with the bootloader, only
-certain Linux kernel configurations work out of the box on these boards.
-
-Kernels for the PB-A8 board should have CONFIG_REALVIEW_HIGH_PHYS_OFFSET
-enabled in the kernel, and expect 512M RAM. Kernels for The PBX-A9 board
-should have CONFIG_SPARSEMEM enabled, CONFIG_REALVIEW_HIGH_PHYS_OFFSET
-disabled and expect 1024M RAM.
-
-The following devices are emulated:
-
-- ARM926E, ARM1136, ARM11MPCore, Cortex-A8 or Cortex-A9 MPCore CPU
-
-- ARM AMBA Generic/Distributed Interrupt Controller
-
-- Four PL011 UARTs
-
-- SMC 91c111 or SMSC LAN9118 Ethernet adapter
-
-- PL110 LCD controller
-
-- PL050 KMI with PS/2 keyboard and mouse
-
-- PCI host bridge
-
-- PCI OHCI USB controller
-
-- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
- devices
-
-- PL181 MultiMedia Card Interface with SD card.
-
-The XScale-based clamshell PDA models (\"Spitz\", \"Akita\", \"Borzoi\"
-and \"Terrier\") emulation includes the following peripherals:
-
-- Intel PXA270 System-on-chip (ARM V5TE core)
-
-- NAND Flash memory
-
-- IBM/Hitachi DSCM microdrive in a PXA PCMCIA slot - not in \"Akita\"
-
-- On-chip OHCI USB controller
-
-- On-chip LCD controller
-
-- On-chip Real Time Clock
-
-- TI ADS7846 touchscreen controller on SSP bus
-
-- Maxim MAX1111 analog-digital converter on |I2C| bus
-
-- GPIO-connected keyboard controller and LEDs
-
-- Secure Digital card connected to PXA MMC/SD host
-
-- Three on-chip UARTs
-
-- WM8750 audio CODEC on |I2C| and |I2S| busses
-
-The Palm Tungsten|E PDA (codename \"Cheetah\") emulation includes the
-following elements:
-
-- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
-
-- ROM and RAM memories (ROM firmware image can be loaded with
- -option-rom)
-
-- On-chip LCD controller
-
-- On-chip Real Time Clock
-
-- TI TSC2102i touchscreen controller / analog-digital converter /
- Audio CODEC, connected through MicroWire and |I2S| busses
-
-- GPIO-connected matrix keypad
-
-- Secure Digital card connected to OMAP MMC/SD host
-
-- Three on-chip UARTs
-
-Nokia N800 and N810 internet tablets (known also as RX-34 and RX-44 /
-48) emulation supports the following elements:
-
-- Texas Instruments OMAP2420 System-on-chip (ARM 1136 core)
-
-- RAM and non-volatile OneNAND Flash memories
-
-- Display connected to EPSON remote framebuffer chip and OMAP on-chip
- display controller and a LS041y3 MIPI DBI-C controller
-
-- TI TSC2301 (in N800) and TI TSC2005 (in N810) touchscreen
- controllers driven through SPI bus
-
-- National Semiconductor LM8323-controlled qwerty keyboard driven
- through |I2C| bus
-
-- Secure Digital card connected to OMAP MMC/SD host
-
-- Three OMAP on-chip UARTs and on-chip STI debugging console
-
-- Mentor Graphics \"Inventra\" dual-role USB controller embedded in a
- TI TUSB6010 chip - only USB host mode is supported
-
-- TI TMP105 temperature sensor driven through |I2C| bus
-
-- TI TWL92230C power management companion with an RTC on
- |I2C| bus
-
-- Nokia RETU and TAHVO multi-purpose chips with an RTC, connected
- through CBUS
-
-The Luminary Micro Stellaris LM3S811EVB emulation includes the following
-devices:
-
-- Cortex-M3 CPU core.
-
-- 64k Flash and 8k SRAM.
-
-- Timers, UARTs, ADC and |I2C| interface.
-
-- OSRAM Pictiva 96x16 OLED with SSD0303 controller on
- |I2C| bus.
-
-The Luminary Micro Stellaris LM3S6965EVB emulation includes the
-following devices:
-
-- Cortex-M3 CPU core.
-
-- 256k Flash and 64k SRAM.
-
-- Timers, UARTs, ADC, |I2C| and SSI interfaces.
-
-- OSRAM Pictiva 128x64 OLED with SSD0323 controller connected via
- SSI.
-
-The Freecom MusicPal internet radio emulation includes the following
-elements:
-
-- Marvell MV88W8618 ARM core.
-
-- 32 MB RAM, 256 KB SRAM, 8 MB flash.
-
-- Up to 2 16550 UARTs
-
-- MV88W8xx8 Ethernet controller
-
-- MV88W8618 audio controller, WM8750 CODEC and mixer
-
-- 128x64 display with brightness control
-
-- 2 buttons, 2 navigation wheels with button function
-
-The Siemens SX1 models v1 and v2 (default) basic emulation. The
-emulation includes the following elements:
-
-- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
-
-- ROM and RAM memories (ROM firmware image can be loaded with
- -pflash) V1 1 Flash of 16MB and 1 Flash of 8MB V2 1 Flash of 32MB
-
-- On-chip LCD controller
-
-- On-chip Real Time Clock
-
-- Secure Digital card connected to OMAP MMC/SD host
-
-- Three on-chip UARTs
-
-A Linux 2.6 test image is available on the QEMU web site. More
-information is available in the QEMU mailing-list archive.
+Use the executable ``qemu-system-arm`` to simulate a ARM machine.
+
+.. toctree::
+
+ arm/integratorcp
+ arm/versatile
+ arm/realview
+ arm/xscale
+ arm/palm
+ arm/nseries
+ arm/stellaris
+ arm/musicpal
+ arm/sx1
--
2.20.1
^ permalink raw reply related [flat|nested] 18+ messages in thread
* [PATCH 3/5] docs/system/target-arm.rst: Add some introductory text
2020-03-09 21:58 [PATCH 0/5] docs/system: Split target-arm.rst Peter Maydell
2020-03-09 21:58 ` [PATCH 1/5] Makefile: Allow for subdirectories in Sphinx manual dependencies Peter Maydell
2020-03-09 21:58 ` [PATCH 2/5] docs/system: Split target-arm.rst into sub-documents Peter Maydell
@ 2020-03-09 21:58 ` Peter Maydell
2020-03-10 14:54 ` Alex Bennée
2020-03-10 20:58 ` Niek Linnenbank
2020-03-09 21:58 ` [PATCH 4/5] docs: Move arm-cpu-features.rst into the system manual Peter Maydell
` (2 subsequent siblings)
5 siblings, 2 replies; 18+ messages in thread
From: Peter Maydell @ 2020-03-09 21:58 UTC (permalink / raw)
To: qemu-arm, qemu-devel; +Cc: Niek Linnenbank
Now we've moved the various bits of per-board documentation into
their own files, the top level document is a little bare. Add
some introductory information, including a note that many
of the board models we support are currently undocumented.
(Most sections of this new text were originally written by me
for the wiki page https://wiki.qemu.org/Documentation/Platforms/ARM)
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
---
docs/system/target-arm.rst | 66 ++++++++++++++++++++++++++++++++++++--
1 file changed, 64 insertions(+), 2 deletions(-)
diff --git a/docs/system/target-arm.rst b/docs/system/target-arm.rst
index c7df6fc1f97..86ea6f2f568 100644
--- a/docs/system/target-arm.rst
+++ b/docs/system/target-arm.rst
@@ -1,9 +1,71 @@
.. _ARM-System-emulator:
-ARM System emulator
+Arm System emulator
-------------------
-Use the executable ``qemu-system-arm`` to simulate a ARM machine.
+QEMU can emulate both 32-bit and 64-bit Arm CPUs. Use the
+``qemu-system-aarch64`` executable to simulate a 64-bit Arm machine.
+You can use either ``qemu-system-arm`` or ``qemu-system-aarch64``
+to simulate a 32-bit Arm machine: in general, command lines that
+work for ``qemu-system-arm`` will behave the same when used with
+``qemu-system-aarch64``.
+
+QEMU has generally good support for Arm guests. It has support for
+nearly fifty different machines. The reason we support so many is that
+Arm hardware is much more widely varying than x86 hardware. Arm CPUs
+are generally built into "system-on-chip" (SoC) designs created by
+many different companies with different devices, and these SoCs are
+then built into machines which can vary still further even if they use
+the same SoC. Even with fifty boards QEMU does not cover more than a
+small fraction of the Arm hardware ecosystem.
+
+The situation for 64-bit Arm is fairly similar, except that we don't
+implement so many different machines.
+
+As well as the more common "A-profile" CPUs (which have MMUs and will
+run Linux) QEMU also supports "M-profile" CPUs such as the Cortex-M0,
+Cortex-M4 and Cortex-M33 (which are microcontrollers used in very
+embedded boards). For most boards the CPU type is fixed (matching what
+the hardware has), so typically you don't need to specify the CPU type
+by hand, except for special cases like the ``virt`` board.
+
+Choosing a board model
+======================
+
+For QEMU's Arm system emulation, you must specify which board
+model you want to use with the ``-M`` or ``--machine`` option;
+there is no default.
+
+Because Arm systems differ so much and in fundamental ways, typically
+operating system or firmware images intended to run on one machine
+will not run at all on any other. This is often surprising for new
+users who are used to the x86 world where every system looks like a
+standard PC. (Once the kernel has booted, most userspace software
+cares much less about the detail of the hardware.)
+
+If you already have a system image or a kernel that works on hardware
+and you want to boot with QEMU, check whether QEMU lists that machine
+in its ``-machine help`` output. If it is listed, then you can probably
+use that board model. If it is not listed, then unfortunately your image
+will almost certainly not boot on QEMU. (You might be able to
+extract the filesystem and use that with a different kernel which
+boots on a system that QEMU does emulate.)
+
+If you don't care about reproducing the idiosyncrasies of a particular
+bit of hardware, such as small amount of RAM, no PCI or other hard
+disk, etc., and just want to run Linux, the best option is to use the
+``virt`` board. This is a platform which doesn't correspond to any
+real hardware and is designed for use in virtual machines. You'll
+need to compile Linux with a suitable configuration for running on
+the ``virt`` board. ``virt`` supports PCI, virtio, recent CPUs and
+large amounts of RAM. It also supports 64-bit CPUs.
+
+Board-specific documentation
+============================
+
+Unfortunately many of the Arm boards QEMU supports are currently
+undocumented; you can get a complete list by running
+``qemu-system-aarch64 --machine help``.
.. toctree::
--
2.20.1
^ permalink raw reply related [flat|nested] 18+ messages in thread
* [PATCH 4/5] docs: Move arm-cpu-features.rst into the system manual
2020-03-09 21:58 [PATCH 0/5] docs/system: Split target-arm.rst Peter Maydell
` (2 preceding siblings ...)
2020-03-09 21:58 ` [PATCH 3/5] docs/system/target-arm.rst: Add some introductory text Peter Maydell
@ 2020-03-09 21:58 ` Peter Maydell
2020-03-10 14:54 ` Alex Bennée
2020-03-10 21:00 ` Niek Linnenbank
2020-03-09 21:58 ` [PATCH 5/5] docs: Be consistent about capitalization of 'Arm' Peter Maydell
2020-03-09 22:45 ` [PATCH 0/5] docs/system: Split target-arm.rst no-reply
5 siblings, 2 replies; 18+ messages in thread
From: Peter Maydell @ 2020-03-09 21:58 UTC (permalink / raw)
To: qemu-arm, qemu-devel; +Cc: Niek Linnenbank
Now we have somewhere to put arm-specific rst documentation,
we can move arm-cpu-features.rst from the docs/ top level
directory into docs/system/arm/.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
.../{arm-cpu-features.rst => system/arm/cpu-features.rst} | 8 +-------
docs/system/target-arm.rst | 6 ++++++
2 files changed, 7 insertions(+), 7 deletions(-)
rename docs/{arm-cpu-features.rst => system/arm/cpu-features.rst} (99%)
diff --git a/docs/arm-cpu-features.rst b/docs/system/arm/cpu-features.rst
similarity index 99%
rename from docs/arm-cpu-features.rst
rename to docs/system/arm/cpu-features.rst
index fc1623aeca5..7495b7b672b 100644
--- a/docs/arm-cpu-features.rst
+++ b/docs/system/arm/cpu-features.rst
@@ -1,11 +1,5 @@
+Arm CPU Features
================
-ARM CPU Features
-================
-
-Examples of probing and using ARM CPU features
-
-Introduction
-============
CPU features are optional features that a CPU of supporting type may
choose to implement or not. In QEMU, optional CPU features have
diff --git a/docs/system/target-arm.rst b/docs/system/target-arm.rst
index 86ea6f2f568..1425bd5303a 100644
--- a/docs/system/target-arm.rst
+++ b/docs/system/target-arm.rst
@@ -78,3 +78,9 @@ undocumented; you can get a complete list by running
arm/stellaris
arm/musicpal
arm/sx1
+
+Arm CPU features
+================
+
+.. toctree::
+ arm/cpu-features
--
2.20.1
^ permalink raw reply related [flat|nested] 18+ messages in thread
* [PATCH 5/5] docs: Be consistent about capitalization of 'Arm'
2020-03-09 21:58 [PATCH 0/5] docs/system: Split target-arm.rst Peter Maydell
` (3 preceding siblings ...)
2020-03-09 21:58 ` [PATCH 4/5] docs: Move arm-cpu-features.rst into the system manual Peter Maydell
@ 2020-03-09 21:58 ` Peter Maydell
2020-03-10 14:55 ` Alex Bennée
2020-03-10 21:01 ` Niek Linnenbank
2020-03-09 22:45 ` [PATCH 0/5] docs/system: Split target-arm.rst no-reply
5 siblings, 2 replies; 18+ messages in thread
From: Peter Maydell @ 2020-03-09 21:58 UTC (permalink / raw)
To: qemu-arm, qemu-devel; +Cc: Niek Linnenbank
The company 'Arm' went through a rebranding some years back
involving a recapitalization from 'ARM' to 'Arm'. As a result
our documentation is a bit inconsistent between the two forms.
It's not worth trying to update everywhere in QEMU, but it's
easy enough to make docs/ consistent.
Note that "ARMv8" and similar architecture names, and
older CPU names like "ARM926" still retain all-caps.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
I don't feel very strongly about this change, but it
looked a bit odd where earlier rearrangements in this
series meant that some documents had a mix of both styles,
so I thought I might as well fix all of docs/.
---
docs/can.txt | 2 +-
docs/devel/atomics.txt | 2 +-
docs/devel/multi-thread-tcg.txt | 8 ++++----
docs/replay.txt | 2 +-
docs/specs/fw_cfg.txt | 2 +-
docs/devel/kconfig.rst | 2 +-
docs/devel/loads-stores.rst | 2 +-
docs/devel/tcg.rst | 2 +-
docs/specs/tpm.rst | 6 +++---
docs/system/arm/cpu-features.rst | 4 ++--
docs/system/arm/integratorcp.rst | 2 +-
docs/system/arm/musicpal.rst | 2 +-
docs/system/arm/nseries.rst | 2 +-
docs/system/arm/palm.rst | 2 +-
docs/system/arm/realview.rst | 4 ++--
docs/system/arm/sx1.rst | 2 +-
docs/system/arm/versatile.rst | 2 +-
docs/system/arm/xscale.rst | 2 +-
docs/user/main.rst | 8 ++++----
19 files changed, 29 insertions(+), 29 deletions(-)
diff --git a/docs/can.txt b/docs/can.txt
index 9fa6ed51c82..11ed8f2d68b 100644
--- a/docs/can.txt
+++ b/docs/can.txt
@@ -13,7 +13,7 @@ controller is implemented.
The PCI addon card hardware has been selected as the first CAN
interface to implement because such device can be easily connected
-to systems with different CPU architectures (x86, PowerPC, ARM, etc.).
+to systems with different CPU architectures (x86, PowerPC, Arm, etc.).
The project has been initially started in frame of RTEMS GSoC 2013
slot by Jin Yang under our mentoring The initial idea was to provide generic
diff --git a/docs/devel/atomics.txt b/docs/devel/atomics.txt
index a4db3a4aaad..67bdf826280 100644
--- a/docs/devel/atomics.txt
+++ b/docs/devel/atomics.txt
@@ -87,7 +87,7 @@ Sequentially consistent loads and stores can be done using:
atomic_xchg(ptr, val) for stores
However, they are quite expensive on some platforms, notably POWER and
-ARM. Therefore, qemu/atomic.h provides two primitives with slightly
+Arm. Therefore, qemu/atomic.h provides two primitives with slightly
weaker constraints:
typeof(*ptr) atomic_mb_read(ptr)
diff --git a/docs/devel/multi-thread-tcg.txt b/docs/devel/multi-thread-tcg.txt
index 782bebc28b4..3c85ac0eab9 100644
--- a/docs/devel/multi-thread-tcg.txt
+++ b/docs/devel/multi-thread-tcg.txt
@@ -227,7 +227,7 @@ minimise contention.
(Current solution)
MMIO access automatically serialises hardware emulation by way of the
-BQL. Currently ARM targets serialise all ARM_CP_IO register accesses
+BQL. Currently Arm targets serialise all ARM_CP_IO register accesses
and also defer the reset/startup of vCPUs to the vCPU context by way
of async_run_on_cpu().
@@ -268,7 +268,7 @@ ordered backends this could become a NOP.
Aside from explicit standalone memory barrier instructions there are
also implicit memory ordering semantics which comes with each guest
memory access instruction. For example all x86 load/stores come with
-fairly strong guarantees of sequential consistency where as ARM has
+fairly strong guarantees of sequential consistency whereas Arm has
special variants of load/store instructions that imply acquire/release
semantics.
@@ -317,7 +317,7 @@ x86 cmpxchg instruction.
The second type offer a pair of load/store instructions which offer a
guarantee that a region of memory has not been touched between the
-load and store instructions. An example of this is ARM's ldrex/strex
+load and store instructions. An example of this is Arm's ldrex/strex
pair where the strex instruction will return a flag indicating a
successful store only if no other CPU has accessed the memory region
since the ldrex.
@@ -339,7 +339,7 @@ CURRENT OPEN QUESTIONS:
The TCG provides a number of atomic helpers (tcg_gen_atomic_*) which
can be used directly or combined to emulate other instructions like
-ARM's ldrex/strex instructions. While they are susceptible to the ABA
+Arm's ldrex/strex instructions. While they are susceptible to the ABA
problem so far common guests have not implemented patterns where
this may be a problem - typically presenting a locking ABI which
assumes cmpxchg like semantics.
diff --git a/docs/replay.txt b/docs/replay.txt
index f4619a62a3d..70c27edb362 100644
--- a/docs/replay.txt
+++ b/docs/replay.txt
@@ -19,7 +19,7 @@ Deterministic replay has the following features:
the memory, state of the hardware devices, clocks, and screen of the VM.
* Writes execution log into the file for later replaying for multiple times
on different machines.
- * Supports i386, x86_64, and ARM hardware platforms.
+ * Supports i386, x86_64, and Arm hardware platforms.
* Performs deterministic replay of all operations with keyboard and mouse
input devices.
diff --git a/docs/specs/fw_cfg.txt b/docs/specs/fw_cfg.txt
index 08c00bdf44a..8f1ebc66fa4 100644
--- a/docs/specs/fw_cfg.txt
+++ b/docs/specs/fw_cfg.txt
@@ -82,7 +82,7 @@ Selector Register IOport: 0x510
Data Register IOport: 0x511
DMA Address IOport: 0x514
-=== ARM Register Locations ===
+=== Arm Register Locations ===
Selector Register address: Base + 8 (2 bytes)
Data Register address: Base + 0 (8 bytes)
diff --git a/docs/devel/kconfig.rst b/docs/devel/kconfig.rst
index b7bca447046..e5df72b3422 100644
--- a/docs/devel/kconfig.rst
+++ b/docs/devel/kconfig.rst
@@ -8,7 +8,7 @@ time different targets can share large amounts of code. For example,
a POWER and an x86 board can run the same code to emulate a PCI network
card, even though the boards use different PCI host bridges, and they
can run the same code to emulate a SCSI disk while using different
-SCSI adapters. ARM, s390 and x86 boards can all present a virtio-blk
+SCSI adapters. Arm, s390 and x86 boards can all present a virtio-blk
disk to their guests, but with three different virtio guest interfaces.
Each QEMU target enables a subset of the boards, devices and buses that
diff --git a/docs/devel/loads-stores.rst b/docs/devel/loads-stores.rst
index 03aa9e7ff80..0d99eb24c1b 100644
--- a/docs/devel/loads-stores.rst
+++ b/docs/devel/loads-stores.rst
@@ -302,7 +302,7 @@ way QEMU defines the view of memory that a device or CPU has.
or bus fabric.)
Each CPU has an AddressSpace. Some kinds of CPU have more than
-one AddressSpace (for instance ARM guest CPUs have an AddressSpace
+one AddressSpace (for instance Arm guest CPUs have an AddressSpace
for the Secure world and one for NonSecure if they implement TrustZone).
Devices which can do DMA-type operations should generally have an
AddressSpace. There is also a "system address space" which typically
diff --git a/docs/devel/tcg.rst b/docs/devel/tcg.rst
index 4956a30a4e6..4ebde44b9d7 100644
--- a/docs/devel/tcg.rst
+++ b/docs/devel/tcg.rst
@@ -83,7 +83,7 @@ memory until the end of the translation block. This is done for internal
emulation state that is rarely accessed directly by the program and/or changes
very often throughout the execution of a translation block---this includes
condition codes on x86, delay slots on SPARC, conditional execution on
-ARM, and so on. This state is stored for each target instruction, and
+Arm, and so on. This state is stored for each target instruction, and
looked up on exceptions.
MMU emulation
diff --git a/docs/specs/tpm.rst b/docs/specs/tpm.rst
index da9eb39ca97..5e61238bc5f 100644
--- a/docs/specs/tpm.rst
+++ b/docs/specs/tpm.rst
@@ -25,7 +25,7 @@ QEMU files related to TPM TIS interface:
Both an ISA device and a sysbus device are available. The former is
used with pc/q35 machine while the latter can be instantiated in the
-ARM virt machine.
+Arm virt machine.
CRB interface
-------------
@@ -331,7 +331,7 @@ In case a pSeries machine is emulated, use the following command line:
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0 \
-drive file=test.img,format=raw,if=none,id=drive-virtio-disk0
-In case an ARM virt machine is emulated, use the following command line:
+In case an Arm virt machine is emulated, use the following command line:
.. code-block:: console
@@ -346,7 +346,7 @@ In case an ARM virt machine is emulated, use the following command line:
-drive if=pflash,format=raw,file=flash0.img,readonly \
-drive if=pflash,format=raw,file=flash1.img
- On ARM, ACPI boot with TPM is not yet supported.
+ On Arm, ACPI boot with TPM is not yet supported.
In case SeaBIOS is used as firmware, it should show the TPM menu item
after entering the menu with 'ESC'.
diff --git a/docs/system/arm/cpu-features.rst b/docs/system/arm/cpu-features.rst
index 7495b7b672b..2d5c06cd016 100644
--- a/docs/system/arm/cpu-features.rst
+++ b/docs/system/arm/cpu-features.rst
@@ -5,9 +5,9 @@ CPU features are optional features that a CPU of supporting type may
choose to implement or not. In QEMU, optional CPU features have
corresponding boolean CPU proprieties that, when enabled, indicate
that the feature is implemented, and, conversely, when disabled,
-indicate that it is not implemented. An example of an ARM CPU feature
+indicate that it is not implemented. An example of an Arm CPU feature
is the Performance Monitoring Unit (PMU). CPU types such as the
-Cortex-A15 and the Cortex-A57, which respectively implement ARM
+Cortex-A15 and the Cortex-A57, which respectively implement Arm
architecture reference manuals ARMv7-A and ARMv8-A, may both optionally
implement PMUs. For example, if a user wants to use a Cortex-A15 without
a PMU, then the `-cpu` parameter should contain `pmu=off` on the QEMU
diff --git a/docs/system/arm/integratorcp.rst b/docs/system/arm/integratorcp.rst
index 3232b43a08b..e6f050f602b 100644
--- a/docs/system/arm/integratorcp.rst
+++ b/docs/system/arm/integratorcp.rst
@@ -1,7 +1,7 @@
Integrator/CP (``integratorcp``)
================================
-The ARM Integrator/CP board is emulated with the following devices:
+The Arm Integrator/CP board is emulated with the following devices:
- ARM926E, ARM1026E, ARM946E, ARM1136 or Cortex-A8 CPU
diff --git a/docs/system/arm/musicpal.rst b/docs/system/arm/musicpal.rst
index 35c22212486..9de380edf81 100644
--- a/docs/system/arm/musicpal.rst
+++ b/docs/system/arm/musicpal.rst
@@ -4,7 +4,7 @@ Freecom MusicPal (``musicpal``)
The Freecom MusicPal internet radio emulation includes the following
elements:
-- Marvell MV88W8618 ARM core.
+- Marvell MV88W8618 Arm core.
- 32 MB RAM, 256 KB SRAM, 8 MB flash.
diff --git a/docs/system/arm/nseries.rst b/docs/system/arm/nseries.rst
index b000b6d13bb..cd9edf5d88b 100644
--- a/docs/system/arm/nseries.rst
+++ b/docs/system/arm/nseries.rst
@@ -4,7 +4,7 @@ Nokia N800 and N810 tablets (``n800``, ``n810``)
Nokia N800 and N810 internet tablets (known also as RX-34 and RX-44 /
48) emulation supports the following elements:
-- Texas Instruments OMAP2420 System-on-chip (ARM 1136 core)
+- Texas Instruments OMAP2420 System-on-chip (ARM1136 core)
- RAM and non-volatile OneNAND Flash memories
diff --git a/docs/system/arm/palm.rst b/docs/system/arm/palm.rst
index 0eabf63e0e7..47ff9b36d46 100644
--- a/docs/system/arm/palm.rst
+++ b/docs/system/arm/palm.rst
@@ -4,7 +4,7 @@ Palm Tungsten|E PDA (``cheetah``)
The Palm Tungsten|E PDA (codename \"Cheetah\") emulation includes the
following elements:
-- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
+- Texas Instruments OMAP310 System-on-chip (ARM925T core)
- ROM and RAM memories (ROM firmware image can be loaded with
-option-rom)
diff --git a/docs/system/arm/realview.rst b/docs/system/arm/realview.rst
index 8e08eb5da16..65f5be346b1 100644
--- a/docs/system/arm/realview.rst
+++ b/docs/system/arm/realview.rst
@@ -1,7 +1,7 @@
Arm Realview boards (``realview-eb``, ``realview-eb-mpcore``, ``realview-pb-a8``, ``realview-pbx-a9``)
======================================================================================================
-Several variants of the ARM RealView baseboard are emulated, including
+Several variants of the Arm RealView baseboard are emulated, including
the EB, PB-A8 and PBX-A9. Due to interactions with the bootloader, only
certain Linux kernel configurations work out of the box on these boards.
@@ -14,7 +14,7 @@ The following devices are emulated:
- ARM926E, ARM1136, ARM11MPCore, Cortex-A8 or Cortex-A9 MPCore CPU
-- ARM AMBA Generic/Distributed Interrupt Controller
+- Arm AMBA Generic/Distributed Interrupt Controller
- Four PL011 UARTs
diff --git a/docs/system/arm/sx1.rst b/docs/system/arm/sx1.rst
index 321993bc098..8bce30d4b25 100644
--- a/docs/system/arm/sx1.rst
+++ b/docs/system/arm/sx1.rst
@@ -4,7 +4,7 @@ Siemens SX1 (``sx1``, ``sx1-v1``)
The Siemens SX1 models v1 and v2 (default) basic emulation. The
emulation includes the following elements:
-- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
+- Texas Instruments OMAP310 System-on-chip (ARM925T core)
- ROM and RAM memories (ROM firmware image can be loaded with
-pflash) V1 1 Flash of 16MB and 1 Flash of 8MB V2 1 Flash of 32MB
diff --git a/docs/system/arm/versatile.rst b/docs/system/arm/versatile.rst
index 48b6ca0a020..51221c30a48 100644
--- a/docs/system/arm/versatile.rst
+++ b/docs/system/arm/versatile.rst
@@ -1,7 +1,7 @@
Arm Versatile boards (``versatileab``, ``versatilepb``)
=======================================================
-The ARM Versatile baseboard is emulated with the following devices:
+The Arm Versatile baseboard is emulated with the following devices:
- ARM926E, ARM1136 or Cortex-A8 CPU
diff --git a/docs/system/arm/xscale.rst b/docs/system/arm/xscale.rst
index 19da2eff352..89ec93e904e 100644
--- a/docs/system/arm/xscale.rst
+++ b/docs/system/arm/xscale.rst
@@ -4,7 +4,7 @@ Sharp XScale-based PDA models (``akita``, ``borzoi``, ``spitz``, ``terrier``)
The XScale-based clamshell PDA models (\"Spitz\", \"Akita\", \"Borzoi\"
and \"Terrier\") emulation includes the following peripherals:
-- Intel PXA270 System-on-chip (ARM V5TE core)
+- Intel PXA270 System-on-chip (ARMv5TE core)
- NAND Flash memory
diff --git a/docs/user/main.rst b/docs/user/main.rst
index ca69f7727d5..bd99b0fdbe9 100644
--- a/docs/user/main.rst
+++ b/docs/user/main.rst
@@ -35,7 +35,7 @@ QEMU user space emulation has the following notable features:
On Linux, QEMU can emulate the ``clone`` syscall and create a real
host thread (with a separate virtual CPU) for each emulated thread.
Note that not all targets currently emulate atomic operations
- correctly. x86 and ARM use a global lock in order to preserve their
+ correctly. x86 and Arm use a global lock in order to preserve their
semantics.
QEMU was conceived so that ultimately it can emulate itself. Although it
@@ -173,11 +173,11 @@ Other binaries
user mode (Alpha)
``qemu-alpha`` TODO.
-user mode (ARM)
+user mode (Arm)
``qemu-armeb`` TODO.
-user mode (ARM)
-``qemu-arm`` is also capable of running ARM \"Angel\" semihosted ELF
+user mode (Arm)
+``qemu-arm`` is also capable of running Arm \"Angel\" semihosted ELF
binaries (as implemented by the arm-elf and arm-eabi Newlib/GDB
configurations), and arm-uclinux bFLT format binaries.
--
2.20.1
^ permalink raw reply related [flat|nested] 18+ messages in thread
* Re: [PATCH 0/5] docs/system: Split target-arm.rst
2020-03-09 21:58 [PATCH 0/5] docs/system: Split target-arm.rst Peter Maydell
` (4 preceding siblings ...)
2020-03-09 21:58 ` [PATCH 5/5] docs: Be consistent about capitalization of 'Arm' Peter Maydell
@ 2020-03-09 22:45 ` no-reply
5 siblings, 0 replies; 18+ messages in thread
From: no-reply @ 2020-03-09 22:45 UTC (permalink / raw)
To: peter.maydell; +Cc: nieklinnenbank, qemu-arm, qemu-devel
Patchew URL: https://patchew.org/QEMU/20200309215818.2021-1-peter.maydell@linaro.org/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
export ARCH=x86_64
make docker-image-fedora V=1 NETWORK=1
time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
=== TEST SCRIPT END ===
PASS 1 fdc-test /x86_64/fdc/cmos
PASS 2 fdc-test /x86_64/fdc/no_media_on_start
PASS 3 fdc-test /x86_64/fdc/read_without_media
==6146==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 4 fdc-test /x86_64/fdc/media_change
PASS 5 fdc-test /x86_64/fdc/sense_interrupt
PASS 6 fdc-test /x86_64/fdc/relative_seek
---
PASS 32 test-opts-visitor /visitor/opts/range/beyond
PASS 33 test-opts-visitor /visitor/opts/dict/unvisited
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-coroutine -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-coroutine"
==6194==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6194==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7fff994a9000; bottom 0x7f101d9a5000; size: 0x00ef7bb04000 (1028572332032)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 1 test-coroutine /basic/no-dangling-access
---
PASS 11 test-aio /aio/event/wait
PASS 12 test-aio /aio/event/flush
PASS 13 test-aio /aio/event/wait/no-flush-cb
==6209==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 14 test-aio /aio/timer/schedule
PASS 15 test-aio /aio/coroutine/queue-chaining
PASS 16 test-aio /aio-gsource/flush
---
PASS 12 fdc-test /x86_64/fdc/read_no_dma_19
PASS 13 fdc-test /x86_64/fdc/fuzz-registers
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 QTEST_QEMU_IMG=qemu-img tests/qtest/ide-test -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="ide-test"
==6217==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 ide-test /x86_64/ide/identify
PASS 28 test-aio /aio-gsource/timer/schedule
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-aio-multithread -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-aio-multithread"
==6223==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6227==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-aio-multithread /aio/multi/lifecycle
PASS 2 ide-test /x86_64/ide/flush
==6243==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 2 test-aio-multithread /aio/multi/schedule
PASS 3 ide-test /x86_64/ide/bmdma/simple_rw
==6254==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 4 ide-test /x86_64/ide/bmdma/trim
PASS 3 test-aio-multithread /aio/multi/mutex/contended
==6260==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 4 test-aio-multithread /aio/multi/mutex/handoff
PASS 5 test-aio-multithread /aio/multi/mutex/mcs
PASS 6 test-aio-multithread /aio/multi/mutex/pthread
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-throttle -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-throttle"
==6282==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-throttle /throttle/leak_bucket
PASS 2 test-throttle /throttle/compute_wait
PASS 3 test-throttle /throttle/init
---
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-thread-pool -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-thread-pool"
PASS 1 test-thread-pool /thread-pool/submit
PASS 2 test-thread-pool /thread-pool/submit-aio
==6288==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 3 test-thread-pool /thread-pool/submit-co
PASS 4 test-thread-pool /thread-pool/submit-many
==6284==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 5 test-thread-pool /thread-pool/cancel
PASS 6 test-thread-pool /thread-pool/cancel-async
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-hbitmap -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-hbitmap"
---
PASS 13 test-hbitmap /hbitmap/set/general
PASS 14 test-hbitmap /hbitmap/set/twice
PASS 15 test-hbitmap /hbitmap/set/overlap
==6363==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 16 test-hbitmap /hbitmap/reset/empty
PASS 17 test-hbitmap /hbitmap/reset/general
PASS 18 test-hbitmap /hbitmap/reset/all
---
PASS 28 test-hbitmap /hbitmap/truncate/shrink/medium
PASS 29 test-hbitmap /hbitmap/truncate/shrink/large
PASS 30 test-hbitmap /hbitmap/meta/zero
==6369==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 31 test-hbitmap /hbitmap/meta/one
PASS 32 test-hbitmap /hbitmap/meta/byte
PASS 33 test-hbitmap /hbitmap/meta/word
---
PASS 44 test-hbitmap /hbitmap/next_dirty_area/next_dirty_area_4
PASS 45 test-hbitmap /hbitmap/next_dirty_area/next_dirty_area_after_truncate
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-bdrv-drain -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-bdrv-drain"
==6376==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-bdrv-drain /bdrv-drain/nested
PASS 2 test-bdrv-drain /bdrv-drain/multiparent
PASS 3 test-bdrv-drain /bdrv-drain/set_aio_context
---
PASS 41 test-bdrv-drain /bdrv-drain/bdrv_drop_intermediate/poll
PASS 42 test-bdrv-drain /bdrv-drain/replace_child/mid-drain
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-bdrv-graph-mod -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-bdrv-graph-mod"
==6415==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-bdrv-graph-mod /bdrv-graph-mod/update-perm-tree
PASS 2 test-bdrv-graph-mod /bdrv-graph-mod/should-update-child
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-blockjob -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-blockjob"
==6419==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-blockjob /blockjob/ids
PASS 2 test-blockjob /blockjob/cancel/created
PASS 3 test-blockjob /blockjob/cancel/running
---
PASS 7 test-blockjob /blockjob/cancel/pending
PASS 8 test-blockjob /blockjob/cancel/concluded
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-blockjob-txn -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-blockjob-txn"
==6423==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-blockjob-txn /single/success
PASS 2 test-blockjob-txn /single/failure
PASS 3 test-blockjob-txn /single/cancel
---
PASS 6 test-blockjob-txn /pair/cancel
PASS 7 test-blockjob-txn /pair/fail-cancel-race
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-block-backend -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-block-backend"
==6427==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-block-backend /block-backend/drain_aio_error
PASS 2 test-block-backend /block-backend/drain_all_aio_error
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-block-iothread -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-block-iothread"
==6431==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-block-iothread /sync-op/pread
PASS 2 test-block-iothread /sync-op/pwrite
PASS 3 test-block-iothread /sync-op/load_vmstate
---
PASS 15 test-block-iothread /propagate/diamond
PASS 16 test-block-iothread /propagate/mirror
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-image-locking -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-image-locking"
==6451==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-image-locking /image-locking/basic
PASS 2 test-image-locking /image-locking/set-perm-abort
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-x86-cpuid -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-x86-cpuid"
---
PASS 3 test-xbzrle /xbzrle/encode_decode_unchanged
PASS 4 test-xbzrle /xbzrle/encode_decode_1_byte
PASS 5 test-xbzrle /xbzrle/encode_decode_overflow
==6458==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 6 test-xbzrle /xbzrle/encode_decode
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-vmstate -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-vmstate"
PASS 1 test-vmstate /vmstate/tmp_struct
---
PASS 2 rcutorture /rcu/torture/10readers
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-rcu-list -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-rcu-list"
PASS 1 test-rcu-list /rcu/qlist/single-threaded
==6515==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 2 test-rcu-list /rcu/qlist/short-few
PASS 3 test-rcu-list /rcu/qlist/long-many
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-rcu-simpleq -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-rcu-simpleq"
PASS 1 test-rcu-simpleq /rcu/qsimpleq/single-threaded
PASS 2 test-rcu-simpleq /rcu/qsimpleq/short-few
==6581==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 3 test-rcu-simpleq /rcu/qsimpleq/long-many
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-rcu-tailq -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-rcu-tailq"
PASS 1 test-rcu-tailq /rcu/qtailq/single-threaded
PASS 2 test-rcu-tailq /rcu/qtailq/short-few
PASS 3 test-rcu-tailq /rcu/qtailq/long-many
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-rcu-slist -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-rcu-slist"
==6620==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-rcu-slist /rcu/qslist/single-threaded
PASS 2 test-rcu-slist /rcu/qslist/short-few
PASS 3 test-rcu-slist /rcu/qslist/long-many
---
PASS 7 test-qdist /qdist/binning/expand
PASS 8 test-qdist /qdist/binning/shrink
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-qht -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-qht"
==6666==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 5 ide-test /x86_64/ide/bmdma/various_prdts
==6672==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6672==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffe7b88a000; bottom 0x7f4cfd146000; size: 0x00b17e744000 (762330759168)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 6 ide-test /x86_64/ide/bmdma/no_busmaster
PASS 7 ide-test /x86_64/ide/flush/nodev
==6683==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 8 ide-test /x86_64/ide/flush/empty_drive
==6688==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 9 ide-test /x86_64/ide/flush/retry_pci
==6694==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 10 ide-test /x86_64/ide/flush/retry_isa
==6700==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 11 ide-test /x86_64/ide/cdrom/pio
==6706==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 12 ide-test /x86_64/ide/cdrom/pio_large
PASS 1 test-qht /qht/mode/default
PASS 2 test-qht /qht/mode/resize
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-qht-par -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-qht-par"
==6712==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 13 ide-test /x86_64/ide/cdrom/dma
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 QTEST_QEMU_IMG=qemu-img tests/qtest/ahci-test -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="ahci-test"
PASS 1 test-qht-par /qht/parallel/2threads-0%updates-1s
==6735==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 ahci-test /x86_64/ahci/sanity
==6747==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 2 test-qht-par /qht/parallel/2threads-20%updates-1s
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-bitops -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-bitops"
PASS 2 ahci-test /x86_64/ahci/pci_spec
---
PASS 3 test-qdev-global-props /qdev/properties/dynamic/global
PASS 4 test-qdev-global-props /qdev/properties/global/subclass
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/check-qom-interface -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="check-qom-interface"
==6756==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 3 ahci-test /x86_64/ahci/pci_enable
PASS 1 check-qom-interface /qom/interface/direct_impl
PASS 2 check-qom-interface /qom/interface/intermediate_impl
---
PASS 18 test-qemu-opts /qemu-opts/to_qdict/filtered
PASS 19 test-qemu-opts /qemu-opts/to_qdict/duplicates
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-keyval -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-keyval"
==6783==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-keyval /keyval/keyval_parse
PASS 2 test-keyval /keyval/keyval_parse/list
PASS 3 test-keyval /keyval/visit/bool
---
PASS 3 test-crypto-hmac /crypto/hmac/prealloc
PASS 4 test-crypto-hmac /crypto/hmac/digest
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-crypto-cipher -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-crypto-cipher"
==6804==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-crypto-cipher /crypto/cipher/aes-ecb-128
PASS 2 test-crypto-cipher /crypto/cipher/aes-ecb-192
PASS 3 test-crypto-cipher /crypto/cipher/aes-ecb-256
---
PASS 15 test-crypto-secret /crypto/secret/crypt/missingiv
PASS 16 test-crypto-secret /crypto/secret/crypt/badiv
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-crypto-tlscredsx509 -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-crypto-tlscredsx509"
==6827==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/perfectserver
PASS 2 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/perfectclient
PASS 3 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/goodca1
PASS 6 ahci-test /x86_64/ahci/identify
==6837==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 7 ahci-test /x86_64/ahci/max
==6843==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 4 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/goodca2
PASS 8 ahci-test /x86_64/ahci/reset
PASS 5 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/goodca3
---
PASS 8 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/badca3
PASS 9 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/goodserver1
PASS 10 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/goodserver2
==6849==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6849==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffc59272000; bottom 0x7f01613fe000; size: 0x00faf7e74000 (1077900951552)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 9 ahci-test /x86_64/ahci/io/pio/lba28/simple/zero
PASS 11 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/goodserver3
==6855==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 12 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/goodserver4
==6855==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffd9d6e2000; bottom 0x7f46df1fe000; size: 0x00b6be4e4000 (784876847104)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 10 ahci-test /x86_64/ahci/io/pio/lba28/simple/low
PASS 13 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/goodserver5
==6861==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6861==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7fff18d4a000; bottom 0x7facc73fe000; size: 0x00525194c000 (353556021248)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 11 ahci-test /x86_64/ahci/io/pio/lba28/simple/high
PASS 14 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/goodserver6
==6867==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6867==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7fff98b65000; bottom 0x7fb857dfe000; size: 0x004740d67000 (306030473216)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 12 ahci-test /x86_64/ahci/io/pio/lba28/double/zero
---
PASS 32 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/inactive1
PASS 33 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/inactive2
PASS 34 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/inactive3
==6873==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6873==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7fff033f3000; bottom 0x7f38c01fe000; size: 0x00c6431f5000 (851529650176)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 35 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/chain1
---
PASS 39 test-crypto-tlscredsx509 /qcrypto/tlscredsx509/missingclient
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-crypto-tlssession -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-crypto-tlssession"
PASS 13 ahci-test /x86_64/ahci/io/pio/lba28/double/low
==6882==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6882==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffe1965e000; bottom 0x7f70e65fe000; size: 0x008d33060000 (606446419968)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 1 test-crypto-tlssession /qcrypto/tlssession/psk
PASS 14 ahci-test /x86_64/ahci/io/pio/lba28/double/high
==6889==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6889==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffecc601000; bottom 0x7fc3ad17c000; size: 0x003b1f485000 (253927903232)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 2 test-crypto-tlssession /qcrypto/tlssession/basicca
PASS 15 ahci-test /x86_64/ahci/io/pio/lba28/long/zero
PASS 3 test-crypto-tlssession /qcrypto/tlssession/differentca
PASS 4 test-crypto-tlssession /qcrypto/tlssession/altname1
==6895==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 5 test-crypto-tlssession /qcrypto/tlssession/altname2
==6895==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffc9a71f000; bottom 0x7fa3c9124000; size: 0x0058d15fb000 (381469831168)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 16 ahci-test /x86_64/ahci/io/pio/lba28/long/low
==6901==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6901==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffc0dc7d000; bottom 0x7faa35d24000; size: 0x0051d7f59000 (351515545600)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 17 ahci-test /x86_64/ahci/io/pio/lba28/long/high
PASS 6 test-crypto-tlssession /qcrypto/tlssession/altname3
==6907==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 7 test-crypto-tlssession /qcrypto/tlssession/altname4
PASS 18 ahci-test /x86_64/ahci/io/pio/lba28/short/zero
==6913==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 19 ahci-test /x86_64/ahci/io/pio/lba28/short/low
==6919==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 20 ahci-test /x86_64/ahci/io/pio/lba28/short/high
PASS 8 test-crypto-tlssession /qcrypto/tlssession/altname5
==6925==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 9 test-crypto-tlssession /qcrypto/tlssession/altname6
==6925==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffc3d122000; bottom 0x7fa0435fe000; size: 0x005bf9b24000 (395031232512)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 21 ahci-test /x86_64/ahci/io/pio/lba48/simple/zero
==6931==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 10 test-crypto-tlssession /qcrypto/tlssession/wildcard1
==6931==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffff6ed0000; bottom 0x7efd4a9fe000; size: 0x0102ac4d2000 (1110992297984)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 11 test-crypto-tlssession /qcrypto/tlssession/wildcard2
PASS 12 test-crypto-tlssession /qcrypto/tlssession/wildcard3
PASS 22 ahci-test /x86_64/ahci/io/pio/lba48/simple/low
PASS 13 test-crypto-tlssession /qcrypto/tlssession/wildcard4
==6937==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6937==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffeb2cb6000; bottom 0x7f67707fe000; size: 0x0097424b8000 (649652305920)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 23 ahci-test /x86_64/ahci/io/pio/lba48/simple/high
==6943==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6943==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffffe6d2000; bottom 0x7f18511fe000; size: 0x00e7ad4d4000 (995044966400)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 14 test-crypto-tlssession /qcrypto/tlssession/wildcard5
---
PASS 15 test-crypto-tlssession /qcrypto/tlssession/wildcard6
PASS 16 test-crypto-tlssession /qcrypto/tlssession/cachain
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-qga -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-qga"
==6949==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6949==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffda4650000; bottom 0x7f5d78bfe000; size: 0x00a02ba52000 (687927009280)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 25 ahci-test /x86_64/ahci/io/pio/lba48/double/low
==6963==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-qga /qga/sync-delimited
PASS 2 test-qga /qga/sync
PASS 3 test-qga /qga/ping
---
PASS 6 test-qga /qga/get-vcpus
PASS 7 test-qga /qga/get-fsinfo
PASS 8 test-qga /qga/get-memory-block-info
==6963==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffe3aa8f000; bottom 0x7f499e1fe000; size: 0x00b49c891000 (775720341504)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 9 test-qga /qga/get-memory-blocks
---
PASS 16 test-qga /qga/invalid-args
PASS 17 test-qga /qga/fsfreeze-status
PASS 26 ahci-test /x86_64/ahci/io/pio/lba48/double/high
==6972==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6972==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7fff2bec7000; bottom 0x7f06f69fe000; size: 0x00f8354c9000 (1066046099456)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 18 test-qga /qga/blacklist
---
PASS 19 test-qga /qga/config
PASS 20 test-qga /qga/guest-exec
PASS 21 test-qga /qga/guest-exec-invalid
==6982==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==6982==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffda1e3b000; bottom 0x7f860317c000; size: 0x00779ecbf000 (513765273600)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 28 ahci-test /x86_64/ahci/io/pio/lba48/long/low
---
PASS 24 test-qga /qga/guest-get-timezone
PASS 25 test-qga /qga/guest-get-users
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-timed-average -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-timed-average"
==6996==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-timed-average /timed-average/average
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-util-filemonitor -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-util-filemonitor"
PASS 1 test-util-filemonitor /util/filemonitor
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-util-sockets -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-util-sockets"
==6996==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffec759b000; bottom 0x7f6309724000; size: 0x009bbde77000 (668905992192)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 1 test-util-sockets /util/socket/is-socket/bad
---
PASS 4 test-authz-listfile /auth/list/explicit/deny
PASS 5 test-authz-listfile /auth/list/explicit/allow
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-io-task -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-io-task"
==7020==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-io-task /crypto/task/complete
PASS 2 test-io-task /crypto/task/datafree
PASS 3 test-io-task /crypto/task/failure
---
PASS 4 test-io-channel-file /io/channel/pipe/sync
PASS 5 test-io-channel-file /io/channel/pipe/async
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-io-channel-tls -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-io-channel-tls"
==7083==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-io-channel-tls /qio/channel/tls/basic
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-io-channel-command -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-io-channel-command"
PASS 31 ahci-test /x86_64/ahci/io/pio/lba48/short/low
---
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-io-channel-buffer -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-io-channel-buffer"
PASS 1 test-io-channel-buffer /io/channel/buf
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-base64 -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-base64"
==7106==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-base64 /util/base64/good
PASS 2 test-base64 /util/base64/embedded-nul
PASS 3 test-base64 /util/base64/not-nul-terminated
---
PASS 8 test-crypto-ivgen /crypto/ivgen/essiv/1f2e3d4c
PASS 9 test-crypto-ivgen /crypto/ivgen/essiv/1f2e3d4c5b6a7988
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-crypto-afsplit -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-crypto-afsplit"
==7127==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 1 test-crypto-afsplit /crypto/afsplit/sha256/5
PASS 2 test-crypto-afsplit /crypto/afsplit/sha256/5000
PASS 3 test-crypto-afsplit /crypto/afsplit/sha256/big
---
PASS 4 test-logging /logging/logfile_lock_path
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-replication -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-replication"
PASS 33 ahci-test /x86_64/ahci/io/dma/lba28/fragmented
==7150==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7152==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 34 ahci-test /x86_64/ahci/io/dma/lba28/retry
PASS 1 test-replication /replication/primary/read
==7160==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 2 test-replication /replication/primary/write
PASS 35 ahci-test /x86_64/ahci/io/dma/lba28/simple/zero
PASS 3 test-replication /replication/primary/start
PASS 4 test-replication /replication/primary/stop
PASS 5 test-replication /replication/primary/do_checkpoint
PASS 6 test-replication /replication/primary/get_error_all
==7166==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 36 ahci-test /x86_64/ahci/io/dma/lba28/simple/low
==7172==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 7 test-replication /replication/secondary/read
PASS 37 ahci-test /x86_64/ahci/io/dma/lba28/simple/high
==7178==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 8 test-replication /replication/secondary/write
PASS 38 ahci-test /x86_64/ahci/io/dma/lba28/double/zero
==7184==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 39 ahci-test /x86_64/ahci/io/dma/lba28/double/low
==7190==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 40 ahci-test /x86_64/ahci/io/dma/lba28/double/high
==7196==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7196==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffe30019000; bottom 0x7f66d31fd000; size: 0x00975ce1c000 (650098360320)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 41 ahci-test /x86_64/ahci/io/dma/lba28/long/zero
==7204==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7150==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffdb8484000; bottom 0x7fb55b3ef000; size: 0x00485d095000 (310798536704)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
==7204==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7fff34023000; bottom 0x7f175cb7b000; size: 0x00e7d74a8000 (995749429248)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 9 test-replication /replication/secondary/start
PASS 42 ahci-test /x86_64/ahci/io/dma/lba28/long/low
==7228==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7228==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffe50fb1000; bottom 0x7f419c7fd000; size: 0x00bcb47b4000 (810481827840)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 43 ahci-test /x86_64/ahci/io/dma/lba28/long/high
==7235==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 44 ahci-test /x86_64/ahci/io/dma/lba28/short/zero
==7241==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 45 ahci-test /x86_64/ahci/io/dma/lba28/short/low
PASS 10 test-replication /replication/secondary/stop
==7247==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 46 ahci-test /x86_64/ahci/io/dma/lba28/short/high
==7253==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 47 ahci-test /x86_64/ahci/io/dma/lba48/simple/zero
==7259==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 48 ahci-test /x86_64/ahci/io/dma/lba48/simple/low
PASS 11 test-replication /replication/secondary/continuous_replication
==7265==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 49 ahci-test /x86_64/ahci/io/dma/lba48/simple/high
==7271==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 50 ahci-test /x86_64/ahci/io/dma/lba48/double/zero
==7277==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 12 test-replication /replication/secondary/do_checkpoint
PASS 51 ahci-test /x86_64/ahci/io/dma/lba48/double/low
==7283==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 13 test-replication /replication/secondary/get_error_all
PASS 52 ahci-test /x86_64/ahci/io/dma/lba48/double/high
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-bufferiszero -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-bufferiszero"
==7289==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7289==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7fff837b4000; bottom 0x7f7cfed7b000; size: 0x008284a39000 (560571060224)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 53 ahci-test /x86_64/ahci/io/dma/lba48/long/zero
==7299==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7299==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffeeb54b000; bottom 0x7fe82b5fd000; size: 0x0016bff4e000 (97709776896)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 54 ahci-test /x86_64/ahci/io/dma/lba48/long/low
==7306==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7306==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffc83f01000; bottom 0x7ffbd1bfd000; size: 0x0000b2304000 (2989506560)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 55 ahci-test /x86_64/ahci/io/dma/lba48/long/high
==7313==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 56 ahci-test /x86_64/ahci/io/dma/lba48/short/zero
==7319==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 57 ahci-test /x86_64/ahci/io/dma/lba48/short/low
==7325==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 58 ahci-test /x86_64/ahci/io/dma/lba48/short/high
==7331==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 59 ahci-test /x86_64/ahci/io/ncq/simple
==7337==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 60 ahci-test /x86_64/ahci/io/ncq/retry
==7343==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 61 ahci-test /x86_64/ahci/flush/simple
==7349==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 62 ahci-test /x86_64/ahci/flush/retry
==7355==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7361==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 63 ahci-test /x86_64/ahci/flush/migrate
==7369==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7375==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 64 ahci-test /x86_64/ahci/migrate/sanity
==7383==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7389==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 65 ahci-test /x86_64/ahci/migrate/dma/simple
==7397==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7403==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 66 ahci-test /x86_64/ahci/migrate/dma/halted
==7411==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7417==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 67 ahci-test /x86_64/ahci/migrate/ncq/simple
==7425==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7431==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 68 ahci-test /x86_64/ahci/migrate/ncq/halted
==7439==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 69 ahci-test /x86_64/ahci/cdrom/eject
==7444==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 70 ahci-test /x86_64/ahci/cdrom/dma/single
==7450==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 71 ahci-test /x86_64/ahci/cdrom/dma/multi
==7456==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 72 ahci-test /x86_64/ahci/cdrom/pio/single
==7462==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7462==WARNING: ASan is ignoring requested __asan_handle_no_return: stack top: 0x7ffdacd48000; bottom 0x7f36bfdfe000; size: 0x00c6ecf4a000 (854378979328)
False positive error reports may follow
For details see https://github.com/google/sanitizers/issues/189
PASS 73 ahci-test /x86_64/ahci/cdrom/pio/multi
---
PASS 527 ptimer-test /ptimer/periodic_with_load_0 policy=wrap_after_one_period,continuous_trigger,no_immediate_reload,no_counter_rounddown,trigger_only_on_decrement,
PASS 528 ptimer-test /ptimer/oneshot_with_load_0 policy=wrap_after_one_period,continuous_trigger,no_immediate_reload,no_counter_rounddown,trigger_only_on_decrement,
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} tests/test-qapi-util -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="test-qapi-util"
==7468==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 74 ahci-test /x86_64/ahci/cdrom/pio/bcl
PASS 1 test-qapi-util /qapi/util/qapi_enum_parse
PASS 2 test-qapi-util /qapi/util/parse_qapi_name
---
PASS 22 test-qgraph /qgraph/test_test_in_path
PASS 23 test-qgraph /qgraph/test_double_edge
PASS 1 hd-geo-test /x86_64/hd-geo/ide/none
==7495==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 2 hd-geo-test /x86_64/hd-geo/ide/drive/cd_0
==7501==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 3 hd-geo-test /x86_64/hd-geo/ide/drive/mbr/blank
==7507==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 4 hd-geo-test /x86_64/hd-geo/ide/drive/mbr/lba
==7513==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 5 hd-geo-test /x86_64/hd-geo/ide/drive/mbr/chs
==7519==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 6 hd-geo-test /x86_64/hd-geo/ide/device/mbr/blank
==7525==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 7 hd-geo-test /x86_64/hd-geo/ide/device/mbr/lba
==7531==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 8 hd-geo-test /x86_64/hd-geo/ide/device/mbr/chs
==7537==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 9 hd-geo-test /x86_64/hd-geo/ide/device/user/chs
==7542==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 10 hd-geo-test /x86_64/hd-geo/ide/device/user/chst
==7548==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7552==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7556==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7560==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7564==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7568==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7572==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7576==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7579==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 11 hd-geo-test /x86_64/hd-geo/override/ide
==7586==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7590==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7594==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7598==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7602==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7606==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7610==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7614==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7617==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 12 hd-geo-test /x86_64/hd-geo/override/scsi
==7624==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7628==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7632==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7636==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7640==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7644==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7648==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7652==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7655==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 13 hd-geo-test /x86_64/hd-geo/override/scsi_2_controllers
==7662==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7666==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7670==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7674==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7677==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 14 hd-geo-test /x86_64/hd-geo/override/virtio_blk
==7684==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7688==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7691==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 15 hd-geo-test /x86_64/hd-geo/override/zero_chs
==7698==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7702==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7706==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7710==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7713==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 16 hd-geo-test /x86_64/hd-geo/override/scsi_hot_unplug
==7720==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7724==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7728==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7732==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
==7735==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 17 hd-geo-test /x86_64/hd-geo/override/virtio_hot_unplug
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 QTEST_QEMU_IMG=qemu-img tests/qtest/boot-order-test -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="boot-order-test"
PASS 1 boot-order-test /x86_64/boot-order/pc
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7804==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/pc/FACP'
Using expected file 'tests/data/acpi/pc/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7810==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/q35/FACP'
Using expected file 'tests/data/acpi/q35/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7816==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/pc/FACP.bridge'
Looking for expected file 'tests/data/acpi/pc/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7822==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/pc/FACP.ipmikcs'
Looking for expected file 'tests/data/acpi/pc/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7828==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/pc/FACP.cphp'
Looking for expected file 'tests/data/acpi/pc/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7835==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/pc/FACP.memhp'
Looking for expected file 'tests/data/acpi/pc/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7841==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/pc/FACP.numamem'
Looking for expected file 'tests/data/acpi/pc/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7847==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/pc/FACP.dimmpxm'
Looking for expected file 'tests/data/acpi/pc/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7856==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/pc/FACP.acpihmat'
Looking for expected file 'tests/data/acpi/pc/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7863==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/q35/FACP.bridge'
Looking for expected file 'tests/data/acpi/q35/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7869==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/q35/FACP.mmio64'
Looking for expected file 'tests/data/acpi/q35/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7875==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/q35/FACP.ipmibt'
Looking for expected file 'tests/data/acpi/q35/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7881==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/q35/FACP.cphp'
Looking for expected file 'tests/data/acpi/q35/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7888==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/q35/FACP.memhp'
Looking for expected file 'tests/data/acpi/q35/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7894==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/q35/FACP.numamem'
Looking for expected file 'tests/data/acpi/q35/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7900==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/q35/FACP.dimmpxm'
Looking for expected file 'tests/data/acpi/q35/FACP'
---
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: -accel kvm: failed to initialize kvm: No such file or directory
qemu-system-x86_64: falling back to tcg
==7909==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
Looking for expected file 'tests/data/acpi/q35/FACP.acpihmat'
Looking for expected file 'tests/data/acpi/q35/FACP'
---
PASS 1 i440fx-test /x86_64/i440fx/defaults
PASS 2 i440fx-test /x86_64/i440fx/pam
PASS 3 i440fx-test /x86_64/i440fx/firmware/bios
==8001==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 4 i440fx-test /x86_64/i440fx/firmware/pflash
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 QTEST_QEMU_IMG=qemu-img tests/qtest/fw_cfg-test -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="fw_cfg-test"
PASS 1 fw_cfg-test /x86_64/fw_cfg/signature
---
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 QTEST_QEMU_IMG=qemu-img tests/qtest/drive_del-test -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="drive_del-test"
PASS 1 drive_del-test /x86_64/drive_del/without-dev
PASS 2 drive_del-test /x86_64/drive_del/after_failed_device_add
==8094==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases!
PASS 3 drive_del-test /x86_64/blockdev/drive_del_device_del
MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))} QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 QTEST_QEMU_IMG=qemu-img tests/qtest/wdt_ib700-test -m=quick -k --tap < /dev/null | ./scripts/tap-driver.pl --test-name="wdt_ib700-test"
PASS 1 wdt_ib700-test /x86_64/wdt_ib700/pause
---
dbus-daemon[8264]: Could not get password database information for UID of current process: User "???" unknown or no memory to allocate password entry
**
ERROR:/tmp/qemu-test/src/tests/qtest/dbus-vmstate-test.c:114:get_connection: assertion failed (err == NULL): The connection is closed (g-io-error-quark, 18)
cleaning up pid 8264
ERROR - Bail out! ERROR:/tmp/qemu-test/src/tests/qtest/dbus-vmstate-test.c:114:get_connection: assertion failed (err == NULL): The connection is closed (g-io-error-quark, 18)
make: *** [/tmp/qemu-test/src/tests/Makefile.include:632: check-qtest-x86_64] Error 1
make: *** Waiting for unfinished jobs....
Traceback (most recent call last):
File "./tests/docker/docker.py", line 664, in <module>
---
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'run', '--label', 'com.qemu.instance.uuid=4a5f21d8569743a69c390df875103ed2', '-u', '1003', '--security-opt', 'seccomp=unconfined', '--rm', '-e', 'TARGET_LIST=x86_64-softmmu', '-e', 'EXTRA_CONFIGURE_OPTS=', '-e', 'V=', '-e', 'J=14', '-e', 'DEBUG=', '-e', 'SHOW_ENV=', '-e', 'CCACHE_DIR=/var/tmp/ccache', '-v', '/home/patchew2/.cache/qemu-docker-ccache:/var/tmp/ccache:z', '-v', '/var/tmp/patchew-tester-tmp-orkn8ysz/src/docker-src.2020-03-09-18.16.46.28361:/var/tmp/qemu:z,ro', 'qemu:fedora', '/var/tmp/qemu/run', 'test-debug']' returned non-zero exit status 2.
filter=--filter=label=com.qemu.instance.uuid=4a5f21d8569743a69c390df875103ed2
make[1]: *** [docker-run] Error 1
make[1]: Leaving directory `/var/tmp/patchew-tester-tmp-orkn8ysz/src'
make: *** [docker-run-test-debug@fedora] Error 2
real 28m13.303s
user 0m8.733s
The full log is available at
http://patchew.org/logs/20200309215818.2021-1-peter.maydell@linaro.org/testing.asan/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 1/5] Makefile: Allow for subdirectories in Sphinx manual dependencies
2020-03-09 21:58 ` [PATCH 1/5] Makefile: Allow for subdirectories in Sphinx manual dependencies Peter Maydell
@ 2020-03-10 14:29 ` Alex Bennée
2020-03-10 20:37 ` Niek Linnenbank
2020-03-11 6:36 ` Richard Henderson
2 siblings, 0 replies; 18+ messages in thread
From: Alex Bennée @ 2020-03-10 14:29 UTC (permalink / raw)
To: Peter Maydell; +Cc: Niek Linnenbank, qemu-arm, qemu-devel
Peter Maydell <peter.maydell@linaro.org> writes:
> Currently we put 'docs/foo/*.rst' in the Make list of dependencies
> for the Sphinx 'foo' manual, which means all the files must be
> in the top level of that manual's directory. We'd like to be
> able to have subdirectories inside some of the manuals, so add
> 'docs/foo/*/*.rst' to the dependencies too.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index 2e930688942..5dba949947a 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1081,7 +1081,7 @@ sphinxdocs: $(MANUAL_BUILDDIR)/devel/index.html \
> # a single doctree: https://github.com/sphinx-doc/sphinx/issues/2946
> build-manual = $(call quiet-command,CONFDIR="$(qemu_confdir)" $(SPHINX_BUILD) $(if $(V),,-q) -W -b $2 -D version=$(VERSION) -D release="$(FULL_VERSION)" -d .doctrees/$1-$2 $(SRC_PATH)/docs/$1 $(MANUAL_BUILDDIR)/$1 ,"SPHINX","$(MANUAL_BUILDDIR)/$1")
> # We assume all RST files in the manual's directory are used in it
> -manual-deps = $(wildcard $(SRC_PATH)/docs/$1/*.rst) \
> +manual-deps = $(wildcard $(SRC_PATH)/docs/$1/*.rst $(SRC_PATH)/docs/$1/*/*.rst) \
> $(SRC_PATH)/docs/defs.rst.inc \
> $(SRC_PATH)/docs/$1/conf.py $(SRC_PATH)/docs/conf.py
> # Macro to write out the rule and dependencies for building manpages
--
Alex Bennée
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 2/5] docs/system: Split target-arm.rst into sub-documents
2020-03-09 21:58 ` [PATCH 2/5] docs/system: Split target-arm.rst into sub-documents Peter Maydell
@ 2020-03-10 14:29 ` Alex Bennée
2020-03-10 20:53 ` Niek Linnenbank
1 sibling, 0 replies; 18+ messages in thread
From: Alex Bennée @ 2020-03-10 14:29 UTC (permalink / raw)
To: Peter Maydell; +Cc: Niek Linnenbank, qemu-arm, qemu-devel
Peter Maydell <peter.maydell@linaro.org> writes:
> Currently the documentation for Arm system emulator targets is in a
> single target-arm.rst. This describes only some of the boards and
> often in a fairly abbreviated fashion. Restructure it so that each
> board has its own documentation file in the docs/system/arm/
> subdirectory.
>
> This will hopefully encourage us to write board documentation that
> describes the board in detail, rather than a few brief paragraphs
> in a single long page. The table of contents should also help users
> to find the board they care about faster.
>
> Once the structure is in place we'll be able to move microvm.rst
> from the top-level docs/ directory.
>
> All the text from the old page is retained, except for the final
> paragraph ("A Linux 2.6 test image is available on the QEMU web site.
> More information is available in the QEMU mailing-list archive."),
> which is deleted. The git history shows this was originally added
> in reference to the integratorcp board (at that time the only
> Arm board that was supported), and has subsequently gradually been
> further and further separated from the integratorcp documentation
> by the insertion of other board documentation sections. It's
> extremely out of date and no longer accurate, since AFAICT there
> isn't an integratorcp kernel on the website any more; so better
> deleted than retained.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> A subsequent patch will add some text that at least gestures
> in the direction of some of the more obvious missing info,
> eg 64-bit boards.
> ---
> MAINTAINERS | 9 ++
> docs/system/arm/integratorcp.rst | 16 +++
> docs/system/arm/musicpal.rst | 19 +++
> docs/system/arm/nseries.rst | 33 +++++
> docs/system/arm/palm.rst | 23 ++++
> docs/system/arm/realview.rst | 34 +++++
> docs/system/arm/stellaris.rst | 26 ++++
> docs/system/arm/sx1.rst | 18 +++
> docs/system/arm/versatile.rst | 29 ++++
> docs/system/arm/xscale.rst | 29 ++++
> docs/system/target-arm.rst | 225 ++-----------------------------
> 11 files changed, 249 insertions(+), 212 deletions(-)
> create mode 100644 docs/system/arm/integratorcp.rst
> create mode 100644 docs/system/arm/musicpal.rst
> create mode 100644 docs/system/arm/nseries.rst
> create mode 100644 docs/system/arm/palm.rst
> create mode 100644 docs/system/arm/realview.rst
> create mode 100644 docs/system/arm/stellaris.rst
> create mode 100644 docs/system/arm/sx1.rst
> create mode 100644 docs/system/arm/versatile.rst
> create mode 100644 docs/system/arm/xscale.rst
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 36d0c6887a9..31a1b423df1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -155,6 +155,7 @@ F: include/hw/cpu/a*mpcore.h
> F: disas/arm.c
> F: disas/arm-a64.cc
> F: disas/libvixl/
> +F: docs/system/target-arm.rst
>
> ARM SMMU
> M: Eric Auger <eric.auger@redhat.com>
> @@ -615,6 +616,7 @@ F: hw/arm/integratorcp.c
> F: hw/misc/arm_integrator_debug.c
> F: include/hw/misc/arm_integrator_debug.h
> F: tests/acceptance/machine_arm_integratorcp.py
> +F: docs/system/arm/integratorcp.rst
>
> MCIMX6UL EVK / i.MX6ul
> M: Peter Maydell <peter.maydell@linaro.org>
> @@ -673,6 +675,7 @@ M: Peter Maydell <peter.maydell@linaro.org>
> L: qemu-arm@nongnu.org
> S: Odd Fixes
> F: hw/arm/musicpal.c
> +F: docs/system/arm/musicpal.rst
>
> nSeries
> M: Andrzej Zaborowski <balrogg@gmail.com>
> @@ -689,6 +692,7 @@ F: include/hw/display/blizzard.h
> F: include/hw/input/tsc2xxx.h
> F: include/hw/misc/cbus.h
> F: tests/acceptance/machine_arm_n8x0.py
> +F: docs/system/arm/nseries.rst
>
> Palm
> M: Andrzej Zaborowski <balrogg@gmail.com>
> @@ -698,6 +702,7 @@ S: Odd Fixes
> F: hw/arm/palm.c
> F: hw/input/tsc210x.c
> F: include/hw/input/tsc2xxx.h
> +F: docs/system/arm/palm.rst
>
> Raspberry Pi
> M: Peter Maydell <peter.maydell@linaro.org>
> @@ -719,6 +724,7 @@ F: hw/arm/realview*
> F: hw/cpu/realview_mpcore.c
> F: hw/intc/realview_gic.c
> F: include/hw/intc/realview_gic.h
> +F: docs/system/arm/realview.rst
>
> PXA2XX
> M: Andrzej Zaborowski <balrogg@gmail.com>
> @@ -738,6 +744,7 @@ F: hw/misc/max111x.c
> F: include/hw/arm/pxa.h
> F: include/hw/arm/sharpsl.h
> F: include/hw/display/tc6393xb.h
> +F: docs/system/arm/xscale.rst
>
> SABRELITE / i.MX6
> M: Peter Maydell <peter.maydell@linaro.org>
> @@ -773,6 +780,7 @@ L: qemu-arm@nongnu.org
> S: Maintained
> F: hw/*/stellaris*
> F: include/hw/input/gamepad.h
> +F: docs/system/arm/stellaris.rst
>
> Versatile Express
> M: Peter Maydell <peter.maydell@linaro.org>
> @@ -786,6 +794,7 @@ L: qemu-arm@nongnu.org
> S: Maintained
> F: hw/*/versatile*
> F: hw/misc/arm_sysctl.c
> +F: docs/system/arm/versatile.rst
>
> Virt
> M: Peter Maydell <peter.maydell@linaro.org>
> diff --git a/docs/system/arm/integratorcp.rst b/docs/system/arm/integratorcp.rst
> new file mode 100644
> index 00000000000..3232b43a08b
> --- /dev/null
> +++ b/docs/system/arm/integratorcp.rst
> @@ -0,0 +1,16 @@
> +Integrator/CP (``integratorcp``)
> +================================
> +
> +The ARM Integrator/CP board is emulated with the following devices:
> +
> +- ARM926E, ARM1026E, ARM946E, ARM1136 or Cortex-A8 CPU
> +
> +- Two PL011 UARTs
> +
> +- SMC 91c111 Ethernet adapter
> +
> +- PL110 LCD controller
> +
> +- PL050 KMI with PS/2 keyboard and mouse.
> +
> +- PL181 MultiMedia Card Interface with SD card.
> diff --git a/docs/system/arm/musicpal.rst b/docs/system/arm/musicpal.rst
> new file mode 100644
> index 00000000000..35c22212486
> --- /dev/null
> +++ b/docs/system/arm/musicpal.rst
> @@ -0,0 +1,19 @@
> +Freecom MusicPal (``musicpal``)
> +===============================
> +
> +The Freecom MusicPal internet radio emulation includes the following
> +elements:
> +
> +- Marvell MV88W8618 ARM core.
> +
> +- 32 MB RAM, 256 KB SRAM, 8 MB flash.
> +
> +- Up to 2 16550 UARTs
> +
> +- MV88W8xx8 Ethernet controller
> +
> +- MV88W8618 audio controller, WM8750 CODEC and mixer
> +
> +- 128x64 display with brightness control
> +
> +- 2 buttons, 2 navigation wheels with button function
> diff --git a/docs/system/arm/nseries.rst b/docs/system/arm/nseries.rst
> new file mode 100644
> index 00000000000..b000b6d13bb
> --- /dev/null
> +++ b/docs/system/arm/nseries.rst
> @@ -0,0 +1,33 @@
> +Nokia N800 and N810 tablets (``n800``, ``n810``)
> +================================================
> +
> +Nokia N800 and N810 internet tablets (known also as RX-34 and RX-44 /
> +48) emulation supports the following elements:
> +
> +- Texas Instruments OMAP2420 System-on-chip (ARM 1136 core)
> +
> +- RAM and non-volatile OneNAND Flash memories
> +
> +- Display connected to EPSON remote framebuffer chip and OMAP on-chip
> + display controller and a LS041y3 MIPI DBI-C controller
> +
> +- TI TSC2301 (in N800) and TI TSC2005 (in N810) touchscreen
> + controllers driven through SPI bus
> +
> +- National Semiconductor LM8323-controlled qwerty keyboard driven
> + through |I2C| bus
> +
> +- Secure Digital card connected to OMAP MMC/SD host
> +
> +- Three OMAP on-chip UARTs and on-chip STI debugging console
> +
> +- Mentor Graphics \"Inventra\" dual-role USB controller embedded in a
> + TI TUSB6010 chip - only USB host mode is supported
> +
> +- TI TMP105 temperature sensor driven through |I2C| bus
> +
> +- TI TWL92230C power management companion with an RTC on
> + |I2C| bus
> +
> +- Nokia RETU and TAHVO multi-purpose chips with an RTC, connected
> + through CBUS
> diff --git a/docs/system/arm/palm.rst b/docs/system/arm/palm.rst
> new file mode 100644
> index 00000000000..0eabf63e0e7
> --- /dev/null
> +++ b/docs/system/arm/palm.rst
> @@ -0,0 +1,23 @@
> +Palm Tungsten|E PDA (``cheetah``)
> +=================================
> +
> +The Palm Tungsten|E PDA (codename \"Cheetah\") emulation includes the
> +following elements:
> +
> +- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> +
> +- ROM and RAM memories (ROM firmware image can be loaded with
> + -option-rom)
> +
> +- On-chip LCD controller
> +
> +- On-chip Real Time Clock
> +
> +- TI TSC2102i touchscreen controller / analog-digital converter /
> + Audio CODEC, connected through MicroWire and |I2S| busses
> +
> +- GPIO-connected matrix keypad
> +
> +- Secure Digital card connected to OMAP MMC/SD host
> +
> +- Three on-chip UARTs
> diff --git a/docs/system/arm/realview.rst b/docs/system/arm/realview.rst
> new file mode 100644
> index 00000000000..8e08eb5da16
> --- /dev/null
> +++ b/docs/system/arm/realview.rst
> @@ -0,0 +1,34 @@
> +Arm Realview boards (``realview-eb``, ``realview-eb-mpcore``, ``realview-pb-a8``, ``realview-pbx-a9``)
> +======================================================================================================
> +
> +Several variants of the ARM RealView baseboard are emulated, including
> +the EB, PB-A8 and PBX-A9. Due to interactions with the bootloader, only
> +certain Linux kernel configurations work out of the box on these boards.
> +
> +Kernels for the PB-A8 board should have CONFIG_REALVIEW_HIGH_PHYS_OFFSET
> +enabled in the kernel, and expect 512M RAM. Kernels for The PBX-A9 board
> +should have CONFIG_SPARSEMEM enabled, CONFIG_REALVIEW_HIGH_PHYS_OFFSET
> +disabled and expect 1024M RAM.
> +
> +The following devices are emulated:
> +
> +- ARM926E, ARM1136, ARM11MPCore, Cortex-A8 or Cortex-A9 MPCore CPU
> +
> +- ARM AMBA Generic/Distributed Interrupt Controller
> +
> +- Four PL011 UARTs
> +
> +- SMC 91c111 or SMSC LAN9118 Ethernet adapter
> +
> +- PL110 LCD controller
> +
> +- PL050 KMI with PS/2 keyboard and mouse
> +
> +- PCI host bridge
> +
> +- PCI OHCI USB controller
> +
> +- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
> + devices
> +
> +- PL181 MultiMedia Card Interface with SD card.
> diff --git a/docs/system/arm/stellaris.rst b/docs/system/arm/stellaris.rst
> new file mode 100644
> index 00000000000..8af4ad79c79
> --- /dev/null
> +++ b/docs/system/arm/stellaris.rst
> @@ -0,0 +1,26 @@
> +Stellaris boards (``lm3s6965evb``, ``lm3s811evb``)
> +==================================================
> +
> +The Luminary Micro Stellaris LM3S811EVB emulation includes the following
> +devices:
> +
> +- Cortex-M3 CPU core.
> +
> +- 64k Flash and 8k SRAM.
> +
> +- Timers, UARTs, ADC and |I2C| interface.
> +
> +- OSRAM Pictiva 96x16 OLED with SSD0303 controller on
> + |I2C| bus.
> +
> +The Luminary Micro Stellaris LM3S6965EVB emulation includes the
> +following devices:
> +
> +- Cortex-M3 CPU core.
> +
> +- 256k Flash and 64k SRAM.
> +
> +- Timers, UARTs, ADC, |I2C| and SSI interfaces.
> +
> +- OSRAM Pictiva 128x64 OLED with SSD0323 controller connected via
> + SSI.
> diff --git a/docs/system/arm/sx1.rst b/docs/system/arm/sx1.rst
> new file mode 100644
> index 00000000000..321993bc098
> --- /dev/null
> +++ b/docs/system/arm/sx1.rst
> @@ -0,0 +1,18 @@
> +Siemens SX1 (``sx1``, ``sx1-v1``)
> +=================================
> +
> +The Siemens SX1 models v1 and v2 (default) basic emulation. The
> +emulation includes the following elements:
> +
> +- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> +
> +- ROM and RAM memories (ROM firmware image can be loaded with
> + -pflash) V1 1 Flash of 16MB and 1 Flash of 8MB V2 1 Flash of 32MB
> +
> +- On-chip LCD controller
> +
> +- On-chip Real Time Clock
> +
> +- Secure Digital card connected to OMAP MMC/SD host
> +
> +- Three on-chip UARTs
> diff --git a/docs/system/arm/versatile.rst b/docs/system/arm/versatile.rst
> new file mode 100644
> index 00000000000..48b6ca0a020
> --- /dev/null
> +++ b/docs/system/arm/versatile.rst
> @@ -0,0 +1,29 @@
> +Arm Versatile boards (``versatileab``, ``versatilepb``)
> +=======================================================
> +
> +The ARM Versatile baseboard is emulated with the following devices:
> +
> +- ARM926E, ARM1136 or Cortex-A8 CPU
> +
> +- PL190 Vectored Interrupt Controller
> +
> +- Four PL011 UARTs
> +
> +- SMC 91c111 Ethernet adapter
> +
> +- PL110 LCD controller
> +
> +- PL050 KMI with PS/2 keyboard and mouse.
> +
> +- PCI host bridge. Note the emulated PCI bridge only provides access
> + to PCI memory space. It does not provide access to PCI IO space. This
> + means some devices (eg. ne2k_pci NIC) are not usable, and others (eg.
> + rtl8139 NIC) are only usable when the guest drivers use the memory
> + mapped control registers.
> +
> +- PCI OHCI USB controller.
> +
> +- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
> + devices.
> +
> +- PL181 MultiMedia Card Interface with SD card.
> diff --git a/docs/system/arm/xscale.rst b/docs/system/arm/xscale.rst
> new file mode 100644
> index 00000000000..19da2eff352
> --- /dev/null
> +++ b/docs/system/arm/xscale.rst
> @@ -0,0 +1,29 @@
> +Sharp XScale-based PDA models (``akita``, ``borzoi``, ``spitz``, ``terrier``)
> +=============================================================================
> +
> +The XScale-based clamshell PDA models (\"Spitz\", \"Akita\", \"Borzoi\"
> +and \"Terrier\") emulation includes the following peripherals:
> +
> +- Intel PXA270 System-on-chip (ARM V5TE core)
> +
> +- NAND Flash memory
> +
> +- IBM/Hitachi DSCM microdrive in a PXA PCMCIA slot - not in \"Akita\"
> +
> +- On-chip OHCI USB controller
> +
> +- On-chip LCD controller
> +
> +- On-chip Real Time Clock
> +
> +- TI ADS7846 touchscreen controller on SSP bus
> +
> +- Maxim MAX1111 analog-digital converter on |I2C| bus
> +
> +- GPIO-connected keyboard controller and LEDs
> +
> +- Secure Digital card connected to PXA MMC/SD host
> +
> +- Three on-chip UARTs
> +
> +- WM8750 audio CODEC on |I2C| and |I2S| busses
> diff --git a/docs/system/target-arm.rst b/docs/system/target-arm.rst
> index d2a3b44ce88..c7df6fc1f97 100644
> --- a/docs/system/target-arm.rst
> +++ b/docs/system/target-arm.rst
> @@ -3,215 +3,16 @@
> ARM System emulator
> -------------------
>
> -Use the executable ``qemu-system-arm`` to simulate a ARM machine. The
> -ARM Integrator/CP board is emulated with the following devices:
> -
> -- ARM926E, ARM1026E, ARM946E, ARM1136 or Cortex-A8 CPU
> -
> -- Two PL011 UARTs
> -
> -- SMC 91c111 Ethernet adapter
> -
> -- PL110 LCD controller
> -
> -- PL050 KMI with PS/2 keyboard and mouse.
> -
> -- PL181 MultiMedia Card Interface with SD card.
> -
> -The ARM Versatile baseboard is emulated with the following devices:
> -
> -- ARM926E, ARM1136 or Cortex-A8 CPU
> -
> -- PL190 Vectored Interrupt Controller
> -
> -- Four PL011 UARTs
> -
> -- SMC 91c111 Ethernet adapter
> -
> -- PL110 LCD controller
> -
> -- PL050 KMI with PS/2 keyboard and mouse.
> -
> -- PCI host bridge. Note the emulated PCI bridge only provides access
> - to PCI memory space. It does not provide access to PCI IO space. This
> - means some devices (eg. ne2k_pci NIC) are not usable, and others (eg.
> - rtl8139 NIC) are only usable when the guest drivers use the memory
> - mapped control registers.
> -
> -- PCI OHCI USB controller.
> -
> -- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
> - devices.
> -
> -- PL181 MultiMedia Card Interface with SD card.
> -
> -Several variants of the ARM RealView baseboard are emulated, including
> -the EB, PB-A8 and PBX-A9. Due to interactions with the bootloader, only
> -certain Linux kernel configurations work out of the box on these boards.
> -
> -Kernels for the PB-A8 board should have CONFIG_REALVIEW_HIGH_PHYS_OFFSET
> -enabled in the kernel, and expect 512M RAM. Kernels for The PBX-A9 board
> -should have CONFIG_SPARSEMEM enabled, CONFIG_REALVIEW_HIGH_PHYS_OFFSET
> -disabled and expect 1024M RAM.
> -
> -The following devices are emulated:
> -
> -- ARM926E, ARM1136, ARM11MPCore, Cortex-A8 or Cortex-A9 MPCore CPU
> -
> -- ARM AMBA Generic/Distributed Interrupt Controller
> -
> -- Four PL011 UARTs
> -
> -- SMC 91c111 or SMSC LAN9118 Ethernet adapter
> -
> -- PL110 LCD controller
> -
> -- PL050 KMI with PS/2 keyboard and mouse
> -
> -- PCI host bridge
> -
> -- PCI OHCI USB controller
> -
> -- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
> - devices
> -
> -- PL181 MultiMedia Card Interface with SD card.
> -
> -The XScale-based clamshell PDA models (\"Spitz\", \"Akita\", \"Borzoi\"
> -and \"Terrier\") emulation includes the following peripherals:
> -
> -- Intel PXA270 System-on-chip (ARM V5TE core)
> -
> -- NAND Flash memory
> -
> -- IBM/Hitachi DSCM microdrive in a PXA PCMCIA slot - not in \"Akita\"
> -
> -- On-chip OHCI USB controller
> -
> -- On-chip LCD controller
> -
> -- On-chip Real Time Clock
> -
> -- TI ADS7846 touchscreen controller on SSP bus
> -
> -- Maxim MAX1111 analog-digital converter on |I2C| bus
> -
> -- GPIO-connected keyboard controller and LEDs
> -
> -- Secure Digital card connected to PXA MMC/SD host
> -
> -- Three on-chip UARTs
> -
> -- WM8750 audio CODEC on |I2C| and |I2S| busses
> -
> -The Palm Tungsten|E PDA (codename \"Cheetah\") emulation includes the
> -following elements:
> -
> -- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> -
> -- ROM and RAM memories (ROM firmware image can be loaded with
> - -option-rom)
> -
> -- On-chip LCD controller
> -
> -- On-chip Real Time Clock
> -
> -- TI TSC2102i touchscreen controller / analog-digital converter /
> - Audio CODEC, connected through MicroWire and |I2S| busses
> -
> -- GPIO-connected matrix keypad
> -
> -- Secure Digital card connected to OMAP MMC/SD host
> -
> -- Three on-chip UARTs
> -
> -Nokia N800 and N810 internet tablets (known also as RX-34 and RX-44 /
> -48) emulation supports the following elements:
> -
> -- Texas Instruments OMAP2420 System-on-chip (ARM 1136 core)
> -
> -- RAM and non-volatile OneNAND Flash memories
> -
> -- Display connected to EPSON remote framebuffer chip and OMAP on-chip
> - display controller and a LS041y3 MIPI DBI-C controller
> -
> -- TI TSC2301 (in N800) and TI TSC2005 (in N810) touchscreen
> - controllers driven through SPI bus
> -
> -- National Semiconductor LM8323-controlled qwerty keyboard driven
> - through |I2C| bus
> -
> -- Secure Digital card connected to OMAP MMC/SD host
> -
> -- Three OMAP on-chip UARTs and on-chip STI debugging console
> -
> -- Mentor Graphics \"Inventra\" dual-role USB controller embedded in a
> - TI TUSB6010 chip - only USB host mode is supported
> -
> -- TI TMP105 temperature sensor driven through |I2C| bus
> -
> -- TI TWL92230C power management companion with an RTC on
> - |I2C| bus
> -
> -- Nokia RETU and TAHVO multi-purpose chips with an RTC, connected
> - through CBUS
> -
> -The Luminary Micro Stellaris LM3S811EVB emulation includes the following
> -devices:
> -
> -- Cortex-M3 CPU core.
> -
> -- 64k Flash and 8k SRAM.
> -
> -- Timers, UARTs, ADC and |I2C| interface.
> -
> -- OSRAM Pictiva 96x16 OLED with SSD0303 controller on
> - |I2C| bus.
> -
> -The Luminary Micro Stellaris LM3S6965EVB emulation includes the
> -following devices:
> -
> -- Cortex-M3 CPU core.
> -
> -- 256k Flash and 64k SRAM.
> -
> -- Timers, UARTs, ADC, |I2C| and SSI interfaces.
> -
> -- OSRAM Pictiva 128x64 OLED with SSD0323 controller connected via
> - SSI.
> -
> -The Freecom MusicPal internet radio emulation includes the following
> -elements:
> -
> -- Marvell MV88W8618 ARM core.
> -
> -- 32 MB RAM, 256 KB SRAM, 8 MB flash.
> -
> -- Up to 2 16550 UARTs
> -
> -- MV88W8xx8 Ethernet controller
> -
> -- MV88W8618 audio controller, WM8750 CODEC and mixer
> -
> -- 128x64 display with brightness control
> -
> -- 2 buttons, 2 navigation wheels with button function
> -
> -The Siemens SX1 models v1 and v2 (default) basic emulation. The
> -emulation includes the following elements:
> -
> -- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> -
> -- ROM and RAM memories (ROM firmware image can be loaded with
> - -pflash) V1 1 Flash of 16MB and 1 Flash of 8MB V2 1 Flash of 32MB
> -
> -- On-chip LCD controller
> -
> -- On-chip Real Time Clock
> -
> -- Secure Digital card connected to OMAP MMC/SD host
> -
> -- Three on-chip UARTs
> -
> -A Linux 2.6 test image is available on the QEMU web site. More
> -information is available in the QEMU mailing-list archive.
> +Use the executable ``qemu-system-arm`` to simulate a ARM machine.
> +
> +.. toctree::
> +
> + arm/integratorcp
> + arm/versatile
> + arm/realview
> + arm/xscale
> + arm/palm
> + arm/nseries
> + arm/stellaris
> + arm/musicpal
> + arm/sx1
--
Alex Bennée
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 3/5] docs/system/target-arm.rst: Add some introductory text
2020-03-09 21:58 ` [PATCH 3/5] docs/system/target-arm.rst: Add some introductory text Peter Maydell
@ 2020-03-10 14:54 ` Alex Bennée
2020-03-10 20:58 ` Niek Linnenbank
1 sibling, 0 replies; 18+ messages in thread
From: Alex Bennée @ 2020-03-10 14:54 UTC (permalink / raw)
To: Peter Maydell; +Cc: Niek Linnenbank, qemu-arm, qemu-devel
Peter Maydell <peter.maydell@linaro.org> writes:
> Now we've moved the various bits of per-board documentation into
> their own files, the top level document is a little bare. Add
> some introductory information, including a note that many
> of the board models we support are currently undocumented.
>
> (Most sections of this new text were originally written by me
> for the wiki page https://wiki.qemu.org/Documentation/Platforms/ARM)
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> ---
> docs/system/target-arm.rst | 66 ++++++++++++++++++++++++++++++++++++--
> 1 file changed, 64 insertions(+), 2 deletions(-)
>
> diff --git a/docs/system/target-arm.rst b/docs/system/target-arm.rst
> index c7df6fc1f97..86ea6f2f568 100644
> --- a/docs/system/target-arm.rst
> +++ b/docs/system/target-arm.rst
> @@ -1,9 +1,71 @@
> .. _ARM-System-emulator:
>
> -ARM System emulator
> +Arm System emulator
> -------------------
>
> -Use the executable ``qemu-system-arm`` to simulate a ARM machine.
> +QEMU can emulate both 32-bit and 64-bit Arm CPUs. Use the
> +``qemu-system-aarch64`` executable to simulate a 64-bit Arm machine.
> +You can use either ``qemu-system-arm`` or ``qemu-system-aarch64``
> +to simulate a 32-bit Arm machine: in general, command lines that
> +work for ``qemu-system-arm`` will behave the same when used with
> +``qemu-system-aarch64``.
> +
> +QEMU has generally good support for Arm guests. It has support for
> +nearly fifty different machines. The reason we support so many is that
> +Arm hardware is much more widely varying than x86 hardware. Arm CPUs
> +are generally built into "system-on-chip" (SoC) designs created by
> +many different companies with different devices, and these SoCs are
> +then built into machines which can vary still further even if they use
> +the same SoC. Even with fifty boards QEMU does not cover more than a
> +small fraction of the Arm hardware ecosystem.
> +
> +The situation for 64-bit Arm is fairly similar, except that we don't
> +implement so many different machines.
> +
> +As well as the more common "A-profile" CPUs (which have MMUs and will
> +run Linux) QEMU also supports "M-profile" CPUs such as the Cortex-M0,
> +Cortex-M4 and Cortex-M33 (which are microcontrollers used in very
> +embedded boards). For most boards the CPU type is fixed (matching what
> +the hardware has), so typically you don't need to specify the CPU type
> +by hand, except for special cases like the ``virt`` board.
> +
> +Choosing a board model
> +======================
> +
> +For QEMU's Arm system emulation, you must specify which board
> +model you want to use with the ``-M`` or ``--machine`` option;
> +there is no default.
> +
> +Because Arm systems differ so much and in fundamental ways, typically
> +operating system or firmware images intended to run on one machine
> +will not run at all on any other. This is often surprising for new
> +users who are used to the x86 world where every system looks like a
> +standard PC. (Once the kernel has booted, most userspace software
> +cares much less about the detail of the hardware.)
> +
> +If you already have a system image or a kernel that works on hardware
> +and you want to boot with QEMU, check whether QEMU lists that machine
> +in its ``-machine help`` output. If it is listed, then you can probably
> +use that board model. If it is not listed, then unfortunately your image
> +will almost certainly not boot on QEMU. (You might be able to
> +extract the filesystem and use that with a different kernel which
> +boots on a system that QEMU does emulate.)
> +
> +If you don't care about reproducing the idiosyncrasies of a particular
> +bit of hardware, such as small amount of RAM, no PCI or other hard
> +disk, etc., and just want to run Linux, the best option is to use the
> +``virt`` board. This is a platform which doesn't correspond to any
> +real hardware and is designed for use in virtual machines. You'll
> +need to compile Linux with a suitable configuration for running on
> +the ``virt`` board. ``virt`` supports PCI, virtio, recent CPUs and
> +large amounts of RAM. It also supports 64-bit CPUs.
> +
> +Board-specific documentation
> +============================
> +
> +Unfortunately many of the Arm boards QEMU supports are currently
> +undocumented; you can get a complete list by running
> +``qemu-system-aarch64 --machine help``.
>
> .. toctree::
--
Alex Bennée
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 4/5] docs: Move arm-cpu-features.rst into the system manual
2020-03-09 21:58 ` [PATCH 4/5] docs: Move arm-cpu-features.rst into the system manual Peter Maydell
@ 2020-03-10 14:54 ` Alex Bennée
2020-03-10 21:00 ` Niek Linnenbank
1 sibling, 0 replies; 18+ messages in thread
From: Alex Bennée @ 2020-03-10 14:54 UTC (permalink / raw)
To: Peter Maydell; +Cc: Niek Linnenbank, qemu-arm, qemu-devel
Peter Maydell <peter.maydell@linaro.org> writes:
> Now we have somewhere to put arm-specific rst documentation,
> we can move arm-cpu-features.rst from the docs/ top level
> directory into docs/system/arm/.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> .../{arm-cpu-features.rst => system/arm/cpu-features.rst} | 8 +-------
> docs/system/target-arm.rst | 6 ++++++
> 2 files changed, 7 insertions(+), 7 deletions(-)
> rename docs/{arm-cpu-features.rst => system/arm/cpu-features.rst} (99%)
>
> diff --git a/docs/arm-cpu-features.rst b/docs/system/arm/cpu-features.rst
> similarity index 99%
> rename from docs/arm-cpu-features.rst
> rename to docs/system/arm/cpu-features.rst
> index fc1623aeca5..7495b7b672b 100644
> --- a/docs/arm-cpu-features.rst
> +++ b/docs/system/arm/cpu-features.rst
> @@ -1,11 +1,5 @@
> +Arm CPU Features
> ================
> -ARM CPU Features
> -================
> -
> -Examples of probing and using ARM CPU features
> -
> -Introduction
> -============
>
> CPU features are optional features that a CPU of supporting type may
> choose to implement or not. In QEMU, optional CPU features have
> diff --git a/docs/system/target-arm.rst b/docs/system/target-arm.rst
> index 86ea6f2f568..1425bd5303a 100644
> --- a/docs/system/target-arm.rst
> +++ b/docs/system/target-arm.rst
> @@ -78,3 +78,9 @@ undocumented; you can get a complete list by running
> arm/stellaris
> arm/musicpal
> arm/sx1
> +
> +Arm CPU features
> +================
> +
> +.. toctree::
> + arm/cpu-features
--
Alex Bennée
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 5/5] docs: Be consistent about capitalization of 'Arm'
2020-03-09 21:58 ` [PATCH 5/5] docs: Be consistent about capitalization of 'Arm' Peter Maydell
@ 2020-03-10 14:55 ` Alex Bennée
2020-03-10 21:01 ` Niek Linnenbank
1 sibling, 0 replies; 18+ messages in thread
From: Alex Bennée @ 2020-03-10 14:55 UTC (permalink / raw)
To: Peter Maydell; +Cc: Niek Linnenbank, qemu-arm, qemu-devel
Peter Maydell <peter.maydell@linaro.org> writes:
> The company 'Arm' went through a rebranding some years back
> involving a recapitalization from 'ARM' to 'Arm'. As a result
> our documentation is a bit inconsistent between the two forms.
> It's not worth trying to update everywhere in QEMU, but it's
> easy enough to make docs/ consistent.
>
> Note that "ARMv8" and similar architecture names, and
> older CPU names like "ARM926" still retain all-caps.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> I don't feel very strongly about this change, but it
> looked a bit odd where earlier rearrangements in this
> series meant that some documents had a mix of both styles,
> so I thought I might as well fix all of docs/.
> ---
> docs/can.txt | 2 +-
> docs/devel/atomics.txt | 2 +-
> docs/devel/multi-thread-tcg.txt | 8 ++++----
> docs/replay.txt | 2 +-
> docs/specs/fw_cfg.txt | 2 +-
> docs/devel/kconfig.rst | 2 +-
> docs/devel/loads-stores.rst | 2 +-
> docs/devel/tcg.rst | 2 +-
> docs/specs/tpm.rst | 6 +++---
> docs/system/arm/cpu-features.rst | 4 ++--
> docs/system/arm/integratorcp.rst | 2 +-
> docs/system/arm/musicpal.rst | 2 +-
> docs/system/arm/nseries.rst | 2 +-
> docs/system/arm/palm.rst | 2 +-
> docs/system/arm/realview.rst | 4 ++--
> docs/system/arm/sx1.rst | 2 +-
> docs/system/arm/versatile.rst | 2 +-
> docs/system/arm/xscale.rst | 2 +-
> docs/user/main.rst | 8 ++++----
> 19 files changed, 29 insertions(+), 29 deletions(-)
>
> diff --git a/docs/can.txt b/docs/can.txt
> index 9fa6ed51c82..11ed8f2d68b 100644
> --- a/docs/can.txt
> +++ b/docs/can.txt
> @@ -13,7 +13,7 @@ controller is implemented.
>
> The PCI addon card hardware has been selected as the first CAN
> interface to implement because such device can be easily connected
> -to systems with different CPU architectures (x86, PowerPC, ARM, etc.).
> +to systems with different CPU architectures (x86, PowerPC, Arm, etc.).
>
> The project has been initially started in frame of RTEMS GSoC 2013
> slot by Jin Yang under our mentoring The initial idea was to provide generic
> diff --git a/docs/devel/atomics.txt b/docs/devel/atomics.txt
> index a4db3a4aaad..67bdf826280 100644
> --- a/docs/devel/atomics.txt
> +++ b/docs/devel/atomics.txt
> @@ -87,7 +87,7 @@ Sequentially consistent loads and stores can be done using:
> atomic_xchg(ptr, val) for stores
>
> However, they are quite expensive on some platforms, notably POWER and
> -ARM. Therefore, qemu/atomic.h provides two primitives with slightly
> +Arm. Therefore, qemu/atomic.h provides two primitives with slightly
> weaker constraints:
>
> typeof(*ptr) atomic_mb_read(ptr)
> diff --git a/docs/devel/multi-thread-tcg.txt b/docs/devel/multi-thread-tcg.txt
> index 782bebc28b4..3c85ac0eab9 100644
> --- a/docs/devel/multi-thread-tcg.txt
> +++ b/docs/devel/multi-thread-tcg.txt
> @@ -227,7 +227,7 @@ minimise contention.
> (Current solution)
>
> MMIO access automatically serialises hardware emulation by way of the
> -BQL. Currently ARM targets serialise all ARM_CP_IO register accesses
> +BQL. Currently Arm targets serialise all ARM_CP_IO register accesses
> and also defer the reset/startup of vCPUs to the vCPU context by way
> of async_run_on_cpu().
>
> @@ -268,7 +268,7 @@ ordered backends this could become a NOP.
> Aside from explicit standalone memory barrier instructions there are
> also implicit memory ordering semantics which comes with each guest
> memory access instruction. For example all x86 load/stores come with
> -fairly strong guarantees of sequential consistency where as ARM has
> +fairly strong guarantees of sequential consistency whereas Arm has
> special variants of load/store instructions that imply acquire/release
> semantics.
>
> @@ -317,7 +317,7 @@ x86 cmpxchg instruction.
>
> The second type offer a pair of load/store instructions which offer a
> guarantee that a region of memory has not been touched between the
> -load and store instructions. An example of this is ARM's ldrex/strex
> +load and store instructions. An example of this is Arm's ldrex/strex
> pair where the strex instruction will return a flag indicating a
> successful store only if no other CPU has accessed the memory region
> since the ldrex.
> @@ -339,7 +339,7 @@ CURRENT OPEN QUESTIONS:
>
> The TCG provides a number of atomic helpers (tcg_gen_atomic_*) which
> can be used directly or combined to emulate other instructions like
> -ARM's ldrex/strex instructions. While they are susceptible to the ABA
> +Arm's ldrex/strex instructions. While they are susceptible to the ABA
> problem so far common guests have not implemented patterns where
> this may be a problem - typically presenting a locking ABI which
> assumes cmpxchg like semantics.
> diff --git a/docs/replay.txt b/docs/replay.txt
> index f4619a62a3d..70c27edb362 100644
> --- a/docs/replay.txt
> +++ b/docs/replay.txt
> @@ -19,7 +19,7 @@ Deterministic replay has the following features:
> the memory, state of the hardware devices, clocks, and screen of the VM.
> * Writes execution log into the file for later replaying for multiple times
> on different machines.
> - * Supports i386, x86_64, and ARM hardware platforms.
> + * Supports i386, x86_64, and Arm hardware platforms.
> * Performs deterministic replay of all operations with keyboard and mouse
> input devices.
>
> diff --git a/docs/specs/fw_cfg.txt b/docs/specs/fw_cfg.txt
> index 08c00bdf44a..8f1ebc66fa4 100644
> --- a/docs/specs/fw_cfg.txt
> +++ b/docs/specs/fw_cfg.txt
> @@ -82,7 +82,7 @@ Selector Register IOport: 0x510
> Data Register IOport: 0x511
> DMA Address IOport: 0x514
>
> -=== ARM Register Locations ===
> +=== Arm Register Locations ===
>
> Selector Register address: Base + 8 (2 bytes)
> Data Register address: Base + 0 (8 bytes)
> diff --git a/docs/devel/kconfig.rst b/docs/devel/kconfig.rst
> index b7bca447046..e5df72b3422 100644
> --- a/docs/devel/kconfig.rst
> +++ b/docs/devel/kconfig.rst
> @@ -8,7 +8,7 @@ time different targets can share large amounts of code. For example,
> a POWER and an x86 board can run the same code to emulate a PCI network
> card, even though the boards use different PCI host bridges, and they
> can run the same code to emulate a SCSI disk while using different
> -SCSI adapters. ARM, s390 and x86 boards can all present a virtio-blk
> +SCSI adapters. Arm, s390 and x86 boards can all present a virtio-blk
> disk to their guests, but with three different virtio guest interfaces.
>
> Each QEMU target enables a subset of the boards, devices and buses that
> diff --git a/docs/devel/loads-stores.rst b/docs/devel/loads-stores.rst
> index 03aa9e7ff80..0d99eb24c1b 100644
> --- a/docs/devel/loads-stores.rst
> +++ b/docs/devel/loads-stores.rst
> @@ -302,7 +302,7 @@ way QEMU defines the view of memory that a device or CPU has.
> or bus fabric.)
>
> Each CPU has an AddressSpace. Some kinds of CPU have more than
> -one AddressSpace (for instance ARM guest CPUs have an AddressSpace
> +one AddressSpace (for instance Arm guest CPUs have an AddressSpace
> for the Secure world and one for NonSecure if they implement TrustZone).
> Devices which can do DMA-type operations should generally have an
> AddressSpace. There is also a "system address space" which typically
> diff --git a/docs/devel/tcg.rst b/docs/devel/tcg.rst
> index 4956a30a4e6..4ebde44b9d7 100644
> --- a/docs/devel/tcg.rst
> +++ b/docs/devel/tcg.rst
> @@ -83,7 +83,7 @@ memory until the end of the translation block. This is done for internal
> emulation state that is rarely accessed directly by the program and/or changes
> very often throughout the execution of a translation block---this includes
> condition codes on x86, delay slots on SPARC, conditional execution on
> -ARM, and so on. This state is stored for each target instruction, and
> +Arm, and so on. This state is stored for each target instruction, and
> looked up on exceptions.
>
> MMU emulation
> diff --git a/docs/specs/tpm.rst b/docs/specs/tpm.rst
> index da9eb39ca97..5e61238bc5f 100644
> --- a/docs/specs/tpm.rst
> +++ b/docs/specs/tpm.rst
> @@ -25,7 +25,7 @@ QEMU files related to TPM TIS interface:
>
> Both an ISA device and a sysbus device are available. The former is
> used with pc/q35 machine while the latter can be instantiated in the
> -ARM virt machine.
> +Arm virt machine.
>
> CRB interface
> -------------
> @@ -331,7 +331,7 @@ In case a pSeries machine is emulated, use the following command line:
> -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0 \
> -drive file=test.img,format=raw,if=none,id=drive-virtio-disk0
>
> -In case an ARM virt machine is emulated, use the following command line:
> +In case an Arm virt machine is emulated, use the following command line:
>
> .. code-block:: console
>
> @@ -346,7 +346,7 @@ In case an ARM virt machine is emulated, use the following command line:
> -drive if=pflash,format=raw,file=flash0.img,readonly \
> -drive if=pflash,format=raw,file=flash1.img
>
> - On ARM, ACPI boot with TPM is not yet supported.
> + On Arm, ACPI boot with TPM is not yet supported.
>
> In case SeaBIOS is used as firmware, it should show the TPM menu item
> after entering the menu with 'ESC'.
> diff --git a/docs/system/arm/cpu-features.rst b/docs/system/arm/cpu-features.rst
> index 7495b7b672b..2d5c06cd016 100644
> --- a/docs/system/arm/cpu-features.rst
> +++ b/docs/system/arm/cpu-features.rst
> @@ -5,9 +5,9 @@ CPU features are optional features that a CPU of supporting type may
> choose to implement or not. In QEMU, optional CPU features have
> corresponding boolean CPU proprieties that, when enabled, indicate
> that the feature is implemented, and, conversely, when disabled,
> -indicate that it is not implemented. An example of an ARM CPU feature
> +indicate that it is not implemented. An example of an Arm CPU feature
> is the Performance Monitoring Unit (PMU). CPU types such as the
> -Cortex-A15 and the Cortex-A57, which respectively implement ARM
> +Cortex-A15 and the Cortex-A57, which respectively implement Arm
> architecture reference manuals ARMv7-A and ARMv8-A, may both optionally
> implement PMUs. For example, if a user wants to use a Cortex-A15 without
> a PMU, then the `-cpu` parameter should contain `pmu=off` on the QEMU
> diff --git a/docs/system/arm/integratorcp.rst b/docs/system/arm/integratorcp.rst
> index 3232b43a08b..e6f050f602b 100644
> --- a/docs/system/arm/integratorcp.rst
> +++ b/docs/system/arm/integratorcp.rst
> @@ -1,7 +1,7 @@
> Integrator/CP (``integratorcp``)
> ================================
>
> -The ARM Integrator/CP board is emulated with the following devices:
> +The Arm Integrator/CP board is emulated with the following devices:
>
> - ARM926E, ARM1026E, ARM946E, ARM1136 or Cortex-A8 CPU
>
> diff --git a/docs/system/arm/musicpal.rst b/docs/system/arm/musicpal.rst
> index 35c22212486..9de380edf81 100644
> --- a/docs/system/arm/musicpal.rst
> +++ b/docs/system/arm/musicpal.rst
> @@ -4,7 +4,7 @@ Freecom MusicPal (``musicpal``)
> The Freecom MusicPal internet radio emulation includes the following
> elements:
>
> -- Marvell MV88W8618 ARM core.
> +- Marvell MV88W8618 Arm core.
>
> - 32 MB RAM, 256 KB SRAM, 8 MB flash.
>
> diff --git a/docs/system/arm/nseries.rst b/docs/system/arm/nseries.rst
> index b000b6d13bb..cd9edf5d88b 100644
> --- a/docs/system/arm/nseries.rst
> +++ b/docs/system/arm/nseries.rst
> @@ -4,7 +4,7 @@ Nokia N800 and N810 tablets (``n800``, ``n810``)
> Nokia N800 and N810 internet tablets (known also as RX-34 and RX-44 /
> 48) emulation supports the following elements:
>
> -- Texas Instruments OMAP2420 System-on-chip (ARM 1136 core)
> +- Texas Instruments OMAP2420 System-on-chip (ARM1136 core)
>
> - RAM and non-volatile OneNAND Flash memories
>
> diff --git a/docs/system/arm/palm.rst b/docs/system/arm/palm.rst
> index 0eabf63e0e7..47ff9b36d46 100644
> --- a/docs/system/arm/palm.rst
> +++ b/docs/system/arm/palm.rst
> @@ -4,7 +4,7 @@ Palm Tungsten|E PDA (``cheetah``)
> The Palm Tungsten|E PDA (codename \"Cheetah\") emulation includes the
> following elements:
>
> -- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> +- Texas Instruments OMAP310 System-on-chip (ARM925T core)
>
> - ROM and RAM memories (ROM firmware image can be loaded with
> -option-rom)
> diff --git a/docs/system/arm/realview.rst b/docs/system/arm/realview.rst
> index 8e08eb5da16..65f5be346b1 100644
> --- a/docs/system/arm/realview.rst
> +++ b/docs/system/arm/realview.rst
> @@ -1,7 +1,7 @@
> Arm Realview boards (``realview-eb``, ``realview-eb-mpcore``, ``realview-pb-a8``, ``realview-pbx-a9``)
> ======================================================================================================
>
> -Several variants of the ARM RealView baseboard are emulated, including
> +Several variants of the Arm RealView baseboard are emulated, including
> the EB, PB-A8 and PBX-A9. Due to interactions with the bootloader, only
> certain Linux kernel configurations work out of the box on these boards.
>
> @@ -14,7 +14,7 @@ The following devices are emulated:
>
> - ARM926E, ARM1136, ARM11MPCore, Cortex-A8 or Cortex-A9 MPCore CPU
>
> -- ARM AMBA Generic/Distributed Interrupt Controller
> +- Arm AMBA Generic/Distributed Interrupt Controller
>
> - Four PL011 UARTs
>
> diff --git a/docs/system/arm/sx1.rst b/docs/system/arm/sx1.rst
> index 321993bc098..8bce30d4b25 100644
> --- a/docs/system/arm/sx1.rst
> +++ b/docs/system/arm/sx1.rst
> @@ -4,7 +4,7 @@ Siemens SX1 (``sx1``, ``sx1-v1``)
> The Siemens SX1 models v1 and v2 (default) basic emulation. The
> emulation includes the following elements:
>
> -- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> +- Texas Instruments OMAP310 System-on-chip (ARM925T core)
>
> - ROM and RAM memories (ROM firmware image can be loaded with
> -pflash) V1 1 Flash of 16MB and 1 Flash of 8MB V2 1 Flash of 32MB
> diff --git a/docs/system/arm/versatile.rst b/docs/system/arm/versatile.rst
> index 48b6ca0a020..51221c30a48 100644
> --- a/docs/system/arm/versatile.rst
> +++ b/docs/system/arm/versatile.rst
> @@ -1,7 +1,7 @@
> Arm Versatile boards (``versatileab``, ``versatilepb``)
> =======================================================
>
> -The ARM Versatile baseboard is emulated with the following devices:
> +The Arm Versatile baseboard is emulated with the following devices:
>
> - ARM926E, ARM1136 or Cortex-A8 CPU
>
> diff --git a/docs/system/arm/xscale.rst b/docs/system/arm/xscale.rst
> index 19da2eff352..89ec93e904e 100644
> --- a/docs/system/arm/xscale.rst
> +++ b/docs/system/arm/xscale.rst
> @@ -4,7 +4,7 @@ Sharp XScale-based PDA models (``akita``, ``borzoi``, ``spitz``, ``terrier``)
> The XScale-based clamshell PDA models (\"Spitz\", \"Akita\", \"Borzoi\"
> and \"Terrier\") emulation includes the following peripherals:
>
> -- Intel PXA270 System-on-chip (ARM V5TE core)
> +- Intel PXA270 System-on-chip (ARMv5TE core)
>
> - NAND Flash memory
>
> diff --git a/docs/user/main.rst b/docs/user/main.rst
> index ca69f7727d5..bd99b0fdbe9 100644
> --- a/docs/user/main.rst
> +++ b/docs/user/main.rst
> @@ -35,7 +35,7 @@ QEMU user space emulation has the following notable features:
> On Linux, QEMU can emulate the ``clone`` syscall and create a real
> host thread (with a separate virtual CPU) for each emulated thread.
> Note that not all targets currently emulate atomic operations
> - correctly. x86 and ARM use a global lock in order to preserve their
> + correctly. x86 and Arm use a global lock in order to preserve their
> semantics.
>
> QEMU was conceived so that ultimately it can emulate itself. Although it
> @@ -173,11 +173,11 @@ Other binaries
> user mode (Alpha)
> ``qemu-alpha`` TODO.
>
> -user mode (ARM)
> +user mode (Arm)
> ``qemu-armeb`` TODO.
>
> -user mode (ARM)
> -``qemu-arm`` is also capable of running ARM \"Angel\" semihosted ELF
> +user mode (Arm)
> +``qemu-arm`` is also capable of running Arm \"Angel\" semihosted ELF
> binaries (as implemented by the arm-elf and arm-eabi Newlib/GDB
> configurations), and arm-uclinux bFLT format binaries.
--
Alex Bennée
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 1/5] Makefile: Allow for subdirectories in Sphinx manual dependencies
2020-03-09 21:58 ` [PATCH 1/5] Makefile: Allow for subdirectories in Sphinx manual dependencies Peter Maydell
2020-03-10 14:29 ` Alex Bennée
@ 2020-03-10 20:37 ` Niek Linnenbank
2020-03-11 6:36 ` Richard Henderson
2 siblings, 0 replies; 18+ messages in thread
From: Niek Linnenbank @ 2020-03-10 20:37 UTC (permalink / raw)
To: Peter Maydell; +Cc: qemu-arm, QEMU Developers
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
Reviewed-by: Niek Linnenbank <nieklinnenbank@gmail.com>
On Mon, Mar 9, 2020 at 10:58 PM Peter Maydell <peter.maydell@linaro.org>
wrote:
> Currently we put 'docs/foo/*.rst' in the Make list of dependencies
> for the Sphinx 'foo' manual, which means all the files must be
> in the top level of that manual's directory. We'd like to be
> able to have subdirectories inside some of the manuals, so add
> 'docs/foo/*/*.rst' to the dependencies too.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index 2e930688942..5dba949947a 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1081,7 +1081,7 @@ sphinxdocs: $(MANUAL_BUILDDIR)/devel/index.html \
> # a single doctree: https://github.com/sphinx-doc/sphinx/issues/2946
> build-manual = $(call quiet-command,CONFDIR="$(qemu_confdir)"
> $(SPHINX_BUILD) $(if $(V),,-q) -W -b $2 -D version=$(VERSION) -D
> release="$(FULL_VERSION)" -d .doctrees/$1-$2 $(SRC_PATH)/docs/$1
> $(MANUAL_BUILDDIR)/$1 ,"SPHINX","$(MANUAL_BUILDDIR)/$1")
> # We assume all RST files in the manual's directory are used in it
> -manual-deps = $(wildcard $(SRC_PATH)/docs/$1/*.rst) \
> +manual-deps = $(wildcard $(SRC_PATH)/docs/$1/*.rst
> $(SRC_PATH)/docs/$1/*/*.rst) \
> $(SRC_PATH)/docs/defs.rst.inc \
> $(SRC_PATH)/docs/$1/conf.py $(SRC_PATH)/docs/conf.py
> # Macro to write out the rule and dependencies for building manpages
> --
> 2.20.1
>
>
--
Niek Linnenbank
[-- Attachment #2: Type: text/html, Size: 2322 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 2/5] docs/system: Split target-arm.rst into sub-documents
2020-03-09 21:58 ` [PATCH 2/5] docs/system: Split target-arm.rst into sub-documents Peter Maydell
2020-03-10 14:29 ` Alex Bennée
@ 2020-03-10 20:53 ` Niek Linnenbank
1 sibling, 0 replies; 18+ messages in thread
From: Niek Linnenbank @ 2020-03-10 20:53 UTC (permalink / raw)
To: Peter Maydell; +Cc: qemu-arm, QEMU Developers
[-- Attachment #1: Type: text/plain, Size: 20690 bytes --]
Reviewed-by: Niek Linnenbank <nieklinnenbank@gmail.com>
On Mon, Mar 9, 2020 at 10:58 PM Peter Maydell <peter.maydell@linaro.org>
wrote:
> Currently the documentation for Arm system emulator targets is in a
> single target-arm.rst. This describes only some of the boards and
> often in a fairly abbreviated fashion. Restructure it so that each
> board has its own documentation file in the docs/system/arm/
> subdirectory.
>
> This will hopefully encourage us to write board documentation that
> describes the board in detail, rather than a few brief paragraphs
> in a single long page. The table of contents should also help users
> to find the board they care about faster.
>
> Once the structure is in place we'll be able to move microvm.rst
> from the top-level docs/ directory.
>
> All the text from the old page is retained, except for the final
> paragraph ("A Linux 2.6 test image is available on the QEMU web site.
> More information is available in the QEMU mailing-list archive."),
> which is deleted. The git history shows this was originally added
> in reference to the integratorcp board (at that time the only
> Arm board that was supported), and has subsequently gradually been
> further and further separated from the integratorcp documentation
> by the insertion of other board documentation sections. It's
> extremely out of date and no longer accurate, since AFAICT there
> isn't an integratorcp kernel on the website any more; so better
> deleted than retained.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> A subsequent patch will add some text that at least gestures
> in the direction of some of the more obvious missing info,
> eg 64-bit boards.
> ---
> MAINTAINERS | 9 ++
> docs/system/arm/integratorcp.rst | 16 +++
> docs/system/arm/musicpal.rst | 19 +++
> docs/system/arm/nseries.rst | 33 +++++
> docs/system/arm/palm.rst | 23 ++++
> docs/system/arm/realview.rst | 34 +++++
> docs/system/arm/stellaris.rst | 26 ++++
> docs/system/arm/sx1.rst | 18 +++
> docs/system/arm/versatile.rst | 29 ++++
> docs/system/arm/xscale.rst | 29 ++++
> docs/system/target-arm.rst | 225 ++-----------------------------
> 11 files changed, 249 insertions(+), 212 deletions(-)
> create mode 100644 docs/system/arm/integratorcp.rst
> create mode 100644 docs/system/arm/musicpal.rst
> create mode 100644 docs/system/arm/nseries.rst
> create mode 100644 docs/system/arm/palm.rst
> create mode 100644 docs/system/arm/realview.rst
> create mode 100644 docs/system/arm/stellaris.rst
> create mode 100644 docs/system/arm/sx1.rst
> create mode 100644 docs/system/arm/versatile.rst
> create mode 100644 docs/system/arm/xscale.rst
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 36d0c6887a9..31a1b423df1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -155,6 +155,7 @@ F: include/hw/cpu/a*mpcore.h
> F: disas/arm.c
> F: disas/arm-a64.cc
> F: disas/libvixl/
> +F: docs/system/target-arm.rst
>
> ARM SMMU
> M: Eric Auger <eric.auger@redhat.com>
> @@ -615,6 +616,7 @@ F: hw/arm/integratorcp.c
> F: hw/misc/arm_integrator_debug.c
> F: include/hw/misc/arm_integrator_debug.h
> F: tests/acceptance/machine_arm_integratorcp.py
> +F: docs/system/arm/integratorcp.rst
>
> MCIMX6UL EVK / i.MX6ul
> M: Peter Maydell <peter.maydell@linaro.org>
> @@ -673,6 +675,7 @@ M: Peter Maydell <peter.maydell@linaro.org>
> L: qemu-arm@nongnu.org
> S: Odd Fixes
> F: hw/arm/musicpal.c
> +F: docs/system/arm/musicpal.rst
>
> nSeries
> M: Andrzej Zaborowski <balrogg@gmail.com>
> @@ -689,6 +692,7 @@ F: include/hw/display/blizzard.h
> F: include/hw/input/tsc2xxx.h
> F: include/hw/misc/cbus.h
> F: tests/acceptance/machine_arm_n8x0.py
> +F: docs/system/arm/nseries.rst
>
> Palm
> M: Andrzej Zaborowski <balrogg@gmail.com>
> @@ -698,6 +702,7 @@ S: Odd Fixes
> F: hw/arm/palm.c
> F: hw/input/tsc210x.c
> F: include/hw/input/tsc2xxx.h
> +F: docs/system/arm/palm.rst
>
> Raspberry Pi
> M: Peter Maydell <peter.maydell@linaro.org>
> @@ -719,6 +724,7 @@ F: hw/arm/realview*
> F: hw/cpu/realview_mpcore.c
> F: hw/intc/realview_gic.c
> F: include/hw/intc/realview_gic.h
> +F: docs/system/arm/realview.rst
>
> PXA2XX
> M: Andrzej Zaborowski <balrogg@gmail.com>
> @@ -738,6 +744,7 @@ F: hw/misc/max111x.c
> F: include/hw/arm/pxa.h
> F: include/hw/arm/sharpsl.h
> F: include/hw/display/tc6393xb.h
> +F: docs/system/arm/xscale.rst
>
> SABRELITE / i.MX6
> M: Peter Maydell <peter.maydell@linaro.org>
> @@ -773,6 +780,7 @@ L: qemu-arm@nongnu.org
> S: Maintained
> F: hw/*/stellaris*
> F: include/hw/input/gamepad.h
> +F: docs/system/arm/stellaris.rst
>
> Versatile Express
> M: Peter Maydell <peter.maydell@linaro.org>
> @@ -786,6 +794,7 @@ L: qemu-arm@nongnu.org
> S: Maintained
> F: hw/*/versatile*
> F: hw/misc/arm_sysctl.c
> +F: docs/system/arm/versatile.rst
>
> Virt
> M: Peter Maydell <peter.maydell@linaro.org>
> diff --git a/docs/system/arm/integratorcp.rst
> b/docs/system/arm/integratorcp.rst
> new file mode 100644
> index 00000000000..3232b43a08b
> --- /dev/null
> +++ b/docs/system/arm/integratorcp.rst
> @@ -0,0 +1,16 @@
> +Integrator/CP (``integratorcp``)
> +================================
> +
> +The ARM Integrator/CP board is emulated with the following devices:
> +
> +- ARM926E, ARM1026E, ARM946E, ARM1136 or Cortex-A8 CPU
> +
> +- Two PL011 UARTs
> +
> +- SMC 91c111 Ethernet adapter
> +
> +- PL110 LCD controller
> +
> +- PL050 KMI with PS/2 keyboard and mouse.
> +
> +- PL181 MultiMedia Card Interface with SD card.
> diff --git a/docs/system/arm/musicpal.rst b/docs/system/arm/musicpal.rst
> new file mode 100644
> index 00000000000..35c22212486
> --- /dev/null
> +++ b/docs/system/arm/musicpal.rst
> @@ -0,0 +1,19 @@
> +Freecom MusicPal (``musicpal``)
> +===============================
> +
> +The Freecom MusicPal internet radio emulation includes the following
> +elements:
> +
> +- Marvell MV88W8618 ARM core.
> +
> +- 32 MB RAM, 256 KB SRAM, 8 MB flash.
> +
> +- Up to 2 16550 UARTs
> +
> +- MV88W8xx8 Ethernet controller
> +
> +- MV88W8618 audio controller, WM8750 CODEC and mixer
> +
> +- 128x64 display with brightness control
> +
> +- 2 buttons, 2 navigation wheels with button function
> diff --git a/docs/system/arm/nseries.rst b/docs/system/arm/nseries.rst
> new file mode 100644
> index 00000000000..b000b6d13bb
> --- /dev/null
> +++ b/docs/system/arm/nseries.rst
> @@ -0,0 +1,33 @@
> +Nokia N800 and N810 tablets (``n800``, ``n810``)
> +================================================
>
+
> +Nokia N800 and N810 internet tablets (known also as RX-34 and RX-44 /
> +48) emulation supports the following elements:
> +
> +- Texas Instruments OMAP2420 System-on-chip (ARM 1136 core)
> +
> +- RAM and non-volatile OneNAND Flash memories
> +
> +- Display connected to EPSON remote framebuffer chip and OMAP on-chip
> + display controller and a LS041y3 MIPI DBI-C controller
> +
> +- TI TSC2301 (in N800) and TI TSC2005 (in N810) touchscreen
> + controllers driven through SPI bus
> +
> +- National Semiconductor LM8323-controlled qwerty keyboard driven
> + through |I2C| bus
> +
> +- Secure Digital card connected to OMAP MMC/SD host
> +
> +- Three OMAP on-chip UARTs and on-chip STI debugging console
> +
> +- Mentor Graphics \"Inventra\" dual-role USB controller embedded in a
> + TI TUSB6010 chip - only USB host mode is supported
> +
> +- TI TMP105 temperature sensor driven through |I2C| bus
> +
> +- TI TWL92230C power management companion with an RTC on
> + |I2C| bus
> +
> +- Nokia RETU and TAHVO multi-purpose chips with an RTC, connected
> + through CBUS
> diff --git a/docs/system/arm/palm.rst b/docs/system/arm/palm.rst
> new file mode 100644
> index 00000000000..0eabf63e0e7
> --- /dev/null
> +++ b/docs/system/arm/palm.rst
> @@ -0,0 +1,23 @@
> +Palm Tungsten|E PDA (``cheetah``)
> +=================================
> +
> +The Palm Tungsten|E PDA (codename \"Cheetah\") emulation includes the
> +following elements:
> +
> +- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> +
> +- ROM and RAM memories (ROM firmware image can be loaded with
> + -option-rom)
> +
> +- On-chip LCD controller
> +
> +- On-chip Real Time Clock
> +
> +- TI TSC2102i touchscreen controller / analog-digital converter /
> + Audio CODEC, connected through MicroWire and |I2S| busses
> +
> +- GPIO-connected matrix keypad
> +
> +- Secure Digital card connected to OMAP MMC/SD host
> +
> +- Three on-chip UARTs
> diff --git a/docs/system/arm/realview.rst b/docs/system/arm/realview.rst
> new file mode 100644
> index 00000000000..8e08eb5da16
> --- /dev/null
> +++ b/docs/system/arm/realview.rst
> @@ -0,0 +1,34 @@
> +Arm Realview boards (``realview-eb``, ``realview-eb-mpcore``,
> ``realview-pb-a8``, ``realview-pbx-a9``)
>
> +======================================================================================================
> +
> +Several variants of the ARM RealView baseboard are emulated, including
> +the EB, PB-A8 and PBX-A9. Due to interactions with the bootloader, only
> +certain Linux kernel configurations work out of the box on these boards.
> +
> +Kernels for the PB-A8 board should have CONFIG_REALVIEW_HIGH_PHYS_OFFSET
> +enabled in the kernel, and expect 512M RAM. Kernels for The PBX-A9 board
> +should have CONFIG_SPARSEMEM enabled, CONFIG_REALVIEW_HIGH_PHYS_OFFSET
> +disabled and expect 1024M RAM.
> +
> +The following devices are emulated:
> +
> +- ARM926E, ARM1136, ARM11MPCore, Cortex-A8 or Cortex-A9 MPCore CPU
> +
> +- ARM AMBA Generic/Distributed Interrupt Controller
> +
> +- Four PL011 UARTs
> +
> +- SMC 91c111 or SMSC LAN9118 Ethernet adapter
> +
> +- PL110 LCD controller
> +
> +- PL050 KMI with PS/2 keyboard and mouse
> +
> +- PCI host bridge
> +
> +- PCI OHCI USB controller
> +
> +- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
> + devices
> +
> +- PL181 MultiMedia Card Interface with SD card.
> diff --git a/docs/system/arm/stellaris.rst b/docs/system/arm/stellaris.rst
> new file mode 100644
> index 00000000000..8af4ad79c79
> --- /dev/null
> +++ b/docs/system/arm/stellaris.rst
> @@ -0,0 +1,26 @@
> +Stellaris boards (``lm3s6965evb``, ``lm3s811evb``)
> +==================================================
> +
> +The Luminary Micro Stellaris LM3S811EVB emulation includes the following
> +devices:
> +
> +- Cortex-M3 CPU core.
> +
> +- 64k Flash and 8k SRAM.
> +
> +- Timers, UARTs, ADC and |I2C| interface.
> +
> +- OSRAM Pictiva 96x16 OLED with SSD0303 controller on
> + |I2C| bus.
> +
> +The Luminary Micro Stellaris LM3S6965EVB emulation includes the
> +following devices:
> +
> +- Cortex-M3 CPU core.
> +
> +- 256k Flash and 64k SRAM.
> +
> +- Timers, UARTs, ADC, |I2C| and SSI interfaces.
> +
> +- OSRAM Pictiva 128x64 OLED with SSD0323 controller connected via
> + SSI.
> diff --git a/docs/system/arm/sx1.rst b/docs/system/arm/sx1.rst
> new file mode 100644
> index 00000000000..321993bc098
> --- /dev/null
> +++ b/docs/system/arm/sx1.rst
> @@ -0,0 +1,18 @@
> +Siemens SX1 (``sx1``, ``sx1-v1``)
> +=================================
> +
> +The Siemens SX1 models v1 and v2 (default) basic emulation. The
> +emulation includes the following elements:
> +
> +- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> +
> +- ROM and RAM memories (ROM firmware image can be loaded with
> + -pflash) V1 1 Flash of 16MB and 1 Flash of 8MB V2 1 Flash of 32MB
> +
> +- On-chip LCD controller
> +
> +- On-chip Real Time Clock
> +
> +- Secure Digital card connected to OMAP MMC/SD host
> +
> +- Three on-chip UARTs
> diff --git a/docs/system/arm/versatile.rst b/docs/system/arm/versatile.rst
> new file mode 100644
> index 00000000000..48b6ca0a020
> --- /dev/null
> +++ b/docs/system/arm/versatile.rst
> @@ -0,0 +1,29 @@
> +Arm Versatile boards (``versatileab``, ``versatilepb``)
> +=======================================================
> +
> +The ARM Versatile baseboard is emulated with the following devices:
> +
> +- ARM926E, ARM1136 or Cortex-A8 CPU
> +
> +- PL190 Vectored Interrupt Controller
> +
> +- Four PL011 UARTs
> +
> +- SMC 91c111 Ethernet adapter
> +
> +- PL110 LCD controller
> +
> +- PL050 KMI with PS/2 keyboard and mouse.
> +
> +- PCI host bridge. Note the emulated PCI bridge only provides access
> + to PCI memory space. It does not provide access to PCI IO space. This
> + means some devices (eg. ne2k_pci NIC) are not usable, and others (eg.
> + rtl8139 NIC) are only usable when the guest drivers use the memory
> + mapped control registers.
> +
> +- PCI OHCI USB controller.
> +
> +- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
> + devices.
> +
> +- PL181 MultiMedia Card Interface with SD card.
> diff --git a/docs/system/arm/xscale.rst b/docs/system/arm/xscale.rst
> new file mode 100644
> index 00000000000..19da2eff352
> --- /dev/null
> +++ b/docs/system/arm/xscale.rst
> @@ -0,0 +1,29 @@
> +Sharp XScale-based PDA models (``akita``, ``borzoi``, ``spitz``,
> ``terrier``)
>
> +=============================================================================
> +
> +The XScale-based clamshell PDA models (\"Spitz\", \"Akita\", \"Borzoi\"
> +and \"Terrier\") emulation includes the following peripherals:
> +
> +- Intel PXA270 System-on-chip (ARM V5TE core)
> +
> +- NAND Flash memory
> +
> +- IBM/Hitachi DSCM microdrive in a PXA PCMCIA slot - not in \"Akita\"
> +
> +- On-chip OHCI USB controller
> +
> +- On-chip LCD controller
> +
> +- On-chip Real Time Clock
> +
> +- TI ADS7846 touchscreen controller on SSP bus
> +
> +- Maxim MAX1111 analog-digital converter on |I2C| bus
> +
> +- GPIO-connected keyboard controller and LEDs
> +
> +- Secure Digital card connected to PXA MMC/SD host
> +
> +- Three on-chip UARTs
> +
> +- WM8750 audio CODEC on |I2C| and |I2S| busses
> diff --git a/docs/system/target-arm.rst b/docs/system/target-arm.rst
> index d2a3b44ce88..c7df6fc1f97 100644
> --- a/docs/system/target-arm.rst
> +++ b/docs/system/target-arm.rst
> @@ -3,215 +3,16 @@
> ARM System emulator
> -------------------
>
> -Use the executable ``qemu-system-arm`` to simulate a ARM machine. The
> -ARM Integrator/CP board is emulated with the following devices:
> -
> -- ARM926E, ARM1026E, ARM946E, ARM1136 or Cortex-A8 CPU
> -
> -- Two PL011 UARTs
> -
> -- SMC 91c111 Ethernet adapter
> -
> -- PL110 LCD controller
> -
> -- PL050 KMI with PS/2 keyboard and mouse.
> -
> -- PL181 MultiMedia Card Interface with SD card.
> -
> -The ARM Versatile baseboard is emulated with the following devices:
> -
> -- ARM926E, ARM1136 or Cortex-A8 CPU
> -
> -- PL190 Vectored Interrupt Controller
> -
> -- Four PL011 UARTs
> -
> -- SMC 91c111 Ethernet adapter
> -
> -- PL110 LCD controller
> -
> -- PL050 KMI with PS/2 keyboard and mouse.
> -
> -- PCI host bridge. Note the emulated PCI bridge only provides access
> - to PCI memory space. It does not provide access to PCI IO space. This
> - means some devices (eg. ne2k_pci NIC) are not usable, and others (eg.
> - rtl8139 NIC) are only usable when the guest drivers use the memory
> - mapped control registers.
> -
> -- PCI OHCI USB controller.
> -
> -- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
> - devices.
> -
> -- PL181 MultiMedia Card Interface with SD card.
> -
> -Several variants of the ARM RealView baseboard are emulated, including
> -the EB, PB-A8 and PBX-A9. Due to interactions with the bootloader, only
> -certain Linux kernel configurations work out of the box on these boards.
> -
> -Kernels for the PB-A8 board should have CONFIG_REALVIEW_HIGH_PHYS_OFFSET
> -enabled in the kernel, and expect 512M RAM. Kernels for The PBX-A9 board
> -should have CONFIG_SPARSEMEM enabled, CONFIG_REALVIEW_HIGH_PHYS_OFFSET
> -disabled and expect 1024M RAM.
> -
> -The following devices are emulated:
> -
> -- ARM926E, ARM1136, ARM11MPCore, Cortex-A8 or Cortex-A9 MPCore CPU
> -
> -- ARM AMBA Generic/Distributed Interrupt Controller
> -
> -- Four PL011 UARTs
> -
> -- SMC 91c111 or SMSC LAN9118 Ethernet adapter
> -
> -- PL110 LCD controller
> -
> -- PL050 KMI with PS/2 keyboard and mouse
> -
> -- PCI host bridge
> -
> -- PCI OHCI USB controller
> -
> -- LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM
> - devices
> -
> -- PL181 MultiMedia Card Interface with SD card.
> -
> -The XScale-based clamshell PDA models (\"Spitz\", \"Akita\", \"Borzoi\"
> -and \"Terrier\") emulation includes the following peripherals:
> -
> -- Intel PXA270 System-on-chip (ARM V5TE core)
> -
> -- NAND Flash memory
> -
> -- IBM/Hitachi DSCM microdrive in a PXA PCMCIA slot - not in \"Akita\"
> -
> -- On-chip OHCI USB controller
> -
> -- On-chip LCD controller
> -
> -- On-chip Real Time Clock
> -
> -- TI ADS7846 touchscreen controller on SSP bus
> -
> -- Maxim MAX1111 analog-digital converter on |I2C| bus
> -
> -- GPIO-connected keyboard controller and LEDs
> -
> -- Secure Digital card connected to PXA MMC/SD host
> -
> -- Three on-chip UARTs
> -
> -- WM8750 audio CODEC on |I2C| and |I2S| busses
> -
> -The Palm Tungsten|E PDA (codename \"Cheetah\") emulation includes the
> -following elements:
> -
> -- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> -
> -- ROM and RAM memories (ROM firmware image can be loaded with
> - -option-rom)
> -
> -- On-chip LCD controller
> -
> -- On-chip Real Time Clock
> -
> -- TI TSC2102i touchscreen controller / analog-digital converter /
> - Audio CODEC, connected through MicroWire and |I2S| busses
> -
> -- GPIO-connected matrix keypad
> -
> -- Secure Digital card connected to OMAP MMC/SD host
> -
> -- Three on-chip UARTs
> -
> -Nokia N800 and N810 internet tablets (known also as RX-34 and RX-44 /
> -48) emulation supports the following elements:
> -
> -- Texas Instruments OMAP2420 System-on-chip (ARM 1136 core)
> -
> -- RAM and non-volatile OneNAND Flash memories
> -
> -- Display connected to EPSON remote framebuffer chip and OMAP on-chip
> - display controller and a LS041y3 MIPI DBI-C controller
> -
> -- TI TSC2301 (in N800) and TI TSC2005 (in N810) touchscreen
> - controllers driven through SPI bus
> -
> -- National Semiconductor LM8323-controlled qwerty keyboard driven
> - through |I2C| bus
> -
> -- Secure Digital card connected to OMAP MMC/SD host
> -
> -- Three OMAP on-chip UARTs and on-chip STI debugging console
> -
> -- Mentor Graphics \"Inventra\" dual-role USB controller embedded in a
> - TI TUSB6010 chip - only USB host mode is supported
> -
> -- TI TMP105 temperature sensor driven through |I2C| bus
> -
> -- TI TWL92230C power management companion with an RTC on
> - |I2C| bus
> -
> -- Nokia RETU and TAHVO multi-purpose chips with an RTC, connected
> - through CBUS
> -
> -The Luminary Micro Stellaris LM3S811EVB emulation includes the following
> -devices:
> -
> -- Cortex-M3 CPU core.
> -
> -- 64k Flash and 8k SRAM.
> -
> -- Timers, UARTs, ADC and |I2C| interface.
> -
> -- OSRAM Pictiva 96x16 OLED with SSD0303 controller on
> - |I2C| bus.
> -
> -The Luminary Micro Stellaris LM3S6965EVB emulation includes the
> -following devices:
> -
> -- Cortex-M3 CPU core.
> -
> -- 256k Flash and 64k SRAM.
> -
> -- Timers, UARTs, ADC, |I2C| and SSI interfaces.
> -
> -- OSRAM Pictiva 128x64 OLED with SSD0323 controller connected via
> - SSI.
> -
> -The Freecom MusicPal internet radio emulation includes the following
> -elements:
> -
> -- Marvell MV88W8618 ARM core.
> -
> -- 32 MB RAM, 256 KB SRAM, 8 MB flash.
> -
> -- Up to 2 16550 UARTs
> -
> -- MV88W8xx8 Ethernet controller
> -
> -- MV88W8618 audio controller, WM8750 CODEC and mixer
> -
> -- 128x64 display with brightness control
> -
> -- 2 buttons, 2 navigation wheels with button function
> -
> -The Siemens SX1 models v1 and v2 (default) basic emulation. The
> -emulation includes the following elements:
> -
> -- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> -
> -- ROM and RAM memories (ROM firmware image can be loaded with
> - -pflash) V1 1 Flash of 16MB and 1 Flash of 8MB V2 1 Flash of 32MB
> -
> -- On-chip LCD controller
> -
> -- On-chip Real Time Clock
> -
> -- Secure Digital card connected to OMAP MMC/SD host
> -
> -- Three on-chip UARTs
> -
> -A Linux 2.6 test image is available on the QEMU web site. More
> -information is available in the QEMU mailing-list archive.
> +Use the executable ``qemu-system-arm`` to simulate a ARM machine.
> +
> +.. toctree::
> +
> + arm/integratorcp
> + arm/versatile
> + arm/realview
> + arm/xscale
> + arm/palm
> + arm/nseries
> + arm/stellaris
> + arm/musicpal
> + arm/sx1
> --
> 2.20.1
>
>
--
Niek Linnenbank
[-- Attachment #2: Type: text/html, Size: 24648 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 3/5] docs/system/target-arm.rst: Add some introductory text
2020-03-09 21:58 ` [PATCH 3/5] docs/system/target-arm.rst: Add some introductory text Peter Maydell
2020-03-10 14:54 ` Alex Bennée
@ 2020-03-10 20:58 ` Niek Linnenbank
1 sibling, 0 replies; 18+ messages in thread
From: Niek Linnenbank @ 2020-03-10 20:58 UTC (permalink / raw)
To: Peter Maydell; +Cc: qemu-arm, QEMU Developers
[-- Attachment #1: Type: text/plain, Size: 4525 bytes --]
Reviewed-by: Niek Linnenbank <nieklinnenbank@gmail.com>
On Mon, Mar 9, 2020 at 10:58 PM Peter Maydell <peter.maydell@linaro.org>
wrote:
> Now we've moved the various bits of per-board documentation into
> their own files, the top level document is a little bare. Add
> some introductory information, including a note that many
> of the board models we support are currently undocumented.
>
> (Most sections of this new text were originally written by me
> for the wiki page https://wiki.qemu.org/Documentation/Platforms/ARM)
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> ---
> docs/system/target-arm.rst | 66 ++++++++++++++++++++++++++++++++++++--
> 1 file changed, 64 insertions(+), 2 deletions(-)
>
> diff --git a/docs/system/target-arm.rst b/docs/system/target-arm.rst
> index c7df6fc1f97..86ea6f2f568 100644
> --- a/docs/system/target-arm.rst
> +++ b/docs/system/target-arm.rst
> @@ -1,9 +1,71 @@
> .. _ARM-System-emulator:
>
> -ARM System emulator
> +Arm System emulator
> -------------------
>
> -Use the executable ``qemu-system-arm`` to simulate a ARM machine.
> +QEMU can emulate both 32-bit and 64-bit Arm CPUs. Use the
> +``qemu-system-aarch64`` executable to simulate a 64-bit Arm machine.
> +You can use either ``qemu-system-arm`` or ``qemu-system-aarch64``
> +to simulate a 32-bit Arm machine: in general, command lines that
> +work for ``qemu-system-arm`` will behave the same when used with
> +``qemu-system-aarch64``.
> +
> +QEMU has generally good support for Arm guests. It has support for
> +nearly fifty different machines. The reason we support so many is that
> +Arm hardware is much more widely varying than x86 hardware. Arm CPUs
> +are generally built into "system-on-chip" (SoC) designs created by
> +many different companies with different devices, and these SoCs are
> +then built into machines which can vary still further even if they use
> +the same SoC. Even with fifty boards QEMU does not cover more than a
> +small fraction of the Arm hardware ecosystem.
> +
> +The situation for 64-bit Arm is fairly similar, except that we don't
> +implement so many different machines.
> +
> +As well as the more common "A-profile" CPUs (which have MMUs and will
> +run Linux) QEMU also supports "M-profile" CPUs such as the Cortex-M0,
> +Cortex-M4 and Cortex-M33 (which are microcontrollers used in very
> +embedded boards). For most boards the CPU type is fixed (matching what
> +the hardware has), so typically you don't need to specify the CPU type
> +by hand, except for special cases like the ``virt`` board.
> +
> +Choosing a board model
> +======================
> +
> +For QEMU's Arm system emulation, you must specify which board
> +model you want to use with the ``-M`` or ``--machine`` option;
> +there is no default.
> +
> +Because Arm systems differ so much and in fundamental ways, typically
> +operating system or firmware images intended to run on one machine
> +will not run at all on any other. This is often surprising for new
> +users who are used to the x86 world where every system looks like a
> +standard PC. (Once the kernel has booted, most userspace software
> +cares much less about the detail of the hardware.)
> +
> +If you already have a system image or a kernel that works on hardware
> +and you want to boot with QEMU, check whether QEMU lists that machine
> +in its ``-machine help`` output. If it is listed, then you can probably
> +use that board model. If it is not listed, then unfortunately your image
> +will almost certainly not boot on QEMU. (You might be able to
> +extract the filesystem and use that with a different kernel which
> +boots on a system that QEMU does emulate.)
> +
> +If you don't care about reproducing the idiosyncrasies of a particular
> +bit of hardware, such as small amount of RAM, no PCI or other hard
> +disk, etc., and just want to run Linux, the best option is to use the
> +``virt`` board. This is a platform which doesn't correspond to any
> +real hardware and is designed for use in virtual machines. You'll
> +need to compile Linux with a suitable configuration for running on
> +the ``virt`` board. ``virt`` supports PCI, virtio, recent CPUs and
> +large amounts of RAM. It also supports 64-bit CPUs.
> +
> +Board-specific documentation
> +============================
> +
> +Unfortunately many of the Arm boards QEMU supports are currently
> +undocumented; you can get a complete list by running
> +``qemu-system-aarch64 --machine help``.
>
> .. toctree::
>
> --
> 2.20.1
>
>
--
Niek Linnenbank
[-- Attachment #2: Type: text/html, Size: 5491 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 4/5] docs: Move arm-cpu-features.rst into the system manual
2020-03-09 21:58 ` [PATCH 4/5] docs: Move arm-cpu-features.rst into the system manual Peter Maydell
2020-03-10 14:54 ` Alex Bennée
@ 2020-03-10 21:00 ` Niek Linnenbank
1 sibling, 0 replies; 18+ messages in thread
From: Niek Linnenbank @ 2020-03-10 21:00 UTC (permalink / raw)
To: Peter Maydell; +Cc: qemu-arm, QEMU Developers
[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]
Reviewed-by: Niek Linnenbank <nieklinnenbank@gmail.com>
On Mon, Mar 9, 2020 at 10:58 PM Peter Maydell <peter.maydell@linaro.org>
wrote:
> Now we have somewhere to put arm-specific rst documentation,
> we can move arm-cpu-features.rst from the docs/ top level
> directory into docs/system/arm/.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> .../{arm-cpu-features.rst => system/arm/cpu-features.rst} | 8 +-------
> docs/system/target-arm.rst | 6 ++++++
> 2 files changed, 7 insertions(+), 7 deletions(-)
> rename docs/{arm-cpu-features.rst => system/arm/cpu-features.rst} (99%)
>
> diff --git a/docs/arm-cpu-features.rst b/docs/system/arm/cpu-features.rst
> similarity index 99%
> rename from docs/arm-cpu-features.rst
> rename to docs/system/arm/cpu-features.rst
> index fc1623aeca5..7495b7b672b 100644
> --- a/docs/arm-cpu-features.rst
> +++ b/docs/system/arm/cpu-features.rst
> @@ -1,11 +1,5 @@
> +Arm CPU Features
> ================
> -ARM CPU Features
> -================
> -
> -Examples of probing and using ARM CPU features
> -
> -Introduction
> -============
>
> CPU features are optional features that a CPU of supporting type may
> choose to implement or not. In QEMU, optional CPU features have
> diff --git a/docs/system/target-arm.rst b/docs/system/target-arm.rst
> index 86ea6f2f568..1425bd5303a 100644
> --- a/docs/system/target-arm.rst
> +++ b/docs/system/target-arm.rst
> @@ -78,3 +78,9 @@ undocumented; you can get a complete list by running
> arm/stellaris
> arm/musicpal
> arm/sx1
> +
> +Arm CPU features
> +================
> +
> +.. toctree::
> + arm/cpu-features
> --
> 2.20.1
>
>
--
Niek Linnenbank
[-- Attachment #2: Type: text/html, Size: 2399 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 5/5] docs: Be consistent about capitalization of 'Arm'
2020-03-09 21:58 ` [PATCH 5/5] docs: Be consistent about capitalization of 'Arm' Peter Maydell
2020-03-10 14:55 ` Alex Bennée
@ 2020-03-10 21:01 ` Niek Linnenbank
1 sibling, 0 replies; 18+ messages in thread
From: Niek Linnenbank @ 2020-03-10 21:01 UTC (permalink / raw)
To: Peter Maydell; +Cc: qemu-arm, QEMU Developers
[-- Attachment #1: Type: text/plain, Size: 16530 bytes --]
Reviewed-by: Niek Linnenbank <nieklinnenbank@gmail.com>
On Mon, Mar 9, 2020 at 10:58 PM Peter Maydell <peter.maydell@linaro.org>
wrote:
> The company 'Arm' went through a rebranding some years back
> involving a recapitalization from 'ARM' to 'Arm'. As a result
> our documentation is a bit inconsistent between the two forms.
> It's not worth trying to update everywhere in QEMU, but it's
> easy enough to make docs/ consistent.
>
> Note that "ARMv8" and similar architecture names, and
> older CPU names like "ARM926" still retain all-caps.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> I don't feel very strongly about this change, but it
> looked a bit odd where earlier rearrangements in this
> series meant that some documents had a mix of both styles,
> so I thought I might as well fix all of docs/.
> ---
> docs/can.txt | 2 +-
> docs/devel/atomics.txt | 2 +-
> docs/devel/multi-thread-tcg.txt | 8 ++++----
> docs/replay.txt | 2 +-
> docs/specs/fw_cfg.txt | 2 +-
> docs/devel/kconfig.rst | 2 +-
> docs/devel/loads-stores.rst | 2 +-
> docs/devel/tcg.rst | 2 +-
> docs/specs/tpm.rst | 6 +++---
> docs/system/arm/cpu-features.rst | 4 ++--
> docs/system/arm/integratorcp.rst | 2 +-
> docs/system/arm/musicpal.rst | 2 +-
> docs/system/arm/nseries.rst | 2 +-
> docs/system/arm/palm.rst | 2 +-
> docs/system/arm/realview.rst | 4 ++--
> docs/system/arm/sx1.rst | 2 +-
> docs/system/arm/versatile.rst | 2 +-
> docs/system/arm/xscale.rst | 2 +-
> docs/user/main.rst | 8 ++++----
> 19 files changed, 29 insertions(+), 29 deletions(-)
>
> diff --git a/docs/can.txt b/docs/can.txt
> index 9fa6ed51c82..11ed8f2d68b 100644
> --- a/docs/can.txt
> +++ b/docs/can.txt
> @@ -13,7 +13,7 @@ controller is implemented.
>
> The PCI addon card hardware has been selected as the first CAN
> interface to implement because such device can be easily connected
> -to systems with different CPU architectures (x86, PowerPC, ARM, etc.).
> +to systems with different CPU architectures (x86, PowerPC, Arm, etc.).
>
> The project has been initially started in frame of RTEMS GSoC 2013
> slot by Jin Yang under our mentoring The initial idea was to provide
> generic
> diff --git a/docs/devel/atomics.txt b/docs/devel/atomics.txt
> index a4db3a4aaad..67bdf826280 100644
> --- a/docs/devel/atomics.txt
> +++ b/docs/devel/atomics.txt
> @@ -87,7 +87,7 @@ Sequentially consistent loads and stores can be done
> using:
> atomic_xchg(ptr, val) for stores
>
> However, they are quite expensive on some platforms, notably POWER and
> -ARM. Therefore, qemu/atomic.h provides two primitives with slightly
> +Arm. Therefore, qemu/atomic.h provides two primitives with slightly
> weaker constraints:
>
> typeof(*ptr) atomic_mb_read(ptr)
> diff --git a/docs/devel/multi-thread-tcg.txt
> b/docs/devel/multi-thread-tcg.txt
> index 782bebc28b4..3c85ac0eab9 100644
> --- a/docs/devel/multi-thread-tcg.txt
> +++ b/docs/devel/multi-thread-tcg.txt
> @@ -227,7 +227,7 @@ minimise contention.
> (Current solution)
>
> MMIO access automatically serialises hardware emulation by way of the
> -BQL. Currently ARM targets serialise all ARM_CP_IO register accesses
> +BQL. Currently Arm targets serialise all ARM_CP_IO register accesses
> and also defer the reset/startup of vCPUs to the vCPU context by way
> of async_run_on_cpu().
>
> @@ -268,7 +268,7 @@ ordered backends this could become a NOP.
> Aside from explicit standalone memory barrier instructions there are
> also implicit memory ordering semantics which comes with each guest
> memory access instruction. For example all x86 load/stores come with
> -fairly strong guarantees of sequential consistency where as ARM has
> +fairly strong guarantees of sequential consistency whereas Arm has
> special variants of load/store instructions that imply acquire/release
> semantics.
>
> @@ -317,7 +317,7 @@ x86 cmpxchg instruction.
>
> The second type offer a pair of load/store instructions which offer a
> guarantee that a region of memory has not been touched between the
> -load and store instructions. An example of this is ARM's ldrex/strex
> +load and store instructions. An example of this is Arm's ldrex/strex
> pair where the strex instruction will return a flag indicating a
> successful store only if no other CPU has accessed the memory region
> since the ldrex.
> @@ -339,7 +339,7 @@ CURRENT OPEN QUESTIONS:
>
> The TCG provides a number of atomic helpers (tcg_gen_atomic_*) which
> can be used directly or combined to emulate other instructions like
> -ARM's ldrex/strex instructions. While they are susceptible to the ABA
> +Arm's ldrex/strex instructions. While they are susceptible to the ABA
> problem so far common guests have not implemented patterns where
> this may be a problem - typically presenting a locking ABI which
> assumes cmpxchg like semantics.
> diff --git a/docs/replay.txt b/docs/replay.txt
> index f4619a62a3d..70c27edb362 100644
> --- a/docs/replay.txt
> +++ b/docs/replay.txt
> @@ -19,7 +19,7 @@ Deterministic replay has the following features:
> the memory, state of the hardware devices, clocks, and screen of the
> VM.
> * Writes execution log into the file for later replaying for multiple
> times
> on different machines.
> - * Supports i386, x86_64, and ARM hardware platforms.
> + * Supports i386, x86_64, and Arm hardware platforms.
> * Performs deterministic replay of all operations with keyboard and mouse
> input devices.
>
> diff --git a/docs/specs/fw_cfg.txt b/docs/specs/fw_cfg.txt
> index 08c00bdf44a..8f1ebc66fa4 100644
> --- a/docs/specs/fw_cfg.txt
> +++ b/docs/specs/fw_cfg.txt
> @@ -82,7 +82,7 @@ Selector Register IOport: 0x510
> Data Register IOport: 0x511
> DMA Address IOport: 0x514
>
> -=== ARM Register Locations ===
> +=== Arm Register Locations ===
>
> Selector Register address: Base + 8 (2 bytes)
> Data Register address: Base + 0 (8 bytes)
> diff --git a/docs/devel/kconfig.rst b/docs/devel/kconfig.rst
> index b7bca447046..e5df72b3422 100644
> --- a/docs/devel/kconfig.rst
> +++ b/docs/devel/kconfig.rst
> @@ -8,7 +8,7 @@ time different targets can share large amounts of code.
> For example,
> a POWER and an x86 board can run the same code to emulate a PCI network
> card, even though the boards use different PCI host bridges, and they
> can run the same code to emulate a SCSI disk while using different
> -SCSI adapters. ARM, s390 and x86 boards can all present a virtio-blk
> +SCSI adapters. Arm, s390 and x86 boards can all present a virtio-blk
> disk to their guests, but with three different virtio guest interfaces.
>
> Each QEMU target enables a subset of the boards, devices and buses that
> diff --git a/docs/devel/loads-stores.rst b/docs/devel/loads-stores.rst
> index 03aa9e7ff80..0d99eb24c1b 100644
> --- a/docs/devel/loads-stores.rst
> +++ b/docs/devel/loads-stores.rst
> @@ -302,7 +302,7 @@ way QEMU defines the view of memory that a device or
> CPU has.
> or bus fabric.)
>
> Each CPU has an AddressSpace. Some kinds of CPU have more than
> -one AddressSpace (for instance ARM guest CPUs have an AddressSpace
> +one AddressSpace (for instance Arm guest CPUs have an AddressSpace
> for the Secure world and one for NonSecure if they implement TrustZone).
> Devices which can do DMA-type operations should generally have an
> AddressSpace. There is also a "system address space" which typically
> diff --git a/docs/devel/tcg.rst b/docs/devel/tcg.rst
> index 4956a30a4e6..4ebde44b9d7 100644
> --- a/docs/devel/tcg.rst
> +++ b/docs/devel/tcg.rst
> @@ -83,7 +83,7 @@ memory until the end of the translation block. This is
> done for internal
> emulation state that is rarely accessed directly by the program and/or
> changes
> very often throughout the execution of a translation block---this includes
> condition codes on x86, delay slots on SPARC, conditional execution on
> -ARM, and so on. This state is stored for each target instruction, and
> +Arm, and so on. This state is stored for each target instruction, and
> looked up on exceptions.
>
> MMU emulation
> diff --git a/docs/specs/tpm.rst b/docs/specs/tpm.rst
> index da9eb39ca97..5e61238bc5f 100644
> --- a/docs/specs/tpm.rst
> +++ b/docs/specs/tpm.rst
> @@ -25,7 +25,7 @@ QEMU files related to TPM TIS interface:
>
> Both an ISA device and a sysbus device are available. The former is
> used with pc/q35 machine while the latter can be instantiated in the
> -ARM virt machine.
> +Arm virt machine.
>
> CRB interface
> -------------
> @@ -331,7 +331,7 @@ In case a pSeries machine is emulated, use the
> following command line:
> -device
> virtio-blk-pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-disk0
> \
> -drive file=test.img,format=raw,if=none,id=drive-virtio-disk0
>
> -In case an ARM virt machine is emulated, use the following command line:
> +In case an Arm virt machine is emulated, use the following command line:
>
> .. code-block:: console
>
> @@ -346,7 +346,7 @@ In case an ARM virt machine is emulated, use the
> following command line:
> -drive if=pflash,format=raw,file=flash0.img,readonly \
> -drive if=pflash,format=raw,file=flash1.img
>
> - On ARM, ACPI boot with TPM is not yet supported.
> + On Arm, ACPI boot with TPM is not yet supported.
>
> In case SeaBIOS is used as firmware, it should show the TPM menu item
> after entering the menu with 'ESC'.
> diff --git a/docs/system/arm/cpu-features.rst
> b/docs/system/arm/cpu-features.rst
> index 7495b7b672b..2d5c06cd016 100644
> --- a/docs/system/arm/cpu-features.rst
> +++ b/docs/system/arm/cpu-features.rst
> @@ -5,9 +5,9 @@ CPU features are optional features that a CPU of
> supporting type may
> choose to implement or not. In QEMU, optional CPU features have
> corresponding boolean CPU proprieties that, when enabled, indicate
> that the feature is implemented, and, conversely, when disabled,
> -indicate that it is not implemented. An example of an ARM CPU feature
> +indicate that it is not implemented. An example of an Arm CPU feature
> is the Performance Monitoring Unit (PMU). CPU types such as the
> -Cortex-A15 and the Cortex-A57, which respectively implement ARM
> +Cortex-A15 and the Cortex-A57, which respectively implement Arm
> architecture reference manuals ARMv7-A and ARMv8-A, may both optionally
> implement PMUs. For example, if a user wants to use a Cortex-A15 without
> a PMU, then the `-cpu` parameter should contain `pmu=off` on the QEMU
> diff --git a/docs/system/arm/integratorcp.rst
> b/docs/system/arm/integratorcp.rst
> index 3232b43a08b..e6f050f602b 100644
> --- a/docs/system/arm/integratorcp.rst
> +++ b/docs/system/arm/integratorcp.rst
> @@ -1,7 +1,7 @@
> Integrator/CP (``integratorcp``)
> ================================
>
> -The ARM Integrator/CP board is emulated with the following devices:
> +The Arm Integrator/CP board is emulated with the following devices:
>
> - ARM926E, ARM1026E, ARM946E, ARM1136 or Cortex-A8 CPU
>
> diff --git a/docs/system/arm/musicpal.rst b/docs/system/arm/musicpal.rst
> index 35c22212486..9de380edf81 100644
> --- a/docs/system/arm/musicpal.rst
> +++ b/docs/system/arm/musicpal.rst
> @@ -4,7 +4,7 @@ Freecom MusicPal (``musicpal``)
> The Freecom MusicPal internet radio emulation includes the following
> elements:
>
> -- Marvell MV88W8618 ARM core.
> +- Marvell MV88W8618 Arm core.
>
> - 32 MB RAM, 256 KB SRAM, 8 MB flash.
>
> diff --git a/docs/system/arm/nseries.rst b/docs/system/arm/nseries.rst
> index b000b6d13bb..cd9edf5d88b 100644
> --- a/docs/system/arm/nseries.rst
> +++ b/docs/system/arm/nseries.rst
> @@ -4,7 +4,7 @@ Nokia N800 and N810 tablets (``n800``, ``n810``)
> Nokia N800 and N810 internet tablets (known also as RX-34 and RX-44 /
> 48) emulation supports the following elements:
>
> -- Texas Instruments OMAP2420 System-on-chip (ARM 1136 core)
> +- Texas Instruments OMAP2420 System-on-chip (ARM1136 core)
>
> - RAM and non-volatile OneNAND Flash memories
>
> diff --git a/docs/system/arm/palm.rst b/docs/system/arm/palm.rst
> index 0eabf63e0e7..47ff9b36d46 100644
> --- a/docs/system/arm/palm.rst
> +++ b/docs/system/arm/palm.rst
> @@ -4,7 +4,7 @@ Palm Tungsten|E PDA (``cheetah``)
> The Palm Tungsten|E PDA (codename \"Cheetah\") emulation includes the
> following elements:
>
> -- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> +- Texas Instruments OMAP310 System-on-chip (ARM925T core)
>
> - ROM and RAM memories (ROM firmware image can be loaded with
> -option-rom)
> diff --git a/docs/system/arm/realview.rst b/docs/system/arm/realview.rst
> index 8e08eb5da16..65f5be346b1 100644
> --- a/docs/system/arm/realview.rst
> +++ b/docs/system/arm/realview.rst
> @@ -1,7 +1,7 @@
> Arm Realview boards (``realview-eb``, ``realview-eb-mpcore``,
> ``realview-pb-a8``, ``realview-pbx-a9``)
>
> ======================================================================================================
>
> -Several variants of the ARM RealView baseboard are emulated, including
> +Several variants of the Arm RealView baseboard are emulated, including
> the EB, PB-A8 and PBX-A9. Due to interactions with the bootloader, only
> certain Linux kernel configurations work out of the box on these boards.
>
> @@ -14,7 +14,7 @@ The following devices are emulated:
>
> - ARM926E, ARM1136, ARM11MPCore, Cortex-A8 or Cortex-A9 MPCore CPU
>
> -- ARM AMBA Generic/Distributed Interrupt Controller
> +- Arm AMBA Generic/Distributed Interrupt Controller
>
> - Four PL011 UARTs
>
> diff --git a/docs/system/arm/sx1.rst b/docs/system/arm/sx1.rst
> index 321993bc098..8bce30d4b25 100644
> --- a/docs/system/arm/sx1.rst
> +++ b/docs/system/arm/sx1.rst
> @@ -4,7 +4,7 @@ Siemens SX1 (``sx1``, ``sx1-v1``)
> The Siemens SX1 models v1 and v2 (default) basic emulation. The
> emulation includes the following elements:
>
> -- Texas Instruments OMAP310 System-on-chip (ARM 925T core)
> +- Texas Instruments OMAP310 System-on-chip (ARM925T core)
>
> - ROM and RAM memories (ROM firmware image can be loaded with
> -pflash) V1 1 Flash of 16MB and 1 Flash of 8MB V2 1 Flash of 32MB
> diff --git a/docs/system/arm/versatile.rst b/docs/system/arm/versatile.rst
> index 48b6ca0a020..51221c30a48 100644
> --- a/docs/system/arm/versatile.rst
> +++ b/docs/system/arm/versatile.rst
> @@ -1,7 +1,7 @@
> Arm Versatile boards (``versatileab``, ``versatilepb``)
> =======================================================
>
> -The ARM Versatile baseboard is emulated with the following devices:
> +The Arm Versatile baseboard is emulated with the following devices:
>
> - ARM926E, ARM1136 or Cortex-A8 CPU
>
> diff --git a/docs/system/arm/xscale.rst b/docs/system/arm/xscale.rst
> index 19da2eff352..89ec93e904e 100644
> --- a/docs/system/arm/xscale.rst
> +++ b/docs/system/arm/xscale.rst
> @@ -4,7 +4,7 @@ Sharp XScale-based PDA models (``akita``, ``borzoi``,
> ``spitz``, ``terrier``)
> The XScale-based clamshell PDA models (\"Spitz\", \"Akita\", \"Borzoi\"
> and \"Terrier\") emulation includes the following peripherals:
>
> -- Intel PXA270 System-on-chip (ARM V5TE core)
> +- Intel PXA270 System-on-chip (ARMv5TE core)
>
> - NAND Flash memory
>
> diff --git a/docs/user/main.rst b/docs/user/main.rst
> index ca69f7727d5..bd99b0fdbe9 100644
> --- a/docs/user/main.rst
> +++ b/docs/user/main.rst
> @@ -35,7 +35,7 @@ QEMU user space emulation has the following notable
> features:
> On Linux, QEMU can emulate the ``clone`` syscall and create a real
> host thread (with a separate virtual CPU) for each emulated thread.
> Note that not all targets currently emulate atomic operations
> - correctly. x86 and ARM use a global lock in order to preserve their
> + correctly. x86 and Arm use a global lock in order to preserve their
> semantics.
>
> QEMU was conceived so that ultimately it can emulate itself. Although it
> @@ -173,11 +173,11 @@ Other binaries
> user mode (Alpha)
> ``qemu-alpha`` TODO.
>
> -user mode (ARM)
> +user mode (Arm)
> ``qemu-armeb`` TODO.
>
> -user mode (ARM)
> -``qemu-arm`` is also capable of running ARM \"Angel\" semihosted ELF
> +user mode (Arm)
> +``qemu-arm`` is also capable of running Arm \"Angel\" semihosted ELF
> binaries (as implemented by the arm-elf and arm-eabi Newlib/GDB
> configurations), and arm-uclinux bFLT format binaries.
>
> --
> 2.20.1
>
>
--
Niek Linnenbank
[-- Attachment #2: Type: text/html, Size: 18596 bytes --]
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [PATCH 1/5] Makefile: Allow for subdirectories in Sphinx manual dependencies
2020-03-09 21:58 ` [PATCH 1/5] Makefile: Allow for subdirectories in Sphinx manual dependencies Peter Maydell
2020-03-10 14:29 ` Alex Bennée
2020-03-10 20:37 ` Niek Linnenbank
@ 2020-03-11 6:36 ` Richard Henderson
2 siblings, 0 replies; 18+ messages in thread
From: Richard Henderson @ 2020-03-11 6:36 UTC (permalink / raw)
To: Peter Maydell, qemu-arm, qemu-devel; +Cc: Niek Linnenbank
On 3/9/20 2:58 PM, Peter Maydell wrote:
> Currently we put 'docs/foo/*.rst' in the Make list of dependencies
> for the Sphinx 'foo' manual, which means all the files must be
> in the top level of that manual's directory. We'd like to be
> able to have subdirectories inside some of the manuals, so add
> 'docs/foo/*/*.rst' to the dependencies too.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2020-03-11 6:36 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-09 21:58 [PATCH 0/5] docs/system: Split target-arm.rst Peter Maydell
2020-03-09 21:58 ` [PATCH 1/5] Makefile: Allow for subdirectories in Sphinx manual dependencies Peter Maydell
2020-03-10 14:29 ` Alex Bennée
2020-03-10 20:37 ` Niek Linnenbank
2020-03-11 6:36 ` Richard Henderson
2020-03-09 21:58 ` [PATCH 2/5] docs/system: Split target-arm.rst into sub-documents Peter Maydell
2020-03-10 14:29 ` Alex Bennée
2020-03-10 20:53 ` Niek Linnenbank
2020-03-09 21:58 ` [PATCH 3/5] docs/system/target-arm.rst: Add some introductory text Peter Maydell
2020-03-10 14:54 ` Alex Bennée
2020-03-10 20:58 ` Niek Linnenbank
2020-03-09 21:58 ` [PATCH 4/5] docs: Move arm-cpu-features.rst into the system manual Peter Maydell
2020-03-10 14:54 ` Alex Bennée
2020-03-10 21:00 ` Niek Linnenbank
2020-03-09 21:58 ` [PATCH 5/5] docs: Be consistent about capitalization of 'Arm' Peter Maydell
2020-03-10 14:55 ` Alex Bennée
2020-03-10 21:01 ` Niek Linnenbank
2020-03-09 22:45 ` [PATCH 0/5] docs/system: Split target-arm.rst no-reply
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.