From: Paolo Bonzini <pbonzini@redhat.com>
To: Vincent Palatin <vpalatin@chromium.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 2/5] target-i386: Add Intel HAX files
Date: Mon, 14 Nov 2016 12:55:53 +0100 [thread overview]
Message-ID: <bbedc7e4-7aa6-9d62-541c-54d548442694@redhat.com> (raw)
In-Reply-To: <08625798334d3ea3ccead1b40d1068982b40f1d1.1478863621.git.vpalatin@chromium.org>
On 11/11/2016 12:28, Vincent Palatin wrote:
> +
> + memcpy(env->xmm_regs, fpu.mmx_1, sizeof(fpu.mmx_1));
> + memcpy((ZMMReg *) (env->xmm_regs) + 8, fpu.mmx_2, sizeof(fpu.mmx_2));
HAX will only support SSE (128-bit) registers, while env->xmm_regs
supports AVX512 (512-bit) so you have to copy registers one by one.
Is there documentation for HAX? In particular I'm curious as to what
the CPUID information looks like in the guest, and whether there are
ioctls to change it. In particular I would expect XSAVE to be disabled.
Paolo
next prev parent reply other threads:[~2016-11-14 11:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 11:28 [Qemu-devel] [PATCH v2 0/5] [RFC] Add HAX support Vincent Palatin
2016-11-11 11:28 ` [Qemu-devel] [PATCH v2 1/5] kvm: move cpu synchronization code Vincent Palatin
2016-11-11 11:28 ` [Qemu-devel] [PATCH v2 2/5] target-i386: Add Intel HAX files Vincent Palatin
2016-11-14 9:29 ` Stefan Weil
2016-11-14 9:38 ` Vincent Palatin
2016-11-14 10:15 ` Paolo Bonzini
2016-11-14 12:07 ` Vincent Palatin
2016-11-14 11:55 ` Paolo Bonzini [this message]
2016-11-11 11:28 ` [Qemu-devel] [PATCH v2 3/5] hax: remove non UG code Vincent Palatin
2016-11-11 11:28 ` [Qemu-devel] [PATCH v2 4/5] hax: simplify init Vincent Palatin
2016-11-11 11:28 ` [Qemu-devel] [PATCH v2 5/5] Plumb the HAXM-based hardware acceleration support Vincent Palatin
2016-11-14 11:56 ` Paolo Bonzini
2016-11-14 12:09 ` Vincent Palatin
2016-11-13 3:20 ` [Qemu-devel] [PATCH v2 0/5] [RFC] Add HAX support no-reply
2016-11-14 8:21 ` Vincent Palatin
2016-11-14 8:47 ` Paolo Bonzini
2016-11-14 8:55 ` Stefan Weil
2016-11-14 9:28 ` Vincent Palatin
2016-11-14 12:21 ` Stefan Weil
2016-11-14 12:33 ` Vincent Palatin
2016-11-14 12:38 ` Stefan Weil
2016-11-14 12:36 ` Stefan Weil
2016-11-14 13:09 ` Vincent Palatin
2016-11-17 11:09 ` Vincent Palatin
2016-11-18 10:42 ` Vincent Palatin
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=bbedc7e4-7aa6-9d62-541c-54d548442694@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vpalatin@chromium.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).