linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v3] MIPS: Implement ieee754 NAN2008 emulation mode
Date: Thu, 11 Jul 2024 09:53:30 +0800	[thread overview]
Message-ID: <a8741e38-837b-4fbb-8656-1e6d50bdfcc0@app.fastmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2407101015120.38148@angie.orcam.me.uk>



在2024年7月10日七月 下午5:21,Maciej W. Rozycki写道:
> On Wed, 10 Jul 2024, Thomas Bogendoerfer wrote:
>
>> > > I'm considering to apply your patch, how much testing/verification did
>> > > this patch see ? Do have some test binaries ?
>> > 
>> > It has been tested against Debian rootfs. There is no need to test againt special binary,
>> > but you need NaN2008 hardware such as Loongson 3A4000.
>> 
>> that's just one case, what about NaN2008 binaries on a legacy MIPS CPU ?
>
>  It would be good to check with hard-float QEMU configured for writable 
> FCSR.NAN2008 (which is one way original code was verified) that things 
> have not regressed.  And also what happens if once our emulation has 
> triggered for the unsupported FCSR.NAN2008 mode, an attempt is made to 
> flip the mode bit via ptrace(2), e.g. under GDB, which I reckon our 
> emulation permits for non-legacy CPUs (and which I think should not be 
> allowed under the new setting).

PTrace is working as expected (reflects emulated value).

The actual switchable NaN hardware (M5150, P5600) uses a dedicated Config7
bit rather than writable FCSR.NAN2008 to control NaN2008 mode. This is undocumented
and not present on some RTL releases. FCSR.NAN2008 is R/O as per The MIPS32 Instruction
Set Manual. This renders the purposed test pointless.

That being said, I'll catch some time later to test behaviour with purposed QEMU modification
but I think it's good to go now. 

Thanks
- Jiaxun

>
>   Maciej

-- 
- Jiaxun

  reply	other threads:[~2024-07-11  1:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  8:38 [PATCH v3] MIPS: Implement ieee754 NAN2008 emulation mode Jiaxun Yang
2024-06-27 10:58 ` Thomas Bogendoerfer
2024-06-27 11:21   ` Jiaxun Yang
2024-06-27 19:54     ` Maciej W. Rozycki
2024-06-28  0:33       ` Jiaxun Yang
2024-07-09  8:55         ` Thomas Bogendoerfer
2024-07-10  5:34           ` Jiaxun Yang
2024-07-10  7:36             ` Thomas Bogendoerfer
2024-07-10  8:16               ` Jiaxun Yang
2024-07-10  9:21               ` Maciej W. Rozycki
2024-07-11  1:53                 ` Jiaxun Yang [this message]
2024-07-11 10:20                   ` Maciej W. Rozycki
2024-07-12  0:36                     ` Jiaxun Yang
2024-07-12 12:22                       ` Maciej W. Rozycki
2024-07-14  3:11                         ` Jiaxun Yang
2024-07-15 12:15                           ` Maciej W. Rozycki
2024-07-15 12:35                             ` Jiaxun Yang
2024-07-15 14:01                               ` Maciej W. Rozycki
2024-07-15 16:38                                 ` YunQiang Su
2024-08-22  8:02                               ` Thomas Bogendoerfer
2024-08-22  9:20                                 ` Jiaxun Yang
2024-07-11  1:47               ` Jiaxun Yang
2024-07-12 11:21 ` Thomas Bogendoerfer

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=a8741e38-837b-4fbb-8656-1e6d50bdfcc0@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=philmd@linaro.org \
    --cc=tsbogend@alpha.franken.de \
    /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).