diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:07 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:17 +0200 |
| commit | 9260319e7411ff8281700a532caa436f40120ec4 (patch) | |
| tree | 2f6bfe5f3458dd49d328d3a9eb508595450adec0 /gitlab/issues_text/target_nios2 | |
| parent | 225caa38269323af1bfc2daadff5ec8bd930747f (diff) | |
| download | qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.tar.gz qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.zip | |
gitlab scraper: download in toml and text format
Diffstat (limited to 'gitlab/issues_text/target_nios2')
3 files changed, 31 insertions, 0 deletions
diff --git a/gitlab/issues_text/target_nios2/host_missing/accel_TCG/1258 b/gitlab/issues_text/target_nios2/host_missing/accel_TCG/1258 new file mode 100644 index 000000000..1666a9274 --- /dev/null +++ b/gitlab/issues_text/target_nios2/host_missing/accel_TCG/1258 @@ -0,0 +1 @@ +nios2 system tests are exiting early and not showing an error diff --git a/gitlab/issues_text/target_nios2/host_missing/accel_missing/261 b/gitlab/issues_text/target_nios2/host_missing/accel_missing/261 new file mode 100644 index 000000000..9c3b62ba1 --- /dev/null +++ b/gitlab/issues_text/target_nios2/host_missing/accel_missing/261 @@ -0,0 +1 @@ +broken signal handling in nios2 user-mode emulation diff --git a/gitlab/issues_text/target_nios2/host_s390/accel_missing/1693 b/gitlab/issues_text/target_nios2/host_s390/accel_missing/1693 new file mode 100644 index 000000000..4c6c4aaca --- /dev/null +++ b/gitlab/issues_text/target_nios2/host_s390/accel_missing/1693 @@ -0,0 +1,29 @@ +qemu-system-nios2 not working on s390x (big endian) hosts +Description of problem: +qemu-system-nios2 fails to boot a Linux kernel on s390x hosts. +Steps to reproduce: +1. wget https://qemu-advcal.gitlab.io/qac-best-of-multiarch/download/day14.tar.xz +2. tar -xJf day14.tar.xz +3. cd day14/ +4. qemu-system-nios2 -nographic -kernel vmlinux.elf +Additional information: +When running with "-d in_asm", it seems like the code initially starts executing ok, but in one of the early translation blocks, there is a difference when comparing the log with a run from a x86 host: + +``` +IN: fdt_check_header +0xc81afd48: ldw r3,0(r4) +0xc81afd4c: srli r5,r3,24 +0xc81afd50: slli r2,r3,24 +0xc81afd54: or r2,r2,r5 +0xc81afd58: slli r5,r3,8 +0xc81afd5c: srli r3,r3,8 +0xc81afd60: andhi r5,r5,255 +0xc81afd64: andi r3,r3,65280 +0xc81afd68: or r2,r2,r5 +0xc81afd6c: or r2,r2,r3 +0xc81afd70: movhi r3,53262 +0xc81afd74: addi r3,r3,-275 +0xc81afd78: bne r2,r3,0xc81afde8 +``` + +On the x86 host, the branch at the end is not taken, while on the s390x host, the branch is taken. |