IRC channel logs

2026-02-17.log

back to list of logs

<matrix_bridge><cosinusoidally> @aggi in terms of riscv emulation there is also https://bellard.org/tinyemu/ . Not sure how complete it is though. It's not had a release for a few years. Is much smaller that qemu.
<aggi>cosinusoidally: intersting
<aggi>digging into documentation https://bellard.org/tinyemu/buildroot.html: gcc7/glibc/linux4|5 is territory i won't step onto myself
<aggi>meanwhile riscv-tcc made signifcant progress, but it probably won't suffice for mentioned kernel versions i think
<aggi>nonetheless i'll try to zip tinyemu into an ebuild here, to compile at least this with tcc to bundle with TinyCC/OS
<aggi>something else i've found: there has been KQEMU for linux-2.4 already ... i'll certainly check this out to test with linux-tcc kernel
<aggi>because with this, TinyCC/OS could become a powerful virtualization host system even, even when that's with qemu-0.14.1 (or earlier) only
<aggi>can't find the linux-2.4 kvm-mod patchset (although it's mentioned online these existed)
<aggi>not important
<aggi>TinyEMU make -> x86_machine.c:50: error: include file 'linux/kvm.h' not found
<aggi>ok, that's linux-2.6 realm if i didn't backport kvm to linux-tcc (besides CLOCK_MONOTONIC on TODO i fear)
<aggi>another option is transitioning to >=linux-2.6 alltogether, but that's almost 10fold the amount of lines of code for kernel again (given fiwix reference with 50000LoC!)
<aggi>and those kernel's Kbuild is different (pre-generated headers from gcc -S needed, maybe too linker-script support all of which locks into llvm/c++ and/or GNU/g++)
<aggi>so, the easiest option would be to backport riscv64 and aarch64 to qemu-0.14.1 (without kvm acceleration) to provide a development emulation host for this
<aggi>i recall a remark from my computer science professor at Telekom more than 20years ago, who objected to the "virtualization" ("cloud") trend at that time already
<aggi>and indeed, virtualization re-shaped entire computer science landscape fundementally
<aggi>the most recent qemu-bundle.tar.gz alone, that is almost 150MiB of sources, plus the toolchain bloat pulled into for g++/c++/c11
<aggi>that's hundreds of millions of lines of code to kickstart some riscv64 and/or aarch64 bootcode development on some emulation host
<aggi>after all, i got bundled tinycc/linux2.4 with qemu-0.14 and this does offer rather many emulation hosts for development already