From: James Hogan <james.hogan@mips.com>
To: Aleksandar Markovic <Aleksandar.Markovic@imgtec.com>
Cc: Aleksandar Markovic <Aleksandar.Markovic@rt-rk.com>,
Miodrag Dinic <Miodrag.Dinic@imgtec.com>,
Paul Burton <Paul.Burton@imgtec.com>,
"Petar Jovanovic" <Petar.Jovanovic@imgtec.com>,
Raghu Gandham <Raghu.Gandham@imgtec.com>,
Ralf Baechle <ralf@linux-mips.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
Douglas Leung <Douglas.Leung@imgtec.com>,
Goran Ferenc <Goran.Ferenc@imgtec.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Maciej Rozycki <Maciej.Rozycki@imgtec.com>,
Manuel Lauss <manuel.lauss@gmail.com>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>
Subject: Re: [PATCH 1/2] MIPS: math-emu: Update debugfs FP exception stats for certain instructions
Date: Thu, 12 Oct 2017 17:33:30 +0100 [thread overview]
Message-ID: <20171012163330.GG15235@jhogan-linux> (raw)
In-Reply-To: <EF5FA6C3467F85449672C3E735957B85015DA0B589@badag02.ba.imgtec.org>
On Thu, Oct 12, 2017 at 03:54:48PM +0000, Aleksandar Markovic wrote:
> > This patch fixes something, I think it should
> > a) be clear in the commit message what is fixed
> > b) be tagged for stable (though that can always be done
> > retrospectively)
>
> If you agree, I am going to submit v2 of the series, that would fully
> address these concerns.
>
> Additionally, it seems to me that a new round of testing that tests
> involved code paths under various scenarios would be appropriate
> and I am going to do that.
awesome, thanks!
> > Note: thats the one in fpux_emu(), not fpu_emu() which this patch
> > modifies.
>
> Yes, my bad, wanting to respond as quickly as possible, I inserted
> the segment from fpux_emu(), not fpu_emu() as I should have.
>
> By the way, and not related to this patch, I see only 4 (out of 5)
> exceptions are handled in fpux_emu() case (division-by-zero is not
> handled), I presume this is fine (probably division-by-zero not
> needed), isn't it?
Yeh I just spotted that too.
I agree that it only seems to be division instructions (fdiv_op,
frsqrt_op, and frecip_op) that need it, which are all handled in
fpu_emu(), so it should be fine as is.
>
> I truly appreciate your analysis and help.
No problem
Cheers
James
next prev parent reply other threads:[~2017-10-12 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 17:28 [PATCH 0/2] MIPS: Minor FPU emulation fixes Aleksandar Markovic
2017-10-06 17:29 ` [PATCH 1/2] MIPS: math-emu: Update debugfs FP exception stats for certain instructions Aleksandar Markovic
2017-10-09 21:09 ` James Hogan
2017-10-11 16:18 ` Aleksandar Markovic
2017-10-12 10:17 ` James Hogan
2017-10-12 14:32 ` Aleksandar Markovic
[not found] ` <683c-59df7500-1-10d973a0@9889400>
2017-10-12 14:44 ` James Hogan
2017-10-12 15:54 ` Aleksandar Markovic
2017-10-12 16:33 ` James Hogan [this message]
2017-10-06 17:29 ` [PATCH 2/2] MIPS: math-emu: Use preferred flavor of unsigned integer declarations Aleksandar Markovic
2017-10-09 16:59 ` James Hogan
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=20171012163330.GG15235@jhogan-linux \
--to=james.hogan@mips.com \
--cc=Aleksandar.Markovic@imgtec.com \
--cc=Aleksandar.Markovic@rt-rk.com \
--cc=Douglas.Leung@imgtec.com \
--cc=Goran.Ferenc@imgtec.com \
--cc=Maciej.Rozycki@imgtec.com \
--cc=Miodrag.Dinic@imgtec.com \
--cc=Paul.Burton@imgtec.com \
--cc=Petar.Jovanovic@imgtec.com \
--cc=Raghu.Gandham@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=ralf@linux-mips.org \
--cc=yamada.masahiro@socionext.com \
/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