From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Question about ARM FASTFPE
Date: Wed, 10 Jul 2019 11:46:27 +0100 [thread overview]
Message-ID: <20190710104627.5lam7ipqljks3iji@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAK7LNAT3NDem7_oTyPuDVC7QGY=HuyG-GBE9QQhUuuL_Q=CeNg@mail.gmail.com>
On Wed, Jul 10, 2019 at 07:43:19PM +0900, Masahiro Yamada wrote:
> On Wed, Jul 10, 2019 at 7:02 PM Russell King - ARM Linux admin
> <linux@armlinux.org.uk> wrote:
> >
> > On Wed, Jul 10, 2019 at 06:54:06PM +0900, Masahiro Yamada wrote:
> > > On Wed, Jul 10, 2019 at 5:23 PM Russell King - ARM Linux admin
> > > <linux@armlinux.org.uk> wrote:
> > > >
> > > > On Wed, Jul 10, 2019 at 01:30:24PM +0900, Masahiro Yamada wrote:
> > > > > Hi.
> > > > >
> > > > > I have a question about the following code
> > > > > in arch/arm/Makefile:
> > > > >
> > > > >
> > > > > # Do we have FASTFPE?
> > > > > FASTFPE :=arch/arm/fastfpe
> > > > > ifeq ($(FASTFPE),$(wildcard $(FASTFPE)))
> > > > > FASTFPE_OBJ :=$(FASTFPE)/
> > > > > endif
> > > > >
> > > > >
> > > > > Since arch/arm/fastfpe does not exist in the upstream tree,
> > > > > I guess this is a hook to compile downstream source code.
> > > > >
> > > > > If a user puts arch/arm/fastfpe/ into their local source tree,
> > > > > Kbuild is supposed to compile the files in it.
> > > > >
> > > > > Is this correct?
> > > > >
> > > > >
> > > > > If so, I am afraid this would not work for O= building.
> > > > >
> > > > > $(wildcard ...) checks if this directory exists in the *objtree*,
> > > > > while scripts/Makefile.build needs to include
> > > > > arch/arm/fastfpe/Makefile from *srctree*.
> > > > >
> > > > > I think the correct code should be like follows:
> > > > >
> > > > > # Do we have FASTFPE?
> > > > > FASTFPE :=arch/arm/fastfpe
> > > > > ifneq ($(wildcard $(srctree)/$(FASTFPE)),)
> > > > > FASTFPE_OBJ :=$(FASTFPE)/
> > > > > endif
> > > > >
> > > > >
> > > > > Having said that, I am not sure this code is worth fixing.
> > > > >
> > > > > This code was added around v2.5.1.9,
> > > >
> > > > ... as a _result_ of a discussion and deciding not to upstream it,
> > > > but to still allow its use. Fastfpe is faster than nwfpe (so has
> > > > a definite advantage for FP intensive applications) but we decided
> > > > we didn't want two FP emulation codes in the kernel. However, if
> > > > someone wants to use it, it has to be built into the kernel, it
> > > > can't be modular.
> > >
> > >
> > > IMHO, the entry in Makefile and Kconfig should be removed
> > > from upstream, then moved to a part of the fastfpe local patch.
> >
> > Nope. It means that rather than it being merely a drop-in, it has
> > to be maintained against changes to both these files. Sorry, that's
> > more work.
>
>
> This is the motivation of upstreaming for everybody.
>
> We never know the code that does not exist in upstream.
> Downstream code must pay maintenance cost for ever.
I'm the maintainer of the files in question. I also care-take
fastfpe. It's my choice to make.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-07-10 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 4:30 Question about ARM FASTFPE Masahiro Yamada
2019-07-10 8:23 ` Russell King - ARM Linux admin
2019-07-10 9:54 ` Masahiro Yamada
2019-07-10 10:02 ` Russell King - ARM Linux admin
2019-07-10 10:26 ` Russell King - ARM Linux admin
2019-07-10 10:43 ` Masahiro Yamada
2019-07-10 10:46 ` Russell King - ARM Linux admin [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=20190710104627.5lam7ipqljks3iji@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--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;
as well as URLs for NNTP newsgroup(s).