Quoting Peter Maydell (peter.mayd...@linaro.org): > Doing this only for aarch64 targets seems like a bad idea to me -- this > isn't an aarch64 specific issue. QEMU needs SIGSEGV to go to its own > handler (so we can unprotect pages we've marked as read-only in order to > catch guest writes to them so we can throw away invalidated translated > code), and that's true for all targets. It probably just happens more > often on the aarch64 target than others you've tested because aarch64 > has a signal-return trampoline on the stack frame, so we'll often see > that page get translated and thrown away again. (Other targets with a > trampoline include sparc, cris, openrisc and ppc.)
I see. I've just pushed the customized patch to the archive. We can switch to the original patchset though. But, I'd also like to see what ends up hitting upstream. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1285363 Title: qemu-aarch64-static segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1285363/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
