From: Cui Bixuan <cuibixuan@huawei.com>
To: ltp@lists.linux.it
Subject: [LTP] max_map_count fail in arm64 system which support lib32
Date: Mon, 7 Mar 2016 19:08:40 +0800 [thread overview]
Message-ID: <56DD6138.9060109@huawei.com> (raw)
Hi,
There is an error when run 32-bit 'max_map_count' in arm64 which support lib32:
./max_map_count_32
max_map_count 0 TINFO : set overcommit_memory to 2
max_map_count 0 TINFO : set max_map_count to 64
max_map_count 1 TFAIL : max_map_count.c:233: 64 map entries in total, but expected 64 entries
max_map_count 0 TINFO : set max_map_count to 256
max_map_count 2 TFAIL : max_map_count.c:233: 256 map entries in total, but expected 256 entries
max_map_count 0 TINFO : set max_map_count to 1024
max_map_count 3 TFAIL : max_map_count.c:233: 1024 map entries in total, but expected 1024 entries
max_map_count 0 TINFO : set max_map_count to 4096
max_map_count 4 TFAIL : max_map_count.c:233: 4096 map entries in total, but expected 4096 entries
max_map_count 0 TINFO : set max_map_count to 16384
max_map_count 5 TFAIL : max_map_count.c:233: 16384 map entries in total, but expected 16384 entries
max_map_count 0 TINFO : set max_map_count to 65536
max_map_count 6 TFAIL : max_map_count.c:233: 65536 map entries in total, but expected 65536 entries
max_map_count 0 TINFO : set overcommit_memory to 0
max_map_count 0 TINFO : set max_map_count to 65530
When I use 32-bit SDK, it will compile at:
#elif defined(__arm__)
/* Older arm kernels didn't label their vdso maps */
if (!strncmp(line, "ffff0000-ffff1000", 17))
return true;
and not:
#elif defined(__ia64__)
/* On ia64, the vdso is not a proper mapping */
if (!strcmp(buf, "[vdso]"))
return true;
That will fail in arm64 because of the wrong check; And I have a look at x86 and x86_64, which
have the same check '[vsyscall]';
I think we should fix it but I don't have good idea( I don't know much about it :-( ).
Thanks,
Cui Bixuan
next reply other threads:[~2016-03-07 11:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 11:08 Cui Bixuan [this message]
2016-03-22 10:29 ` [LTP] max_map_count fail in arm64 system which support lib32 Cyril Hrubis
2016-03-22 13:49 ` Cui Bixuan
2016-03-22 14:28 ` Cyril Hrubis
2016-03-23 8:53 ` [LTP] [PATCH] max_map_count: fix error by using runtime check Cui Bixuan
2016-03-23 10:22 ` Jan Stancek
2016-03-23 11:59 ` Cui Bixuan
2016-03-31 12:07 ` Cyril Hrubis
2016-04-05 11:47 ` Cui Bixuan
2016-04-11 17:03 ` Cyril Hrubis
2016-04-12 7:15 ` [LTP] [PATCH v2] " Cui Bixuan
2016-04-12 13:07 ` Cyril Hrubis
2016-03-23 9:00 ` [LTP] max_map_count fail in arm64 system which support lib32 Cui Bixuan
2016-12-16 8:25 ` [LTP] [PATCH] max_map_count: fix a mistake and support it for aarch64_be Cui Bixuan
2016-12-16 10:15 ` [LTP] we can ignore it and discuss the problem at 'Fix wrong checking of aarch64' from the_hoang0709@yahoo.com Cui Bixuan
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=56DD6138.9060109@huawei.com \
--to=cuibixuan@huawei.com \
--cc=ltp@lists.linux.it \
/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