docs and tests: assets moved after GitHub account renaming
GitHub setup a permanent redirection for all repositories when accounts, so the old links will keep on working also. However, GitHub allow this username to be reused again. To ensure no one can inject malicious content, I took ownership of the (newly free) pbo-linaro account [1], so no one else can claim it. [1] https://github.com/pbo-linaro Reviewed-by: Cédric Le Goater <clg@redhat.com> Link: https://lore.kernel.org/qemu-devel/20260326214436.256215-1-pierrick.bouvier@linaro.org Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Pierrick Bouvier committed
Mar 26, 2026 at 14:44 UTC
d5a678c87c4d70c1b5ec4397f1daea7ff0186dc8
4 files changed
+20
-20
docs/about/emulation.rst
+14
-14
@@ -898,24 +898,24 @@ As an example, we can trace qemu itself running git::
898
$ uftrace dump --chrome | gzip > ~/qemu_aarch64_git_help.json.gz
899
900
For convenience, you can download this trace `qemu_aarch64_git_help.json.gz
901
-<https://github.com/pbo-linaro/qemu-assets/raw/refs/heads/master/qemu-uftrace/qemu_aarch64_git_help.json.gz>`_.
901
+<https://github.com/p-b-o/qemu-assets/raw/refs/heads/master/qemu-uftrace/qemu_aarch64_git_help.json.gz>`_.
902
Download it and open this trace on https://ui.perfetto.dev/. You can zoom in/out
903
using :kbd:`W`, :kbd:`A`, :kbd:`S`, :kbd:`D` keys.
904
Some sequences taken from this trace:
905
906
- Loading program and its interpreter
907
908
-.. image:: https://github.com/pbo-linaro/qemu-assets/blob/master/qemu-uftrace/loader_exec.png?raw=true
908
+.. image:: https://github.com/p-b-o/qemu-assets/blob/master/qemu-uftrace/loader_exec.png?raw=true
909
:height: 200px
910
911
- open syscall
912
913
-.. image:: https://github.com/pbo-linaro/qemu-assets/blob/master/qemu-uftrace/open_syscall.png?raw=true
913
+.. image:: https://github.com/p-b-o/qemu-assets/blob/master/qemu-uftrace/open_syscall.png?raw=true
914
:height: 200px
915
916
- TB creation
917
918
-.. image:: https://github.com/pbo-linaro/qemu-assets/blob/master/qemu-uftrace/tb_translation.png?raw=true
918
+.. image:: https://github.com/p-b-o/qemu-assets/blob/master/qemu-uftrace/tb_translation.png?raw=true
919
:height: 200px
920
921
It's usually better to use ``uftrace record`` directly. However, tracing
@@ -928,7 +928,7 @@ Example system trace
928
929
A full trace example (chrome trace, from instructions below) generated from a
930
system boot can be found `here
931
-<https://github.com/pbo-linaro/qemu-assets/raw/refs/heads/master/qemu-uftrace/aarch64_boot.json.gz>`_.
931
+<https://github.com/p-b-o/qemu-assets/raw/refs/heads/master/qemu-uftrace/aarch64_boot.json.gz>`_.
932
Download it and open this trace on https://ui.perfetto.dev/. You can see code
933
executed for all privilege levels, and zoom in/out using
934
:kbd:`W`, :kbd:`A`, :kbd:`S`, :kbd:`D` keys. You can find below some sequences
@@ -936,27 +936,27 @@ taken from this trace:
936
937
- Two first stages of boot sequence in Arm Trusted Firmware (EL3 and S-EL1)
938
939
-.. image:: https://github.com/pbo-linaro/qemu-assets/blob/master/qemu-uftrace/bl3_to_bl1.png?raw=true
939
+.. image:: https://github.com/p-b-o/qemu-assets/blob/master/qemu-uftrace/bl3_to_bl1.png?raw=true
940
:height: 200px
941
942
- U-boot initialization (until code relocation, after which we can't track it)
943
944
-.. image:: https://github.com/pbo-linaro/qemu-assets/blob/master/qemu-uftrace/uboot.png?raw=true
944
+.. image:: https://github.com/p-b-o/qemu-assets/blob/master/qemu-uftrace/uboot.png?raw=true
945
:height: 200px
946
947
- Stat and open syscalls in kernel
948
949
-.. image:: https://github.com/pbo-linaro/qemu-assets/blob/master/qemu-uftrace/stat.png?raw=true
949
+.. image:: https://github.com/p-b-o/qemu-assets/blob/master/qemu-uftrace/stat.png?raw=true
950
:height: 200px
951
952
- Timer interrupt
953
954
-.. image:: https://github.com/pbo-linaro/qemu-assets/blob/master/qemu-uftrace/timer_interrupt.png?raw=true
954
+.. image:: https://github.com/p-b-o/qemu-assets/blob/master/qemu-uftrace/timer_interrupt.png?raw=true
955
:height: 200px
956
957
- Poweroff sequence (from kernel back to firmware, NS-EL2 to EL3)
958
959
-.. image:: https://github.com/pbo-linaro/qemu-assets/blob/master/qemu-uftrace/poweroff.png?raw=true
959
+.. image:: https://github.com/p-b-o/qemu-assets/blob/master/qemu-uftrace/poweroff.png?raw=true
960
:height: 200px
961
962
Build and run system example
@@ -966,7 +966,7 @@ Build and run system example
966
967
Building a full system image with frame pointers is not trivial.
968
969
-We provide a `simple way <https://github.com/pbo-linaro/qemu-linux-stack>`_ to
969
+We provide a `simple way <https://github.com/p-b-o/qemu-linux-stack>`_ to
970
build an aarch64 system, combining Arm Trusted firmware, U-boot, Linux kernel
971
and debian userland. It's based on containers (``podman`` only) and
972
``qemu-user-static (binfmt)`` to make sure it's easily reproducible and does not depend
@@ -974,18 +974,18 @@ on machine where you build it.
974
975
You can follow the exact same instructions for a x64 system, combining edk2,
976
Linux, and Ubuntu, simply by switching to
977
-`x86_64 <https://github.com/pbo-linaro/qemu-linux-stack/tree/x86_64>`_ branch.
977
+`x86_64 <https://github.com/p-b-o/qemu-linux-stack/tree/x86_64>`_ branch.
978
979
You can follow the exact same instructions for a riscv64 system, combining
980
opensbi, Linux, and Ubuntu, simply by switching to
981
-`riscv64 <https://github.com/pbo-linaro/qemu-linux-stack/tree/riscv64>`_ branch.
981
+`riscv64 <https://github.com/p-b-o/qemu-linux-stack/tree/riscv64>`_ branch.
982
983
To build and run the system::
984
985
# Install dependencies
986
$ sudo apt install -y podman qemu-user-static
987
988
- $ git clone https://github.com/pbo-linaro/qemu-linux-stack
988
+ $ git clone https://github.com/p-b-o/qemu-linux-stack
989
$ cd qemu-linux-stack
990
$ ./build.sh
991
tests/functional/aarch64/test_device_passthrough.py
+2
-2
@@ -78,14 +78,14 @@ echo device_passthrough_test_ok
78
79
class Aarch64DevicePassthrough(QemuSystemTest):
80
81
- # https://github.com/pbo-linaro/qemu-linux-stack/tree/device_passthrough
81
+ # https://github.com/p-b-o/qemu-linux-stack/tree/device_passthrough
82
# $ ./build.sh && ./archive_artifacts.sh out.tar.xz
83
#
84
# Linux kernel is compiled with defconfig +
85
# IOMMUFD + VFIO_DEVICE_CDEV + ARM_SMMU_V3_IOMMUFD
86
# https://docs.kernel.org/driver-api/vfio.html#vfio-device-cde
87
ASSET_DEVICE_PASSTHROUGH_STACK = Asset(
88
- ('https://github.com/pbo-linaro/qemu-linux-stack/'
88
+ ('https://github.com/p-b-o/qemu-linux-stack/'
89
'releases/download/build/device_passthrough-a9612a2.tar.xz'),
90
'f7d2f70912e7231986e6e293e1a2c4786dd02bec113a7acb6bfc619e96155455')
91
tests/functional/aarch64/test_rme_sbsaref.py
+2
-2
@@ -20,10 +20,10 @@ class Aarch64RMESbsaRefMachine(QemuSystemTest):
20
21
# Stack is inspired from:
22
# https://linaro.atlassian.net/wiki/spaces/QEMU/pages/29051027459/
23
- # https://github.com/pbo-linaro/qemu-linux-stack/tree/rme_sbsa_release
23
+ # https://github.com/p-b-o/qemu-linux-stack/tree/rme_sbsa_release
24
# ./build.sh && ./archive_artifacts.sh out.tar.xz
25
ASSET_RME_STACK_SBSA = Asset(
26
- ('https://github.com/pbo-linaro/qemu-linux-stack/'
26
+ ('https://github.com/p-b-o/qemu-linux-stack/'
27
'releases/download/build/rme_sbsa_release-6a2dfc5.tar.xz'),
28
'5adba482aa069912292a8da746c6b21268224d9d81c97fe7c0bed690579ebdcb')
29
tests/functional/aarch64/test_rme_virt.py
+2
-2
@@ -19,10 +19,10 @@ class Aarch64RMEVirtMachine(QemuSystemTest):
19
20
# Stack is inspired from:
21
# https://linaro.atlassian.net/wiki/spaces/QEMU/pages/29051027459/
22
- # https://github.com/pbo-linaro/qemu-linux-stack/tree/rme_release
22
+ # https://github.com/p-b-o/qemu-linux-stack/tree/rme_release
23
# ./build.sh && ./archive_artifacts.sh out.tar.xz
24
ASSET_RME_STACK_VIRT = Asset(
25
- ('https://github.com/pbo-linaro/qemu-linux-stack/'
25
+ ('https://github.com/p-b-o/qemu-linux-stack/'
26
'releases/download/build/rme_release-56bc99e.tar.xz'),
27
'0e3dc6b8a4b828dbae09c951a40dcb710eded084b32432b50c69cf4173ffa4be')
28