From: ynorov@caviumnetworks.com (Yury Norov)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC5 PATCH v6 00/21] ILP32 for ARM64
Date: Fri, 19 Feb 2016 01:35:06 +0300 [thread overview]
Message-ID: <20160218223506.GA7816@yury-N73SV> (raw)
In-Reply-To: <56AC38F1.2030608@huawei.com>
On Sat, Jan 30, 2016 at 12:15:45PM +0800, Zhangjian (Bamvor) wrote:
> Hi, Yury
>
> On 1:09 2016/1/30, Yury Norov wrote:
> >On Fri, Jan 29, 2016 at 05:59:33PM +0800, Zhangjian (Bamvor) wrote:
> >>Hi,
> >>
> >>On 1:22 2016/1/15, Yury Norov wrote:
> >>>This is still RFC because we have no glibc yet, that correspnds new ABI
> >>>introduced here. And so we cannot run tests. LP64 and AARCH32 tests show
> >>>no regression though.
> >>Hi,
> >>
> >>Glad to see this version. I hope I could test it. Where could I find the
> >>corresponding glibc? I could not find it in
> >>http://github.com/norov/glibc.git. Or is there a plan to do it?
> >>
> >>Besides compat wrappers discussed in these series, is there any other
> >>blockers for upstream? I would suppose everyone is intestested in the
> >>result of LTP...
> >>
> >>Regards
> >>
> >>Bamvor
> >>
> >
> >Hi, Bamvor,
> >
> >Just to order all commits, I created new ILP32 branch at [1], that
> >based on 4.4 kernel + [2] + [3]. There's no new glibc suitable for
> >rfc5. But I started with it, and I hope there will be progress soon.
> Cool:)
> >
> >You cannot run LTP as there are some syscalls that are called during
> >dynamic loading that fail, but you can try to build your test statically
> >agaginst current glibc, and there's a big chance it will work.
> >I have a set of 'hello-worlds' working that way.
> Currrently, I got 300+ in ltplite with you glibc[1]. I will try static link
> later.
> >
> >If you have some specific test that you cannot run, you can send it to
> >me, and I will take a look on it.
> Sure, I am reading the test results. Hope we could fix these failure
> together.
>
> Regards
>
> Bamvor
>
> [1] https://github.com/norov/glibc/tree/thunderx-ilp32-32time_toff_t
> >
> >Yury
> >
> >[1] https://github.com/norov/linux/tree/rfc5
> >[2] http://permalink.gmane.org/gmane.linux.kernel/2116021
> >[3] http://comments.gmane.org/gmane.linux.kernel/2134747
> >
> >>>
> >>> v3: https://lkml.org/lkml/2014/9/3/704
> >>> v4: https://lkml.org/lkml/2015/4/13/691
> >>> v5: https://lkml.org/lkml/2015/9/29/911
> >>>
Hi Bamvor, everybody,
I have new glibc that follows new ABI:
https://github.com/norov/glibc/tree/new-api
It's very draft and dirty, but you can try it with RFC5.
My fail list for ltplite looks like this:
pipeio_4 FAIL 11
abort01 FAIL 2
clone02 FAIL 4
kill10 FAIL 2
kill11 FAIL 2
lstat01A FAIL 1
lstat02 FAIL 1
mmap16 FAIL 6
nanosleep03 FAIL 1
nftw01 FAIL 1
nftw6401 FAIL 1
open12 FAIL 2
pathconf01 FAIL 1
pipe07 FAIL 2
profil01 FAIL 11
readdir01 FAIL 1
readlink01A FAIL 1
rename11 FAIL 2
rmdir02 FAIL 2
sigaltstack01 FAIL 1
sigaltstack02 FAIL 1
stat03 FAIL 1
stat04 FAIL 1
stat06 FAIL 1
umount2_01 FAIL 2
umount2_02 FAIL 2
umount2_03 FAIL 2
utime06 FAIL 2
writev01 FAIL 1
mtest06 FAIL 11
rwtest01 FAIL 2
rwtest02 FAIL 2
rwtest03 FAIL 2
rwtest04 FAIL 2
rwtest05 FAIL 2
Float tests are exluded, but also fail. Totally, ~40 of 787 tests
fail.
Yury
next prev parent reply other threads:[~2016-02-18 22:35 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 17:22 [RFC5 PATCH v6 00/21] ILP32 for ARM64 Yury Norov
2016-01-14 17:22 ` [PATCH v6 01/21] arm64: ilp32: add documentation on the ILP32 ABI " Yury Norov
2016-01-14 17:22 ` [PATCH v6 02/21] arm64: ensure the kernel is compiled for LP64 Yury Norov
2016-01-14 17:23 ` [PATCH v6 03/21] arm64: rename COMPAT to AARCH32_EL0 in Kconfig Yury Norov
2016-01-14 17:23 ` [PATCH v6 04/21] arm64: change some CONFIG_COMPAT over to use CONFIG_AARCH32_EL0 instead Yury Norov
2016-01-14 17:23 ` [PATCH v6 05/21] arm64: compat: change config dependences to aarch32 Yury Norov
2016-01-14 17:23 ` [PATCH v6 06/21] arm64:uapi: set __BITS_PER_LONG correctly for ILP32 and LP64 Yury Norov
2016-01-14 17:23 ` [PATCH v6 07/21] thread: move thread bits accessors to separated file Yury Norov
2016-01-14 17:23 ` [PATCH v6 08/21] arm64: introduce is_a32_task and is_a32_thread (for AArch32 compat) Yury Norov
2016-01-14 17:23 ` [PATCH v6 09/21] arm64: ilp32: add is_ilp32_compat_{task, thread} and TIF_32BIT_AARCH64 Yury Norov
2016-01-14 17:23 ` [PATCH v6 10/21] arm64: introduce binfmt_elf32.c Yury Norov
2016-01-14 17:23 ` [PATCH v6 11/21] arm64: ilp32: introduce binfmt_ilp32.c Yury Norov
2016-01-14 17:23 ` [PATCH v6 12/21] arm64: ptrace: handle ptrace_request differently for aarch32 and ilp32 Yury Norov
2016-01-14 17:23 ` [PATCH v6 13/21] arm64:ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it Yury Norov
2016-01-14 17:23 ` [PATCH v6 14/21] arm64: signal: wrap struct ucontext, fp and lr with struct sigframe Yury Norov
2016-01-14 17:23 ` [PATCH v6 15/21] arm64: signal: share lp64 signal routines to ilp32 Yury Norov
2016-01-14 17:23 ` [PATCH v6 16/21] arm64: signal32: move ilp32 and aarch32 common code to separated file Yury Norov
2016-01-14 17:23 ` [PATCH v6 17/21] arm64: ilp32: introduce ilp32-specific handlers for sigframe Yury Norov
2016-02-29 8:27 ` Andreas Schwab
2016-01-14 17:23 ` [PATCH v6 18/21] arm64:ilp32: add vdso-ilp32 and use for signal return Yury Norov
2016-01-14 17:23 ` [PATCH v6 19/21] arm64:ilp32: add ARM64_ILP32 to Kconfig Yury Norov
2016-01-14 17:23 ` [PATCH v6 20/21] all: s390: make compat wrappers the generic solution Yury Norov
2016-01-14 18:11 ` Yury Norov
2016-01-15 12:46 ` Heiko Carstens
[not found] ` <20160119175223.GA6603@yury-N73SV>
2016-01-20 8:16 ` Heiko Carstens
2016-01-20 12:17 ` Yury Norov
2016-01-14 17:23 ` [PATCH v6 21/21] arm64: ilp32: wrap syscalls to remove top 32-bit vulnerability Yury Norov
2016-01-18 13:18 ` [RFC5 PATCH v6 00/21] ILP32 for ARM64 Zhangjian (Bamvor)
2016-01-18 13:26 ` Andreas Schwab
2016-01-18 13:41 ` Bamvor Zhang Jian
2016-01-29 9:59 ` Zhangjian (Bamvor)
2016-01-29 17:09 ` Yury Norov
2016-01-30 4:15 ` Zhangjian (Bamvor)
2016-02-18 22:35 ` Yury Norov [this message]
2016-02-19 8:23 ` Arnd Bergmann
2016-02-19 12:59 ` Yury Norov
2016-02-19 14:06 ` Arnd Bergmann
2016-02-29 15:39 ` Yury Norov
2016-02-29 16:00 ` Andreas Schwab
2016-02-29 16:30 ` Arnd Bergmann
2016-02-25 10:50 ` Andreas Schwab
2016-02-25 20:28 ` Yury Norov
2016-03-18 10:28 ` Zhangjian (Bamvor)
2016-03-18 15:49 ` Yury Norov
2016-03-18 15:55 ` Alexander Graf
2016-03-18 16:46 ` Yury Norov
2016-03-20 8:12 ` Zhangjian (Bamvor)
2016-03-21 11:23 ` Zhangjian (Bamvor)
2016-03-21 18:43 ` Yury Norov
2016-03-22 1:49 ` Yury Norov
2016-03-21 9:07 ` Andreas Schwab
2016-03-21 9:43 ` Arnd Bergmann
2016-03-21 10:52 ` Andreas Schwab
2016-03-21 17:02 ` Arnd Bergmann
2016-03-26 12:36 ` Zhangjian (Bamvor)
2016-03-29 10:58 ` Arnd Bergmann
2016-03-29 12:01 ` Yury Norov
2016-03-29 12:42 ` Arnd Bergmann
2016-03-29 13:21 ` Zhangjian (Bamvor)
2016-03-29 13:27 ` Arnd Bergmann
2016-03-29 15:54 ` Joseph Myers
2016-03-29 19:30 ` Arnd Bergmann
2016-03-29 20:15 ` Joseph Myers
2016-03-29 20:24 ` Arnd Bergmann
2016-03-29 21:00 ` Joseph Myers
2016-03-29 21:39 ` Arnd Bergmann
2016-03-31 7:35 ` Zhangjian (Bamvor)
2016-03-21 18:40 ` Yury Norov
2016-03-26 13:08 ` Zhangjian (Bamvor)
2016-03-26 13:45 ` Zhangjian (Bamvor)
2016-03-26 22:46 ` Yury Norov
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=20160218223506.GA7816@yury-N73SV \
--to=ynorov@caviumnetworks.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).