From: Blue Swirl <blauwirbel@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU testing methodology & results
Date: Sat, 30 Apr 2011 00:35:52 +0300 [thread overview]
Message-ID: <BANLkTiksNE8RguN28DUuRwr52BOPxNiKAQ@mail.gmail.com> (raw)
In-Reply-To: <ipdt5a$cvj$1@dough.gmane.org>
On Fri, Apr 29, 2011 at 11:33 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 04/29/2011 02:17 AM, Peter Maydell wrote:
>>
>> The theoretical aim there as far
>> as I'm concerned is architectural correctness -- in other words we
>> should be a valid implementation of the architecture,
>
> That's not even the case for x86. It should be a goal, however, that with
> mainstream kernels user programs shouldn't be able to see the difference.
> There are some known issues besides bugs, for example the "instruction
> pointer of the last FP instruction" register (!) is not implemented.
For Sparc32 userland, I think the emulator is pretty close to correct
(or at least it could be very precise) since the instruction set is so
simple and there are very few corner cases. Maybe also for Sparc64,
where the set is not so simple anymore.
Still, things like order of exceptions may be tricky to implement
correctly. FPUs in QEMU execute synchronously to integer units.
Another case is that TCG needs to keep TBs and the instructions which
were used to generate the TBs in synch to support PC search (usually
this is needed anyway for example to support SMC on x86), but on Sparc
it should be possible to execute old code from cache while the
instructions have been modified in memory and no barrier instructions
have been issued.
prev parent reply other threads:[~2011-04-29 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 7:18 [Qemu-devel] QEMU testing methodology & results Roberto Paleari
2011-04-08 19:56 ` Blue Swirl
2011-04-10 19:10 ` Roberto Paleari
2011-04-27 14:46 ` Stefan Hajnoczi
2011-04-27 15:31 ` Roberto Paleari
2011-04-28 19:09 ` Blue Swirl
2011-04-28 19:44 ` Anthony Liguori
2011-04-29 0:17 ` Peter Maydell
2011-04-29 8:33 ` Paolo Bonzini
2011-04-29 21:35 ` Blue Swirl [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=BANLkTiksNE8RguN28DUuRwr52BOPxNiKAQ@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).