linux-kernel - Re: ILP32 for ARM64 - testing with lmbench

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 5 Dec 2016 14:13:12 +0000
From:   Catalin Marinas <catalin.marinas@....com>
To:     "Zhangjian (Bamvor)" <bamvor.zhangjian@...wei.com>
Cc:     Maxim Kuvyrkov <maxim.kuvyrkov@...aro.org>,
        linux-doc@...r.kernel.org, Szabolcs Nagy <szabolcs.nagy@....com>,
        heiko.carstens@...ibm.com, cmetcalf@...hip.com,
        Yury Norov <ynorov@...iumnetworks.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 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.

> I have also noticed that there are ILP32 failures in glibc testsuite.
> Is it the only blocker for merge ILP32(in technology part)?

It's probably not the only blocker but I have to review the kernel
patches again to make sure. I'd also like to see whether the libc-alpha
community is ok with the glibc counterpart (but don't merge the patches
until the ABI is agreed on both sides).

On performance, I want to make sure there are no regressions on
AArch32/compat and AArch64/LP64.

-- 
Catalin