From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: Juan Quintela <quintela@trasno.org>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Some comments about recent modifications to target-i386/cpu.h
Date: Mon, 5 Oct 2009 18:54:57 +0200 [thread overview]
Message-ID: <761ea48b0910050954u11bf4b67x96cb91cdccb2b9dd@mail.gmail.com> (raw)
In-Reply-To: <m3ws39g5a7.fsf@neno.mitica>
On Mon, Oct 5, 2009 at 6:43 PM, Juan Quintela <quintela@trasno.org> wrote:
[...]
>> 2. changing fpus and fpuc to uint16_t;
>> this will prevent the use of these fields as global temporaries.
>
> humm, and where/how should I have know this?
> I found that everything that fields where used, they were used as
> uint16_t, obviously I was wrong.
That wasn't meant to be a criticism, just a reminder that some
things which might be good for para-virtualization are not
necessarily good for TCG :-)
But I agree fpus, fpuc can be kept as uint16_t until someone
decide to make TCG know about floating-point.
Laurent
prev parent reply other threads:[~2009-10-05 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 16:14 [Qemu-devel] Some comments about recent modifications to target-i386/cpu.h Laurent Desnogues
[not found] ` <m3ws39g5a7.fsf@neno.mitica>
2009-10-05 16:54 ` Laurent Desnogues [this message]
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=761ea48b0910050954u11bf4b67x96cb91cdccb2b9dd@mail.gmail.com \
--to=laurent.desnogues@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@trasno.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).