From: tsnsaito@gmail.com
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>,
qemu-devel@nongnu.org, Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] SPARC64: Implement sparcv9 ldfa/stfa instructions
Date: Fri, 15 Jul 2011 10:55:43 +0900 [thread overview]
Message-ID: <4e1f9e23.9031e70a.4a0d.1b1a@mx.google.com> (raw)
In-Reply-To: <CAAu8pHthfaOZbYrpWuZN9JLyuXtjjj3WwdGjDhoPch=GHNDecQ@mail.gmail.com>
At Thu, 14 Jul 2011 18:31:52 +0300,
Blue Swirl wrote:
> On Thu, Jul 14, 2011 at 12:13 PM, <tsnsaito@gmail.com> wrote:
> > The softmmu version of current implementation is incorrect.
> > Nonfaulting loads should generate exceptions in the same way as
> > normal loads. The CPU hardware should not return zero automatically
> > if no memory mapping exists. The system software is responsible for
> > nonfaulting loads to read zero if no mapping is availale.
> >
> > The differences between nonfaulting loads and normal loads are:
> > - that DSFSR.NF bit is set for nonfaulting loads on MMU faults.
> > - the result of loads on memory region mapped by TTEs with NFO bit set.
>
> I hope this is documented somewhere.
In the UA2007 spec it is partly documented in "9.6 Nonfaulting Load",
but I couldn't find out the description of the SFSR (Synchronous Fault
Status Register) in UA2007...
In the JPS1 spec, the SFSR register is described in F.10.9.
----
Tsuneo Saito <tsnsaito@gmail.com>
prev parent reply other threads:[~2011-07-15 1:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 3:30 [Qemu-devel] [PATCH 0/4] SPARC64: Implement sparcv9 ldfa/stfa instructions Tsuneo Saito
2011-07-13 3:30 ` [Qemu-devel] [PATCH 1/4] SPARC64: Implement ldfa/lddfa/ldqfa instructions properly Tsuneo Saito
2011-07-13 16:27 ` Blue Swirl
2011-07-13 18:02 ` Artyom Tarasenko
2011-07-13 18:19 ` Blue Swirl
2011-07-13 22:56 ` tsnsaito
2011-07-13 3:30 ` [Qemu-devel] [PATCH 2/4] SPARC64: fp_disabled checks on ldfa/lddfa/ldqfa Tsuneo Saito
2011-07-13 3:30 ` [Qemu-devel] [PATCH 3/4] SPARC64: Implement stfa/stdfa/stqfa instrcutions properly Tsuneo Saito
2011-07-13 3:30 ` [Qemu-devel] [PATCH 4/4] SPARC64: fp_disabled checks on stfa/stdfa/stqfa Tsuneo Saito
2011-07-13 8:57 ` [Qemu-devel] [PATCH 0/4] SPARC64: Implement sparcv9 ldfa/stfa instructions Artyom Tarasenko
2011-07-13 11:06 ` tsnsaito
2011-07-13 12:09 ` Mark Cave-Ayland
2011-07-13 12:48 ` tsnsaito
2011-07-13 16:34 ` Blue Swirl
2011-07-14 3:13 ` tsnsaito
2011-07-14 7:38 ` Artyom Tarasenko
2011-07-14 9:13 ` tsnsaito
2011-07-14 15:31 ` Blue Swirl
2011-07-15 1:55 ` tsnsaito [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=4e1f9e23.9031e70a.4a0d.1b1a@mx.google.com \
--to=tsnsaito@gmail.com \
--cc=atar4qemu@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=mark.cave-ayland@siriusit.co.uk \
--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).