From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexandro Sanchez Bach <alexandro@phi.nz>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target/i386: Fixed CR0.TS check in gen_sse
Date: Wed, 27 Jun 2018 11:30:26 +0200 [thread overview]
Message-ID: <5b03eaea-e611-3e83-8c01-33a17a6b3f8e@redhat.com> (raw)
In-Reply-To: <007a01d3f736$8b5e63f0$a21b2bd0$@phi.nz>
On 29/05/2018 12:19, Alexandro Sanchez Bach wrote:
> The function `gen_sse` assumes all of its instructions require CR0.TS=0.
> However, integer extensions at `0F 38 F[0-F]` and `0F 3A F[0-F]` such as
> CRC32, MOVBE, ADX, BMI1, BMI2 that are handled by `gen_sse` are not supposed
> to throw an exception in this scenario. This causes issues while booting
> some FreeBSD-based guests.
>
> Reported-by: Alexandro Sanchez Bach <alexandro@phi.nz>
> Signed-off-by: Alexandro Sanchez Bach <alexandro@phi.nz>
> Cc: qemu-stable@nongnu.org
> diff --git a/target/i386/translate.c b/target/i386/translate.c
> index 7c21814676..079ab7afef 100644
> --- a/target/i386/translate.c
> +++ b/target/i386/translate.c
> @@ -3049,8 +3049,16 @@ static void gen_sse(CPUX86State *env, DisasContext
> *s, int b,
> is_xmm = 1;
> }
> }
> +
> + modrm = x86_ldub_code(env, s);
> + reg = ((modrm >> 3) & 7);
> + if (is_xmm)
> + reg |= rex_r;
> + mod = (modrm >> 6) & 3;
The problem here is that EMMS and FEMMS instructions do not have a
mod/rm byte. However, this change should apply easily on top of another
patch to move EMMS and FEMMS out of gen_sse.
I'll queue the patch, and wait applying it until I have time to do that
other change (or someone else does it ;)).
Thanks,
Paolo
> /* simple MMX/SSE operation */
> - if (s->flags & HF_TS_MASK) {
> + if (s->flags & HF_TS_MASK
> + && ((b != 0x38 && b != 0x3A) || !(modrm & 0xF0))) {
> gen_exception(s, EXCP07_PREX, pc_start - s->cs_base);
> return;
> }
> @@ -3084,11 +3092,6 @@ static void gen_sse(CPUX86State *env, DisasContext
> *s, int b,
> gen_helper_enter_mmx(cpu_env);
> }
>
> - modrm = x86_ldub_code(env, s);
> - reg = ((modrm >> 3) & 7);
> - if (is_xmm)
> - reg |= rex_r;
> - mod = (modrm >> 6) & 3;
> if (sse_fn_epp == SSE_SPECIAL) {
> b |= (b1 << 8);
> switch(b) {
>
>
>
next prev parent reply other threads:[~2018-06-27 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 10:19 [Qemu-devel] [PATCH] target/i386: Fixed CR0.TS check in gen_sse Alexandro Sanchez Bach
2018-06-27 9:30 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-26 17:39 Alexandro Sanchez Bach
2018-06-26 17:51 ` Peter Maydell
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=5b03eaea-e611-3e83-8c01-33a17a6b3f8e@redhat.com \
--to=pbonzini@redhat.com \
--cc=alexandro@phi.nz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).