Date:   Sun, 11 Dec 2016 17:38:06 +0530
From:   Yury Norov <ynorov@...iumnetworks.com>
To:     Catalin Marinas <catalin.marinas@....com>
CC:     "Zhangjian (Bamvor)" <bamvor.zhangjian@...wei.com>,
        Maxim Kuvyrkov <maxim.kuvyrkov@...aro.org>,
        <linux-doc@...r.kernel.org>, Szabolcs Nagy <szabolcs.nagy@....com>,
        <heiko.carstens@...ibm.com>, <cmetcalf@...hip.com>,
        "Dr. Philipp Tomsich" <philipp.tomsich@...obroma-systems.com>,
        <matt.spencer@....com>,
        "Joseph S. Myers" <joseph@...esourcery.com>,
        <linux-arch@...r.kernel.org>, <zhouchengming1@...wei.com>,
        <sellcey@...iumnetworks.com>,
        Prasun Kapoor <Prasun.Kapoor@...iumnetworks.com>,
        <agraf@...e.de>, Geert Uytterhoeven <geert@...ux-m68k.org>,
        Ding Tianhong <dingtianhong@...wei.com>, <kilobyte@...band.pl>,
        <manuel.montezelo@...il.com>, <arnd@...db.de>,
        Andrew Pinski <pinskia@...il.com>, <linyongting@...wei.com>,
        <klimov.linux@...il.com>, <broonie@...nel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        GNU C Library <libc-alpha@...rceware.org>,
        <Nathan_Lynch@...tor.com>, <linux-kernel@...r.kernel.org>,
        <hanjun.guo@...aro.org>, <schwidefsky@...ibm.com>,
        David Miller <davem@...emloft.net>,
        <christoph.muellner@...obroma-systems.com>
Subject: Re: ILP32 for ARM64 - testing with lmbench

On Mon, Dec 05, 2016 at 02:13:12PM +0000, Catalin Marinas wrote:
> On Mon, Dec 05, 2016 at 06:16:09PM +0800, Zhangjian (Bamvor) wrote:
> > Do you have suggestion of next move of upstreaming ILP32?
> 
> I mentioned the steps a few time before. I'm pasting them again here:
> 
> 1. Complete the review of the Linux patches and ABI (no merge yet)
> 2. Review the corresponding glibc patches (no merge yet)
> 3. Ask (Linaro, Cavium) for toolchain + filesystem (pre-built and more
>    than just busybox) to be able to reproduce the testing in ARM
> 4. More testing (LTP, trinity, performance regressions etc.)
> 5. Move the ILP32 PCS out of beta (based on the results from 4)
> 6. Check the market again to see if anyone still needs ILP32
> 7. Based on 6, decide whether to merge the kernel and glibc patches
> 
> What's not explicitly mentioned in step 4 is glibc testing. Point 5 is
> ARM's responsibility (toolchain folk).
> 
> > There are already the test results of lmbench and specint. Do you they
> > are ok or need more data to prove no regression?
> 
> I would need to reproduce the tests myself, see step 3.

Hi Catalin,

> 3. Ask (Linaro, Cavium) for toolchain + filesystem (pre-built and more
>    than just busybox) to be able to reproduce the testing in ARM

This is the Andrew's toolchain I use to build kernel, GLIBC, binutils etc:
https://drive.google.com/open?id=0B93nHerV55yNVlVKaXpOOHQtbW8
It's not the latest build but it works well to me.

This archive contains 4.9-rc8 kernel, initrd, sys-root, qemu image based on
ilp32 busybox. 
https://drive.google.com/open?id=0B93nHerV55yNbVo0bko0bWlQeFE

I can start linux on qemu and run basic commands and tests in ilp32
mode. This is my first attempt to create rootfs, and this is very basic
busybox + sys-root.  But it lets me start lp64 and ilp32 apps (find
example there). If you need something more, let me know and I'll add
it. You can also use any professional distro with this ilp32-enabled
kernel, just copy sys-root there (like I actually do - I run Ubuntu
14 daily). 

BTW. This is of course good idea to build and test ilp32 user
environment, but in real life I think ilp32 apps will work in lp64
userspace.

> 4. More testing (LTP, trinity, performance regressions etc.)

I also built and ran trinity. After ~24 hours I found all trinity
threads stalled for lp64, and after another 24 hours I found it
running but slower for ilp32. Kernel was alive in both cases. 

Yury.

Powered by blists - more mailing lists