Timeline for Differences between qemu-i386 and Linux IA32 emulation
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 19, 2024 at 0:45 | review | Suggested edits | |||
| Jan 19, 2024 at 8:37 | |||||
| Jan 18, 2024 at 19:44 | history | edited | MC68020 | CC BY-SA 4.0 | added 30 characters in body |
| Jan 18, 2024 at 19:38 | history | edited | MC68020 | CC BY-SA 4.0 | added 702 characters in body |
| Jan 18, 2024 at 14:46 | comment | added | mcendu | IA-32 Linux syscalls are generally done by either int 0x80 or vDSO. SYSENTER is rigged with pitfalls for assembly usage (thanks to vDSO), and SYSCALL is not available for Intel processors outside long (64-bit) mode. | |
| Jan 18, 2024 at 11:55 | comment | added | Stephen Kitt | Oh, duh, I missed the significance of qemu-i386. The ELF “hacking” is very minor, all that happens is that ARCH_DLINFO_IA32 is added and the vDSO is made available. There’s more to the syscall handling than the varying syscall numbers: i386 and x86-64 have different syscall mechanisms (SYSCALL, SYSENTER, interrupt 0x80). | |
| Jan 18, 2024 at 11:28 | history | edited | MC68020 | CC BY-SA 4.0 | added 297 characters in body |
| Jan 18, 2024 at 11:04 | history | answered | MC68020 | CC BY-SA 4.0 |