From: Bandan Das <bsd@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH 1/2] KVM: x86: emulate fxsave and fxrstor
Date: Wed, 26 Oct 2016 20:17:46 -0400 [thread overview]
Message-ID: <jpgr372abmd.fsf@linux.bootlegged.copy> (raw)
In-Reply-To: <20161026205014.19801-2-rkrcmar@redhat.com> ("Radim \=\?utf-8\?B\?S3LEjW3DocWZIidz\?\= message of "Wed, 26 Oct 2016 22:50:13 +0200")
Hi Radim,
Radim Krčmář <rkrcmar@redhat.com> writes:
...
> static __always_inline int __linearize(struct x86_emulate_ctxt *ctxt,
> @@ -704,7 +708,7 @@ static __always_inline int __linearize(struct x86_emulate_ctxt *ctxt,
> }
> break;
> }
> - if (insn_aligned(ctxt, size) && ((la & (size - 1)) != 0))
> + if (la & (insn_alignment(ctxt, size) - 1))
> return emulate_gp(ctxt, 0);
> return X86EMUL_CONTINUE;
> bad:
> @@ -3856,6 +3860,75 @@ static int em_movsxd(struct x86_emulate_ctxt *ctxt)
> return X86EMUL_CONTINUE;
> }
>
> +static int check_fxsr(struct x86_emulate_ctxt *ctxt)
> +{
> + u32 eax = 1, ebx, ecx = 0, edx;
> +
> + ctxt->ops->get_cpuid(ctxt, &eax, &ebx, &ecx, &edx);
> + if (!(edx & FFL(FXSR)))
> + return emulate_ud(ctxt);
> +
> + if (ctxt->ops->get_cr(ctxt, 0) & (X86_CR0_TS | X86_CR0_EM))
> + return emulate_nm(ctxt);
> +
> + return X86EMUL_CONTINUE;
> +}
> +
> +/*
> + * FXSAVE and FXRSTOR have 3 different formats depending on execution mode,
> + * 1) non-64-bit mode
> + * 2) 64-bit mode with REX.W prefix
> + * 3) 64-bit mode without REX.W prefix
> + *
> + * Emulation uses (3) for for (1) mode because only the number of XMM registers
> + * is different.
> + */
> +static int em_fxsave(struct x86_emulate_ctxt *ctxt)
> +{
> + char fx_state[512] __aligned(16);
> + int rc;
> +
> + rc = check_fxsr(ctxt);
> + if (rc != X86EMUL_CONTINUE)
> + return rc;
> +
> + ctxt->ops->get_fpu(ctxt);
> +#ifdef CONFIG_X86_64
> + if (ctxt->rex_prefix & (1 << 3))
> + asm volatile("fxsave64 %0" : "+m"(fx_state));
> + else
> +#endif
> + asm volatile("fxsave %0" : "+m"(fx_state));
> + ctxt->ops->put_fpu(ctxt);
> +
> + return segmented_write(ctxt, ctxt->memop.addr.mem, fx_state, 512);
> +}
> +
> +static int em_fxrstor(struct x86_emulate_ctxt *ctxt)
> +{
> + char fx_state[512] __aligned(16);
> + int rc;
> +
> + rc = check_fxsr(ctxt);
Is this check enough here ? What I mean is that is it possible that the memory
image that is read from has data in an invalid format/corrupt or is that irrelevant ?
Bandan
> + if (rc != X86EMUL_CONTINUE)
> + return rc;
> +
> + rc = segmented_read(ctxt, ctxt->memop.addr.mem, fx_state, 512);
> + if (rc != X86EMUL_CONTINUE)
> + return rc;
> +
> + ctxt->ops->get_fpu(ctxt);
> +#ifdef CONFIG_X86_64
> + if (ctxt->rex_prefix & (1 << 3))
> + asm volatile("fxrstor64 %0" : "+m"(fx_state));
> + else
> +#endif
> + asm volatile("fxrstor %0" : "+m"(fx_state));
> + ctxt->ops->put_fpu(ctxt);
> +
> + return X86EMUL_CONTINUE;
> +}
> +
> static bool valid_cr(int nr)
> {
> switch (nr) {
> @@ -4208,7 +4281,9 @@ static const struct gprefix pfx_0f_ae_7 = {
> };
>
> static const struct group_dual group15 = { {
> - N, N, N, N, N, N, N, GP(0, &pfx_0f_ae_7),
> + I(ModRM | Aligned16, em_fxsave),
> + I(ModRM | Aligned16, em_fxrstor),
> + N, N, N, N, N, GP(0, &pfx_0f_ae_7),
> }, {
> N, N, N, N, N, N, N, N,
> } };
next prev parent reply other threads:[~2016-10-27 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 20:50 [PATCH 0/2] KVM: x86: emulate fxsave and fxrstor Radim Krčmář
2016-10-26 20:50 ` [PATCH 1/2] " Radim Krčmář
2016-10-27 0:17 ` Bandan Das [this message]
2016-10-27 16:34 ` Radim Krčmář
2016-10-28 3:29 ` Bandan Das
2016-10-26 20:50 ` [PATCH 2/2] KVM: x86: save one bit in ctxt->d Radim Krčmář
2016-10-26 21:40 ` [PATCH 0/2] KVM: x86: emulate fxsave and fxrstor Laszlo Ersek
2016-10-27 16:41 ` Radim Krčmář
2016-10-27 17:01 ` Laszlo Ersek
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=jpgr372abmd.fsf@linux.bootlegged.copy \
--to=bsd@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lersek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
/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).