From: Paolo Bonzini <pbonzini@redhat.com>
To: asia@lastline.com, qemu-devel@nongnu.org
Cc: ehabkost@redhat.com, A Slowinska <asia.slowinska@gmail.com>,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] target-i386/kvm.c: Fix the order of FPU registers in xsave
Date: Wed, 10 Feb 2016 15:17:24 +0100 [thread overview]
Message-ID: <56BB4674.3050903@redhat.com> (raw)
In-Reply-To: <CAP-0pEZnJUDiTf+8AYvscuWVT29OZ6ZtpM3A+ZN+LhefdvSP_w@mail.gmail.com>
On 10/02/2016 12:02, Asia Slowinska wrote:
> Stick to the expected order of the FPU registers in xsave (as specified
> in the
> Intel manual.) Otherwise, instructions loading the FPU state don't set
> it up
> correctly.
>
> To set up FPU, software needs to provide a buffer of 80 bytes
> storing 8 FPU registers. They are organized in a stack. FPU assumes that the
> first field of the buffer is ST0, then ST1, and so on. QEMU maintains a
> circular buffer. When preparing these 80 bytes for KVM, QEMU just uses
> memcpy
> instead of copying the elements in a proper order.
>
> Signed-off-by: Asia Slowinska <asia@lastline.com <mailto:asia@lastline.com>>
> ---
> target-i386/kvm.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/target-i386/kvm.c b/target-i386/kvm.c
> index 94024bc..c77fe73 100644
> --- a/target-i386/kvm.c
> +++ b/target-i386/kvm.c
> @@ -1325,8 +1325,10 @@ static int kvm_put_xsave(X86CPU *cpu)
> xsave->region[XSAVE_FTW_FOP] = (uint32_t)(env->fpop << 16) + twd;
> memcpy(&xsave->region[XSAVE_CWD_RIP], &env->fpip, sizeof(env->fpip));
> memcpy(&xsave->region[XSAVE_CWD_RDP], &env->fpdp, sizeof(env->fpdp));
> - memcpy(&xsave->region[XSAVE_ST_SPACE], env->fpregs,
> - sizeof env->fpregs);
> + for (i = 0; i < 8; i++) {
> + memcpy(&xsave_region[HXSAVE_ST_SPACE + i * 4],
> + &env->fpregs[(env->fpstt + i) & 7], 16);
> + }
> xsave->region[XSAVE_MXCSR] = env->mxcsr;
> *(uint64_t *)&xsave->region[XSAVE_XSTATE_BV] = env->xstate_bv;
> memcpy(&xsave->region[XSAVE_BNDREGS], env->bnd_regs,
> @@ -1745,8 +1747,10 @@ static int kvm_get_xsave(X86CPU *cpu)
> memcpy(&env->fpip, &xsave->region[XSAVE_CWD_RIP], sizeof(env->fpip));
> memcpy(&env->fpdp, &xsave->region[XSAVE_CWD_RDP], sizeof(env->fpdp));
> env->mxcsr = xsave->region[XSAVE_MXCSR];
> - memcpy(env->fpregs, &xsave->region[XSAVE_ST_SPACE],
> - sizeof env->fpregs);
> + for (i = 0; i < 8; i++) {
> + memcpy(&env->fpregs[(env->fpstt + i) & 7],
> + &xsave_region[HXSAVE_ST_SPACE + i * 4], 16);
Hi, the patch is missing a definition of HXSAVE_ST_SPACE.
Thanks,
Paolo
> + }
> env->xstate_bv = *(uint64_t *)&xsave->region[XSAVE_XSTATE_BV];
> memcpy(env->bnd_regs, &xsave->region[XSAVE_BNDREGS],
> sizeof env->bnd_regs);
> --
> 1.9.1
>
>
next prev parent reply other threads:[~2016-02-10 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 11:02 [Qemu-devel] [PATCH] target-i386/kvm.c: Fix the order of FPU registers in xsave Asia Slowinska
2016-02-10 14:17 ` Paolo Bonzini [this message]
2016-02-10 14:39 ` Asia Slowinska
2016-02-12 20:20 ` Eduardo Habkost
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=56BB4674.3050903@redhat.com \
--to=pbonzini@redhat.com \
--cc=asia.slowinska@gmail.com \
--cc=asia@lastline.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).