From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] libxc: create an initial FPU state for HVM guests
Date: Tue, 13 Oct 2015 18:18:57 +0200 [thread overview]
Message-ID: <561D2EF1.4090501@citrix.com> (raw)
In-Reply-To: <561D34C602000078000AAA71@prv-mh.provo.novell.com>
El 13/10/15 a les 16.43, Jan Beulich ha escrit:
>>>> On 13.10.15 at 15:32, <roger.pau@citrix.com> wrote:
>> --- a/tools/libxc/xc_dom_x86.c
>> +++ b/tools/libxc/xc_dom_x86.c
>> @@ -841,6 +841,23 @@ static int vcpu_hvm(struct xc_dom_image *dom)
>> struct hvm_save_descriptor end_d;
>> HVM_SAVE_TYPE(END) end;
>> } bsp_ctx;
>> + struct {
>> + uint16_t fcw;
>> + uint16_t fsw;
>> + uint8_t ftw;
>> + uint8_t rsvd1;
>> + uint16_t fop;
>> + union {
>> + uint64_t addr;
>> + struct {
>> + uint32_t offs;
>> + uint16_t sel;
>> + uint16_t rsvd;
>> + };
>> + } fip, fdp;
>> + uint32_t mxcsr;
>> + uint32_t mxcsr_mask;
>> + } *fpu_ctxt;
>
> I think a comment should be added here that this layout is the 64-bit
> one, no matter what bitness the tool stack. Or perhaps leave out all
> pieces that you don't need; the ones you care about live at the same
> offsets in both 32- and 64-bit variants.
The layout of this structure is exactly the same for 32 and 64bits, I'm
going to add a comment stating this.
Roger.
next prev parent reply other threads:[~2015-10-13 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 13:32 [PATCH] libxc: create an initial FPU state for HVM guests Roger Pau Monne
2015-10-13 13:36 ` Andrew Cooper
2015-10-13 13:42 ` Ian Campbell
2015-10-13 16:17 ` Roger Pau Monné
2015-10-13 14:43 ` Jan Beulich
2015-10-13 16:18 ` Roger Pau Monné [this message]
2015-10-14 9:52 ` Jan Beulich
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=561D2EF1.4090501@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.