This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: ILP32 for ARM64 - testing with lmbench
- From: Yury Norov <ynorov at caviumnetworks dot com>
- To: Catalin Marinas <catalin dot marinas at arm dot com>
- Cc: "Zhangjian (Bamvor)" <bamvor dot zhangjian at huawei dot com>, Maxim Kuvyrkov <maxim dot kuvyrkov at linaro dot org>, <linux-doc at vger dot kernel dot org>, Szabolcs Nagy <szabolcs dot nagy at arm dot com>, <heiko dot carstens at de dot ibm dot com>, <cmetcalf at ezchip dot com>, "Dr. Philipp Tomsich" <philipp dot tomsich at theobroma-systems dot com>, <matt dot spencer at arm dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>, <linux-arch at vger dot kernel dot org>, <zhouchengming1 at huawei dot com>, <sellcey at caviumnetworks dot com>, Prasun Kapoor <Prasun dot Kapoor at caviumnetworks dot com>, <agraf at suse dot de>, Geert Uytterhoeven <geert at linux-m68k dot org>, Ding Tianhong <dingtianhong at huawei dot com>, <kilobyte at angband dot pl>, <manuel dot montezelo at gmail dot com>, <arnd at arndb dot de>, Andrew Pinski <pinskia at gmail dot com>, <linyongting at huawei dot com>, <klimov dot linux at gmail dot com>, <broonie at kernel dot org>, <linux-arm-kernel at lists dot infradead dot org>, GNU C Library <libc-alpha at sourceware dot org>, <Nathan_Lynch at mentor dot com>, <linux-kernel at vger dot kernel dot org>, <hanjun dot guo at linaro dot org>, <schwidefsky at de dot ibm dot com>, David Miller <davem at davemloft dot net>, <christoph dot muellner at theobroma-systems dot com>
- Date: Sun, 11 Dec 2016 17:38:06 +0530
- Subject: Re: ILP32 for ARM64 - testing with lmbench
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=Yuri dot Norov at caviumnetworks dot com;
- References: <1477081997-4770-1-git-send-email-ynorov@caviumnetworks.com> <20161028124659.GA24131@yury-N73SV> <cdf5cdf2-43af-6d7f-9e0c-72675fb83224@huawei.com> <266952F2-53F5-4D5E-83F0-6C8203092F67@linaro.org> <120041af-f4e9-5b6f-36dc-7d3535a1f01c@huawei.com> <0adfca97-1624-8eac-8149-da447525ad65@huawei.com> <20161205141312.GC14429@e104818-lin.cambridge.arm.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
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.