195801d700
The Big QEMU Lock (BQL) has many names and they are confusing. The actual QemuMutex variable is called qemu_global_mutex but it's commonly referred to as the BQL in discussions and some code comments. The locking APIs, however, are called qemu_mutex_lock_iothread() and qemu_mutex_unlock_iothread(). The "iothread" name is historic and comes from when the main thread was split into into KVM vcpu threads and the "iothread" (now called the main loop thread). I have contributed to the confusion myself by introducing a separate --object iothread, a separate concept unrelated to the BQL. The "iothread" name is no longer appropriate for the BQL. Rename the locking APIs to: - void bql_lock(void) - void bql_unlock(void) - bool bql_locked(void) There are more APIs with "iothread" in their names. Subsequent patches will rename them. There are also comments and documentation that will be updated in later patches. Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: Paul Durrant <paul@xen.org> Acked-by: Fabiano Rosas <farosas@suse.de> Acked-by: David Woodhouse <dwmw@amazon.co.uk> Reviewed-by: Cédric Le Goater <clg@kaod.org> Acked-by: Peter Xu <peterx@redhat.com> Acked-by: Eric Farman <farman@linux.ibm.com> Reviewed-by: Harsh Prateek Bora <harshpb@linux.ibm.com> Acked-by: Hyman Huang <yong.huang@smartx.com> Reviewed-by: Akihiko Odaki <akihiko.odaki@daynix.com> Message-id: 20240102153529.486531-2-stefanha@redhat.com Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> |
||
|---|---|---|
| .. | ||
| tcg | ||
| cpu-csr.h | ||
| cpu-param.h | ||
| cpu-qom.h | ||
| cpu.c | ||
| cpu.h | ||
| disas.c | ||
| gdbstub.c | ||
| helper.h | ||
| insns.decode | ||
| internals.h | ||
| Kconfig | ||
| loongarch-qmp-cmds.c | ||
| machine.c | ||
| meson.build | ||
| README | ||
| translate.h | ||
| vec.h | ||
- Introduction
LoongArch is the general processor architecture of Loongson.
The following versions of the LoongArch core are supported
core: 3A5000
https://github.com/loongson/LoongArch-Documentation/releases/download/2021.08.17/LoongArch-Vol1-v1.00-EN.pdf
We can get the latest loongarch documents at https://github.com/loongson/LoongArch-Documentation/tags.
- System emulation
You can reference docs/system/loongarch/loongson3.rst to get the information about system emulation of LoongArch.
- Linux-user emulation
We already support Linux user emulation. We can use LoongArch cross-tools to build LoongArch executables on X86 machines,
and We can also use qemu-loongarch64 to run LoongArch executables.
1. Config cross-tools env.
see System emulation.
2. Test tests/tcg/multiarch.
./configure --static --prefix=/usr --disable-werror --target-list="loongarch64-linux-user" --enable-debug
cd build
make && make check-tcg
3. Run LoongArch system basic command with loongarch-clfs-system.
- Config clfs env.
wget https://github.com/loongson/build-tools/releases/download/2022.05.29/loongarch64-clfs-system-5.0.tar.bz2
tar -vxf loongarch64-clfs-system-5.0.tar.bz2 -C /opt/clfs
cp /opt/clfs/lib64/ld-linux-loongarch-lp64d.so.1 /lib64
export LD_LIBRARY_PATH="/opt/clfs/lib64"
- Run LoongArch system basic command.
./qemu-loongarch64 /opt/clfs/usr/bin/bash
./qemu-loongarch64 /opt/clfs/usr/bin/ls
./qemu-loongarch64 /opt/clfs/usr/bin/pwd
- Note.
We can get the latest LoongArch documents or LoongArch tools at https://github.com/loongson/