From: zhaogongyi via ltp <ltp@lists.linux.it>
To: Li Wang <liwang@redhat.com>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] max_map_count: Delete dead code
Date: Mon, 29 Nov 2021 07:25:34 +0000 [thread overview]
Message-ID: <a47193579c6e4c138e10d1047c399dec@huawei.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1595 bytes --]
Hi,
In my test system, the __arm__ is not defined, elf head like:
ELF Header:
Magic: 7f 45 4c 46 01 02 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, big endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: DYN (Shared object file)
Machine: AArch64
Version: 0x1
Entry point address: 0x490
Start of program headers: 52 (bytes into file)
Start of section headers: 10012 (bytes into file)
Flags: 0x0
Size of this header: 52 (bytes)
Size of program headers: 32 (bytes)
Number of program headers: 9
Size of section headers: 40 (bytes)
Number of section headers: 36
Section header string table index: 35
But for other arm32 platform, the code may be usefull since i have not an older kernel version can run on arm64.
Thanks,
Gongyi
Hi Gongyi,
On Mon, Nov 29, 2021 at 11:56 AM Zhao Gongyi via ltp <ltp@lists.linux.it<mailto:ltp@lists.linux.it>> wrote:
When we run the testcase on AARCH64, there are no TST_ARM defined.
We thought there is a possible 32bit ARM binary runs on 64bit aarch64 kernel.
https://lists.linux.it/pipermail/ltp/2021-November/026038.html
Or, what's your test scenarios, did you build and test that?
--
Regards,
Li Wang
[-- Attachment #1.2: Type: text/html, Size: 11364 bytes --]
[-- Attachment #2: Type: text/plain, Size: 60 bytes --]
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2021-11-29 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 7:25 zhaogongyi via ltp [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-29 3:57 [LTP] [PATCH] max_map_count: Delete dead code Zhao Gongyi via ltp
2021-11-29 5:47 ` Li Wang
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=a47193579c6e4c138e10d1047c399dec@huawei.com \
--to=ltp@lists.linux.it \
--cc=liwang@redhat.com \
--cc=zhaogongyi@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: 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