From: Andrew Donnellan <ajd@linux.ibm.com>
To: Rohan McLure <rmclure@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: npiggin@gmail.com
Subject: Re: [PATCH v2 03/14] powerpc: Remove direct call to mmap2 syscall handlers
Date: Mon, 08 Aug 2022 13:24:19 +1000 [thread overview]
Message-ID: <e3e58df6fbc801ff53c3e5f5134f974412e27743.camel@linux.ibm.com> (raw)
In-Reply-To: <20220725062558.118793-1-rmclure@linux.ibm.com>
On Mon, 2022-07-25 at 16:25 +1000, Rohan McLure wrote:
>
> diff --git a/tools/perf/arch/powerpc/entry/syscalls/syscall.tbl
> b/tools/perf/arch/powerpc/entry/syscalls/syscall.tbl
> index 54bb5834785f..437066f5c4b2 100644
> --- a/tools/perf/arch/powerpc/entry/syscalls/syscall.tbl
> +++ b/tools/perf/arch/powerpc/entry/syscalls/syscall.tbl
> @@ -243,7 +243,7 @@
> 189 nospu vfork sys_vfork
> 190 common ugetrlimit sys_getrlimit
> compat_sys_getrlimit
> 191 common readahead sys_readahead
> compat_sys_ppc_readahead
> -
> 192 32 mmap2 sys_mmap2
> compat_sys_ppc_mmap2
> +192 32 mmap2 sys_mmap2
> compat_sys_mmap2
> 193 32 truncate64 sys_truncate64
> compat_sys_ppc_truncate64
> 194 32 ftruncate64 sys_ftruncate64
> compat_sys_ppc_ftruncate64
> 195 32 stat64 sys_stat64
> @@ -391,7 +391,7 @@
> 306 common timerfd_create sys_timerfd_create
> 307 common eventfd sys_eventfd
> 308 common sync_file_range2 sys_sync_file_range2
> compat_sys_ppc_sync_file_range2
> -
> 309 nospu fallocate sys_fallocate
> compat_sys_ppc_fallocate
> +309 nospu fallocate sys_fallocate
> compat_sys_fallocate
This should be in patch 5?
> 310 nospu subpage_prot sys_subpage_prot
> 311 32 timerfd_settime sys_timerfd_settime32
> 311 64 timerfd_settime sys_timerfd_settime
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2022-08-08 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 6:25 [PATCH v2 03/14] powerpc: Remove direct call to mmap2 syscall handlers Rohan McLure
2022-08-08 3:24 ` Andrew Donnellan [this message]
2022-08-08 9:43 ` Christophe Leroy
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=e3e58df6fbc801ff53c3e5f5134f974412e27743.camel@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=rmclure@linux.ibm.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).