From: Yury Norov <ynorov@caviumnetworks.com> To: Catalin Marinas <catalin.marinas@arm.com> Cc: "Zhangjian (Bamvor)" <bamvor.zhangjian@huawei.com>, Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>, linux-doc@vger.kernel.org, Szabolcs Nagy <szabolcs.nagy@arm.com>, heiko.carstens@de.ibm.com, cmetcalf@ezchip.com, "Dr. Philipp Tomsich" <philipp.tomsich@theobroma-systems.com>, matt.spencer@arm.com, "Joseph S. Myers" <joseph@codesourcery.com>, linux-arch@vger.kernel.org, zhouchengming1@huawei.com, sellcey@caviumnetworks.com, Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>, agraf@suse.de, Geert Uytterhoeven <geert@linux-m68k.org>, Ding Tianhong <dingtianhong@huawei.com>, kilobyte@angband.pl, manuel.montezelo@gmail.com, arnd@arndb.de, Andrew Pinski <pinskia@gmail.com>, linyongting@huawei.com, klimov.linux@gmail.com, broonie@kernel.orglinux-ar Subject: Re: ILP32 for ARM64 - testing with lmbench Date: Sun, 11 Dec 2016 17:38:06 +0530 [thread overview] Message-ID: <20161211120806.GA5973@yury-N73SV> (raw) In-Reply-To: <20161205141312.GC14429@e104818-lin.cambridge.arm.com> 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.
WARNING: multiple messages have this Message-ID (diff)
From: Yury Norov <ynorov@caviumnetworks.com> To: Catalin Marinas <catalin.marinas@arm.com> Cc: "Zhangjian (Bamvor)" <bamvor.zhangjian@huawei.com>, Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>, linux-doc@vger.kernel.org, Szabolcs Nagy <szabolcs.nagy@arm.com>, heiko.carstens@de.ibm.com, cmetcalf@ezchip.com, "Dr. Philipp Tomsich" <philipp.tomsich@theobroma-systems.com>, matt.spencer@arm.com, "Joseph S. Myers" <joseph@codesourcery.com>, linux-arch@vger.kernel.org, zhouchengming1@huawei.com, sellcey@caviumnetworks.com, Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>, agraf@suse.de, Geert Uytterhoeven <geert@linux-m68k.org>, Ding Tianhong <dingtianhong@huawei.com>, kilobyte@angband.pl, manuel.montezelo@gmail.com, arnd@arndb.de, Andrew Pinski <pinskia@gmail.com>, linyongting@huawei.com, klimov.linux@gmail.com, broonie@kernel.org, linux-arm-kernel@lists.infradead.org, GNU C Library <libc-alpha@sourceware.org>, Nathan_Lynch@mentor.com, linux-kernel@vger.kernel.org, hanjun.guo@linaro.org, schwidefsky@de.ibm.com, David Miller <davem@davemloft.net>, christoph.muellner@theobroma-systems.com Subject: Re: ILP32 for ARM64 - testing with lmbench Date: Sun, 11 Dec 2016 17:38:06 +0530 [thread overview] Message-ID: <20161211120806.GA5973@yury-N73SV> (raw) Message-ID: <20161211120806.oTBoWd33XouxljN7V8zCDj-J880AXCak3YKSJG6YBQM@z> (raw) In-Reply-To: <20161205141312.GC14429@e104818-lin.cambridge.arm.com> 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.
next prev parent reply other threads:[~2016-12-11 12:08 UTC|newest] Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-10-21 20:32 [RFC3 nowrap: PATCH v7 00/18] ILP32 for ARM64 Yury Norov 2016-10-21 20:32 ` Yury Norov 2016-10-21 20:33 ` [PATCH 01/18] 32-bit ABI: introduce ARCH_32BIT_OFF_T config option Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-24 16:30 ` Chris Metcalf 2016-10-24 16:30 ` Chris Metcalf 2016-10-24 22:22 ` Arnd Bergmann 2016-10-27 9:29 ` Yury Norov 2016-10-27 9:29 ` Yury Norov 2016-10-21 20:33 ` [PATCH 02/18] arm64: ilp32: add documentation on the ILP32 ABI for ARM64 Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-24 16:36 ` Chris Metcalf 2016-10-24 16:36 ` Chris Metcalf 2016-10-27 9:40 ` Yury Norov 2016-10-27 9:40 ` Yury Norov 2016-10-21 20:33 ` [PATCH 03/18] arm64: rename COMPAT to AARCH32_EL0 in Kconfig Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-21 20:33 ` [PATCH 04/18] arm64: ensure the kernel is compiled for LP64 Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-21 20:33 ` [PATCH 05/18] arm64:uapi: set __BITS_PER_LONG correctly for ILP32 and LP64 Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-21 20:33 ` [PATCH 06/18] thread: move thread bits accessors to separated file Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-21 20:33 ` [PATCH 07/18] arm64: introduce is_a32_task and is_a32_thread (for AArch32 compat) Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-21 20:33 ` [PATCH 08/18] arm64: ilp32: add is_ilp32_compat_{task, thread} and TIF_32BIT_AARCH64 Yury Norov 2016-10-21 20:33 ` [PATCH 08/18] arm64: ilp32: add is_ilp32_compat_{task,thread} " Yury Norov 2016-10-21 20:33 ` [PATCH 09/18] arm64: introduce binfmt_elf32.c Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-12-05 15:10 ` Catalin Marinas 2016-12-14 9:39 ` Yury Norov 2016-12-14 9:39 ` Yury Norov 2016-10-21 20:33 ` [PATCH 10/18] arm64: ilp32: introduce binfmt_ilp32.c Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-12-05 15:38 ` Catalin Marinas 2016-12-05 15:38 ` Catalin Marinas 2016-12-21 18:56 ` Yury Norov 2016-12-21 18:56 ` Yury Norov 2017-01-06 14:48 ` Catalin Marinas 2017-01-06 14:48 ` Catalin Marinas 2016-10-21 20:33 ` [PATCH 11/18] arm64: ilp32: share aarch32 syscall handlers Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-12-05 17:12 ` Catalin Marinas 2016-12-06 7:32 ` Yury Norov 2016-12-06 7:32 ` Yury Norov 2016-10-21 20:33 ` [PATCH 12/18] arm64: ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-21 20:33 ` [PATCH 13/18] arm64: signal: share lp64 signal routines to ilp32 Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-21 20:33 ` [PATCH 14/18] arm64: signal32: move ilp32 and aarch32 common code to separated file Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-12-05 16:18 ` Catalin Marinas 2016-12-05 16:18 ` Catalin Marinas 2016-12-06 9:36 ` Yury Norov 2016-12-06 9:36 ` Yury Norov 2016-10-21 20:33 ` [PATCH 15/18] arm64: ilp32: introduce ilp32-specific handlers for sigframe and ucontext Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-21 20:33 ` [PATCH 16/18] arm64: ptrace: handle ptrace_request differently for aarch32 and ilp32 Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-12-05 16:34 ` Catalin Marinas 2016-12-06 6:25 ` Yury Norov 2016-12-06 6:30 ` Yury Norov 2016-12-06 6:30 ` Yury Norov 2016-12-07 16:59 ` Catalin Marinas 2016-12-07 16:59 ` Catalin Marinas 2016-12-07 20:40 ` Arnd Bergmann 2016-12-07 20:40 ` Arnd Bergmann 2016-12-08 13:12 ` Catalin Marinas 2017-01-05 20:40 ` Yury Norov 2017-01-05 20:40 ` Yury Norov 2017-01-06 14:36 ` Catalin Marinas 2017-01-06 14:36 ` Catalin Marinas 2016-10-21 20:33 ` [PATCH 17/18] arm64:ilp32: add vdso-ilp32 and use for signal return Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-21 20:33 ` [PATCH 18/18] arm64:ilp32: add ARM64_ILP32 to Kconfig Yury Norov 2016-10-21 20:33 ` Yury Norov 2016-10-28 12:46 ` ILP32 for ARM64 - testing with lmbench Yury Norov 2016-11-17 3:28 ` Zhangjian (Bamvor) 2016-11-17 3:28 ` Zhangjian (Bamvor) 2016-11-17 5:02 ` Maxim Kuvyrkov 2016-11-17 5:02 ` Maxim Kuvyrkov 2016-11-17 7:48 ` Zhangjian (Bamvor) 2016-11-17 7:48 ` Zhangjian (Bamvor) 2016-12-05 10:16 ` Zhangjian (Bamvor) 2016-12-05 10:16 ` Zhangjian (Bamvor) 2016-12-05 14:13 ` Catalin Marinas 2016-12-05 14:13 ` Catalin Marinas 2016-12-11 12:08 ` Yury Norov [this message] 2016-12-11 12:08 ` Yury Norov 2016-11-07 8:23 ` ILP32 for ARM64: testing with glibc testsuite Yury Norov 2016-11-07 8:23 ` Yury Norov 2016-11-09 9:56 ` Yury Norov 2016-11-09 9:56 ` Yury Norov 2016-11-16 11:22 ` Maxim Kuvyrkov 2016-11-16 11:22 ` Maxim Kuvyrkov 2016-11-17 15:50 ` Catalin Marinas 2016-11-17 15:50 ` Catalin Marinas 2016-11-17 21:45 ` Steve Ellcey 2016-11-17 21:45 ` Steve Ellcey 2016-12-05 9:58 ` Zhangjian (Bamvor) 2016-12-05 9:58 ` Zhangjian (Bamvor) 2016-12-05 10:07 ` Andreas Schwab 2016-12-05 10:07 ` Andreas Schwab 2016-12-05 10:24 ` Zhangjian (Bamvor) 2016-12-05 10:24 ` Zhangjian (Bamvor) 2016-12-06 5:29 ` Yury Norov 2016-12-06 5:29 ` Yury Norov 2016-12-05 19:33 ` Steve Ellcey 2016-12-05 19:33 ` Steve Ellcey 2016-12-06 8:31 ` Andreas Schwab 2016-12-06 8:31 ` Andreas Schwab 2016-11-30 5:02 ` [RFC3 nowrap: PATCH v7 00/18] ILP32 for ARM64 Yury Norov 2016-11-30 5:02 ` Yury Norov 2016-11-30 6:52 ` Adam Borowski 2016-11-30 6:52 ` Adam Borowski
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=20161211120806.GA5973@yury-N73SV \ --to=ynorov@caviumnetworks.com \ --cc=Prasun.Kapoor@caviumnetworks.com \ --cc=agraf@suse.de \ --cc=arnd@arndb.de \ --cc=bamvor.zhangjian@huawei.com \ --cc=broonie@kernel.orglinux-ar \ --cc=catalin.marinas@arm.com \ --cc=cmetcalf@ezchip.com \ --cc=dingtianhong@huawei.com \ --cc=geert@linux-m68k.org \ --cc=heiko.carstens@de.ibm.com \ --cc=joseph@codesourcery.com \ --cc=kilobyte@angband.pl \ --cc=klimov.linux@gmail.com \ --cc=linux-arch@vger.kernel.org \ --cc=linux-doc@vger.kernel.org \ --cc=linyongting@huawei.com \ --cc=manuel.montezelo@gmail.com \ --cc=matt.spencer@arm.com \ --cc=maxim.kuvyrkov@linaro.org \ --cc=philipp.tomsich@theobroma-systems.com \ --cc=pinskia@gmail.com \ --cc=sellcey@caviumnetworks.com \ --cc=szabolcs.nagy@arm.com \ --cc=zhouchengming1@huawei.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: linkBe 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).