From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v1] power: don't manage floating point regs when no FPU
Date: Tue, 11 Aug 2020 15:48:07 +0200 [thread overview]
Message-ID: <9edf75a2-103d-ea01-2f53-dbb467047d13@csgroup.eu> (raw)
In-Reply-To: <87o8nh9yjd.fsf@mpe.ellerman.id.au>
Le 11/08/2020 à 14:07, Michael Ellerman a écrit :
> Christophe Leroy <christophe.leroy@csgroup.eu> writes:
>> There is no point in copying floating point regs when there
>> is no FPU and MATH_EMULATION is not selected.
>
> Yeah I guess you're right. I've never touched a system with neither, but
> if such a thing exists then it does seem silly to copy regs around that
> can't be used.
Yes that exists, because glibc implements floating point emulation and
it is definitely more efficient to rely of glibc emulation than kernel one.
>> 10 files changed, 44 insertions(+), 1 deletion(-)
>
> In general this looks fine.
>
> It's a bit #ifdef heavy. Maybe some of those can be cleaned up a bit
> with some wrapper inlines?
>
Yes I'll try and respin, as part of a series I'm preparing to switch the
32 bits signal code to using user_access_begin() logic and
unsafe_put_user() and friends to reduce KUAP unlock/lock.
Christophe
next prev parent reply other threads:[~2020-08-11 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 16:13 [RFC PATCH v1] power: don't manage floating point regs when no FPU Christophe Leroy
2020-08-11 12:07 ` Michael Ellerman
2020-08-11 13:48 ` Christophe Leroy [this message]
2020-08-11 14:06 ` Christophe Leroy
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=9edf75a2-103d-ea01-2f53-dbb467047d13@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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