From: "Maciej W. Rozycki" <macro@imgtec.com> To: Fredrik Noring <noring@nocrew.org> Cc: <linux-mips@linux-mips.org> Subject: Re: [PATCH] MIPS: Add basic R5900 support Date: Fri, 15 Sep 2017 19:28:37 +0100 [thread overview] Message-ID: <alpine.DEB.2.00.1709151838530.16752@tp.orcam.me.uk> (raw) In-Reply-To: <20170915131945.GA32582@localhost.localdomain> Hi Fredrik, > > I wonder if FS=1 hardwired also means the Underflow exception cannot > > happen. As the corresponding Cause and Enable bits cannot be set together > > or an FPE exception will happen right away, and the Unimplemented > > Operation exception is uncoditional so we need to leave it out, can you > > please also try these masks in turns: > > > > " li %1,0x0001f07c\n" > > > > and: > > > > " li %1,0x00000f80\n" > > > > This will reveal if any of the Cause, Enable or Flag bits are hardwired. > > The result is: > > FCSR 0x0001f07c old: 01000001, new: 0101c079 > FCSR 0x00000f80 old: 01000001, new: 01000001 This looks unusual and inconsistent in that only V, Z and O Cause bits appear settable, these and also I Flag bits do and no Enable bits do. Given Jürgen's observations in the discussion you referred to below I would expect the I Flag bit not to be settable either; perhaps it's a hardware erratum. > I was looking for information on GCC for R5900 and found > > https://gcc.gnu.org/ml/gcc-patches/2013-01/msg00658.html > > where you and Jürgen Urban discuss this topic. Jürgen cites some FPU details > from the Emotion Engine core user's manual that is very helpful, in addition > to mentioning TX79 differences. Thanks for the reference, I did remember I had the discussion, but didn't recall the details, although I had a vague recollection about instruction encoding differences. Given the situation I think we'll have to stick with full FPU emulation for regular MIPS/Linux user programs, and then possibly have an ELF ABI flag of sorts to mark software requesting running in the R5900 hard-float mode (which obviously won't be able to use standard `libm', etc.); we can think of doing it in a way to keep binary compatibility with exiting PS2 software, should this be a concern. Tasks run in the R5900 hard-float mode would then have our FPU emulator strapped for pass-through operation, i.e. the CpU exception and context switching would work normally, however any FPE exception, given the findings above about FCSR possibly including Unimplemented Operation only, would just throw SIGFPE, letting the userland handle it if desired. You'd need a new `si_code' of course for Unimplemented Operation; or maybe not even that, because as vague as Jürgen's notes are they seem to suggest the R5900 may not actually trap with FPE ever. This also means you only want FPU_CSR_CONDX in `c->fpu_msk31' (for the full FPU emulation) as with an ordinary MIPS III processor. NB, I think the issue with RDHWR emulation to access CP0.UserLocal mentioned in the discussion referred will have to be addressed with the initial submission as well. Maciej
WARNING: multiple messages have this Message-ID (diff)
From: "Maciej W. Rozycki" <macro@imgtec.com> To: Fredrik Noring <noring@nocrew.org> Cc: linux-mips@linux-mips.org Subject: Re: [PATCH] MIPS: Add basic R5900 support Date: Fri, 15 Sep 2017 19:28:37 +0100 [thread overview] Message-ID: <alpine.DEB.2.00.1709151838530.16752@tp.orcam.me.uk> (raw) Message-ID: <20170915182837.5NymY8kwVbwF18ZF72jSsXMfzxrNoJT9y2mXjukaV1E@z> (raw) In-Reply-To: <20170915131945.GA32582@localhost.localdomain> Hi Fredrik, > > I wonder if FS=1 hardwired also means the Underflow exception cannot > > happen. As the corresponding Cause and Enable bits cannot be set together > > or an FPE exception will happen right away, and the Unimplemented > > Operation exception is uncoditional so we need to leave it out, can you > > please also try these masks in turns: > > > > " li %1,0x0001f07c\n" > > > > and: > > > > " li %1,0x00000f80\n" > > > > This will reveal if any of the Cause, Enable or Flag bits are hardwired. > > The result is: > > FCSR 0x0001f07c old: 01000001, new: 0101c079 > FCSR 0x00000f80 old: 01000001, new: 01000001 This looks unusual and inconsistent in that only V, Z and O Cause bits appear settable, these and also I Flag bits do and no Enable bits do. Given Jürgen's observations in the discussion you referred to below I would expect the I Flag bit not to be settable either; perhaps it's a hardware erratum. > I was looking for information on GCC for R5900 and found > > https://gcc.gnu.org/ml/gcc-patches/2013-01/msg00658.html > > where you and Jürgen Urban discuss this topic. Jürgen cites some FPU details > from the Emotion Engine core user's manual that is very helpful, in addition > to mentioning TX79 differences. Thanks for the reference, I did remember I had the discussion, but didn't recall the details, although I had a vague recollection about instruction encoding differences. Given the situation I think we'll have to stick with full FPU emulation for regular MIPS/Linux user programs, and then possibly have an ELF ABI flag of sorts to mark software requesting running in the R5900 hard-float mode (which obviously won't be able to use standard `libm', etc.); we can think of doing it in a way to keep binary compatibility with exiting PS2 software, should this be a concern. Tasks run in the R5900 hard-float mode would then have our FPU emulator strapped for pass-through operation, i.e. the CpU exception and context switching would work normally, however any FPE exception, given the findings above about FCSR possibly including Unimplemented Operation only, would just throw SIGFPE, letting the userland handle it if desired. You'd need a new `si_code' of course for Unimplemented Operation; or maybe not even that, because as vague as Jürgen's notes are they seem to suggest the R5900 may not actually trap with FPE ever. This also means you only want FPU_CSR_CONDX in `c->fpu_msk31' (for the full FPU emulation) as with an ordinary MIPS III processor. NB, I think the issue with RDHWR emulation to access CP0.UserLocal mentioned in the discussion referred will have to be addressed with the initial submission as well. Maciej
next prev parent reply other threads:[~2017-09-15 18:29 UTC|newest] Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-08-27 13:23 [PATCH] MIPS: Add basic R5900 support Fredrik Noring 2017-08-28 13:53 ` Ralf Baechle 2017-08-28 17:11 ` Maciej W. Rozycki 2017-08-29 17:33 ` Fredrik Noring 2017-08-29 17:24 ` Maciej W. Rozycki 2017-08-29 17:24 ` Maciej W. Rozycki 2017-08-30 13:23 ` Fredrik Noring 2017-08-31 15:11 ` Maciej W. Rozycki 2017-08-31 15:11 ` Maciej W. Rozycki 2017-09-02 10:28 ` Fredrik Noring 2017-09-09 10:13 ` Maciej W. Rozycki 2017-09-09 10:13 ` Maciej W. Rozycki 2017-09-11 5:21 ` Maciej W. Rozycki 2017-09-11 5:21 ` Maciej W. Rozycki 2017-09-12 17:59 ` Fredrik Noring 2017-09-15 11:12 ` Maciej W. Rozycki 2017-09-15 11:12 ` Maciej W. Rozycki 2017-09-15 13:19 ` Fredrik Noring 2017-09-15 18:28 ` Maciej W. Rozycki [this message] 2017-09-15 18:28 ` Maciej W. Rozycki 2017-09-02 14:10 ` [PATCH v2] " Fredrik Noring 2017-09-11 5:18 ` Maciej W. Rozycki 2017-09-11 5:18 ` Maciej W. Rozycki 2017-09-11 15:17 ` Fredrik Noring 2017-09-14 13:50 ` Maciej W. Rozycki 2017-09-14 13:50 ` Maciej W. Rozycki 2017-09-16 13:34 ` Fredrik Noring 2017-09-18 17:05 ` Maciej W. Rozycki 2017-09-18 17:05 ` Maciej W. Rozycki 2017-09-18 19:24 ` Fredrik Noring 2017-09-19 12:44 ` Maciej W. Rozycki 2017-09-19 12:44 ` Maciej W. Rozycki 2017-09-20 14:54 ` Fredrik Noring 2017-09-26 11:50 ` Maciej W. Rozycki 2017-09-26 11:50 ` Maciej W. Rozycki 2017-09-27 17:21 ` Fredrik Noring 2017-09-28 12:13 ` Maciej W. Rozycki 2017-09-28 12:13 ` Maciej W. Rozycki 2017-09-30 6:56 ` Fredrik Noring 2017-10-02 9:05 ` Maciej W. Rozycki 2017-10-02 9:05 ` Maciej W. Rozycki 2017-10-02 16:33 ` Fredrik Noring 2017-10-29 17:20 ` Fredrik Noring 2017-11-10 23:34 ` Maciej W. Rozycki 2017-11-10 23:34 ` Maciej W. Rozycki 2017-11-11 16:04 ` Fredrik Noring 2018-01-29 20:27 ` Fredrik Noring 2018-01-31 23:01 ` Maciej W. Rozycki 2018-02-11 7:29 ` [RFC] MIPS: R5900: Workaround for the short loop bug Fredrik Noring 2018-02-12 9:25 ` Maciej W. Rozycki 2018-02-12 15:22 ` Fredrik Noring 2018-02-11 7:46 ` [RFC] MIPS: R5900: Use SYNC.L for data cache and SYNC.P for instruction cache Fredrik Noring 2018-02-11 7:56 ` [RFC] MIPS: R5900: Workaround exception NOP execution bug (FLX05) Fredrik Noring 2018-02-12 9:28 ` Maciej W. Rozycki 2018-02-15 19:15 ` [RFC v2] " Fredrik Noring 2018-02-15 20:49 ` Maciej W. Rozycki 2018-02-17 11:16 ` Fredrik Noring 2018-02-17 11:57 ` Maciej W. Rozycki 2018-02-17 13:38 ` Fredrik Noring 2018-02-17 15:03 ` Maciej W. Rozycki 2018-02-17 20:04 ` Fredrik Noring 2018-02-20 14:09 ` Maciej W. Rozycki 2018-02-22 17:04 ` Fredrik Noring 2018-02-18 8:47 ` Fredrik Noring 2018-02-20 14:41 ` Maciej W. Rozycki 2018-02-22 17:27 ` Fredrik Noring 2018-02-11 8:01 ` [RFC] MIPS: R5900: Workaround for CACHE instruction near branch delay slot Fredrik Noring 2018-02-11 11:16 ` Aw: " "Jürgen Urban" 2018-02-11 8:09 ` [RFC] MIPS: R5900: The ERET instruction has issues with delay slot and CACHE Fredrik Noring 2018-02-11 11:07 ` Aw: " "Jürgen Urban" 2018-02-11 8:29 ` [RFC] MIPS: R5900: Use mandatory SYNC.L in exception handlers Fredrik Noring 2018-02-11 10:33 ` Aw: " "Jürgen Urban" 2018-02-12 9:22 ` Maciej W. Rozycki 2018-02-12 9:22 ` Maciej W. Rozycki 2018-02-18 10:30 ` Fredrik Noring 2018-02-17 14:43 ` [RFC] MIPS: R5900: Workaround for saving and restoring FPU registers Fredrik Noring 2018-02-17 15:18 ` Maciej W. Rozycki 2018-02-17 17:47 ` Fredrik Noring 2018-02-17 19:33 ` Maciej W. Rozycki 2018-02-18 9:26 ` [RFC] MIPS: R5900: Workaround where MSB must be 0 for the instruction cache Fredrik Noring 2018-02-18 11:08 ` [RFC] MIPS: R5900: Add mandatory SYNC.P to all M[FT]C0 instructions Fredrik Noring 2018-03-03 12:26 ` [RFC] MIPS: PS2: Interrupt request (IRQ) support Fredrik Noring 2018-03-03 13:09 ` Maciej W. Rozycki 2018-03-03 14:14 ` Fredrik Noring 2018-04-09 15:51 ` Fredrik Noring 2018-03-18 10:45 ` Fredrik Noring 2018-03-19 19:15 ` Thomas Gleixner 2018-06-18 18:52 ` [RFC v2] " Fredrik Noring 2017-10-30 17:55 ` [PATCH v2] MIPS: Add basic R5900 support Fredrik Noring 2017-11-24 10:26 ` Maciej W. Rozycki 2017-11-24 10:26 ` Maciej W. Rozycki 2017-11-24 10:39 ` Maciej W. Rozycki 2017-11-24 10:39 ` Maciej W. Rozycki 2017-09-20 14:07 ` Fredrik Noring 2017-09-21 21:07 ` Maciej W. Rozycki 2017-09-21 21:07 ` Maciej W. Rozycki 2017-09-22 16:37 ` Fredrik Noring 2017-09-22 16:37 ` Fredrik Noring 2017-09-29 23:55 ` Maciej W. Rozycki 2017-09-29 23:55 ` Maciej W. Rozycki 2017-09-30 18:26 ` Fredrik Noring 2017-10-02 9:11 ` Maciej W. Rozycki 2017-10-02 9:11 ` Maciej W. Rozycki 2017-10-03 19:49 ` Fredrik Noring 2017-10-05 19:04 ` Fredrik Noring 2017-10-06 20:28 ` Fredrik Noring 2017-10-15 16:39 ` Fredrik Noring 2017-10-17 12:23 ` Maciej W. Rozycki 2017-10-17 12:23 ` Maciej W. Rozycki 2017-10-21 18:00 ` Fredrik Noring 2017-10-23 16:10 ` Maciej W. Rozycki 2017-10-23 16:10 ` Maciej W. Rozycki 2017-09-21 18:11 ` Paul Burton 2017-09-21 18:11 ` Paul Burton 2017-09-21 19:48 ` Maciej W. Rozycki 2017-09-21 19:48 ` Maciej W. Rozycki 2017-10-29 18:42 ` Fredrik Noring
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=alpine.DEB.2.00.1709151838530.16752@tp.orcam.me.uk \ --to=macro@imgtec.com \ --cc=linux-mips@linux-mips.org \ --cc=noring@nocrew.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: linkBe 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.