From: Randy Dunlap <rdunlap@infradead.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
kernel test robot <lkp@intel.com>,
Paul Burton <paulburton@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org
Subject: Re: [PATCH] mips: DEC: honor CONFIG_MIPS_FP_SUPPORT=n
Date: Fri, 4 Mar 2022 07:34:44 -0800 [thread overview]
Message-ID: <05328af0-9b08-8de3-e88a-06f67758c197@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2203040857500.47558@angie.orcam.me.uk>
On 3/4/22 01:07, Maciej W. Rozycki wrote:
> On Thu, 3 Mar 2022, Randy Dunlap wrote:
>
>> Include the DECstation interrupt handler in opting out of
>> FPU support.
>>
>> Fixes a linker error:
>>
>> mips-linux-ld: arch/mips/dec/int-handler.o: in function `fpu':
>> (.text+0x148): undefined reference to `handle_fpe_int'
>>
>> Fixes: 183b40f992c8 ("MIPS: Allow FP support to be disabled")
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Reported-by: kernel test robot <lkp@intel.com>
>> Cc: Paul Burton <paulburton@kernel.org>
>> Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
>> Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>
>> Cc: linux-mips@vger.kernel.org
>> ---
>> This builds OK. Is it enough for runtime interrupt handling?
>
> There's:
>
> #ifdef CONFIG_32BIT
> lw t2,cpu_fpu_mask
> #endif
>
> earlier on that needs to go too, and code in arch/mips/dec/setup.c below:
>
> /* Register board interrupts: FPU and cascade. */
>
> (we don't want an unhandled interrupt unmasked). Are you happy to do such
> an update or shall I?
>
> I cannot verify that change at run time, because any program that does FP
> will then crash. Maybe init(8) and sulogin(8) won't. I can check that.
>
> Thanks for doing this stuff!
I'll update the patch and send v2.
thanks.
--
~Randy
prev parent reply other threads:[~2022-03-04 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 1:13 [PATCH] mips: DEC: honor CONFIG_MIPS_FP_SUPPORT=n Randy Dunlap
2022-03-04 9:07 ` Maciej W. Rozycki
2022-03-04 15:34 ` Randy Dunlap [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=05328af0-9b08-8de3-e88a-06f67758c197@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--cc=macro@orcam.me.uk \
--cc=patches@lists.linux.dev \
--cc=paulburton@kernel.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).