From: Jan Stancek <jstancek@redhat.com>
To: Zhao Gongyi <zhaogongyi@huawei.com>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] lapi/syscalls: Add epoll_create for aarch64.in
Date: Tue, 26 Oct 2021 14:30:37 +0200 [thread overview]
Message-ID: <CAASaF6yWxgM5M0L23k64GkDLBoahxi8-4-zao+yJD0NjtMn9HA@mail.gmail.com> (raw)
In-Reply-To: <20211026075025.29117-1-zhaogongyi@huawei.com>
On Tue, Oct 26, 2021 at 9:49 AM Zhao Gongyi <zhaogongyi@huawei.com> wrote:
>
> Add epoll_create for aarch64.in and modify the value of epoll_ctl
> for aarch64.in. Otherwise, the testcase epoll_create01/epoll_create02 will
> fail.
>
> Signed-off-by: Zhao Gongyi <zhaogongyi@huawei.com>
> ---
> include/lapi/syscalls/aarch64.in | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/lapi/syscalls/aarch64.in b/include/lapi/syscalls/aarch64.in
> index a47185954..e9023a1d0 100644
> --- a/include/lapi/syscalls/aarch64.in
> +++ b/include/lapi/syscalls/aarch64.in
> @@ -19,7 +19,6 @@ getcwd 17
> lookup_dcookie 18
> eventfd2 19
> epoll_create1 20
> -epoll_ctl 21
> epoll_pwait 22
> dup 23
> dup3 24
> @@ -243,6 +242,8 @@ rt_tgsigqueueinfo 240
> perf_event_open 241
> accept4 242
> recvmmsg 243
> +epoll_create 250
> +epoll_ctl 251
These values are for 32 bit only syscalls. Won't this break 64 bit?
> wait4 260
> prlimit64 261
> fanotify_init 262
> --
> 2.17.1
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-10-26 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 7:50 [LTP] [PATCH] lapi/syscalls: Add epoll_create for aarch64.in Zhao Gongyi
2021-10-26 12:30 ` Jan Stancek [this message]
2021-10-27 3:28 zhaogongyi
2021-10-27 8:35 ` Jan Stancek
2021-10-27 9:36 zhaogongyi
2021-10-27 9:44 ` Jan Stancek
2021-10-27 9:55 zhaogongyi
2021-10-28 3:15 zhaogongyi
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=CAASaF6yWxgM5M0L23k64GkDLBoahxi8-4-zao+yJD0NjtMn9HA@mail.gmail.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
--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;
as well as URLs for NNTP newsgroup(s).