From: Roman Bolshakov <1759333@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1759333] Re: Illegal Instruction with HVF when encountering SSE instructions in the emulator
Date: Mon, 16 Nov 2020 10:58:19 -0000 [thread overview]
Message-ID: <160552429932.20240.11862361120061267411.malone@soybean.canonical.com> (raw)
In-Reply-To: 152217002978.21179.18362367542097684091.malonedeb@wampee.canonical.com
Thomas, I think the issue is there. SSE/MMX weren't yet added for HVF.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1759333
Title:
Illegal Instruction with HVF when encountering SSE instructions in the
emulator
Status in QEMU:
Incomplete
Bug description:
The latest version of QEMU doesn't seem to support emulated SSE instructions with HVF acceleration on macOS.
The decoder will treat SSE instructions as invalid, get the instruction sizes wrong and quickly crash the guest OS because of illegal instructions.
After having a quick look at target/i386/hvf/x86_decode.c, it seems that SSE instruction emulation isn't implemented in the current version of the x86 emulator.
A way to reproduce the issue is to run a macOS 10.13 guest with HVF
acceleration enabled, this will crash in the guest once it's loading
up the GUI (and also print a "Unimplemented handler" warning from
target/i386/hvf/x86_emu.c).
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1759333/+subscriptions
next prev parent reply other threads:[~2020-11-16 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 17:00 [Qemu-devel] [Bug 1759333] [NEW] Illegal Instruction with HVF when encountering SSE instructions in the emulator Fa Bi
2018-10-24 12:34 ` [Qemu-devel] [Bug 1759333] " Alex Bennée
2018-10-25 13:06 ` Richard Henderson
2020-11-13 16:10 ` Thomas Huth
2020-11-16 10:58 ` Roman Bolshakov [this message]
2020-11-16 18:14 ` Thomas Huth
2021-05-05 8:19 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=160552429932.20240.11862361120061267411.malone@soybean.canonical.com \
--to=1759333@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.