From: Will Deacon <will.deacon@arm.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <Catalin.Marinas@arm.com>
Subject: Re: [PATCH] generic syscalls: wire up userfaultfd syscall
Date: Tue, 22 Sep 2015 16:52:52 +0100 [thread overview]
Message-ID: <20150922155251.GJ7356@arm.com> (raw)
In-Reply-To: <1442919139-18027-1-git-send-email-andre.przywara@arm.com>
On Tue, Sep 22, 2015 at 11:52:19AM +0100, Andre Przywara wrote:
> Enable the new userfaultfd syscall in the generic syscall table.
> Briefly tested on arm64 with the selftest from the tools directory.
Can you update the selftest too, please? Last time I looked at that it had
typo for the powerpc check and looked pretty unloved...
Will
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> include/uapi/asm-generic/unistd.h | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/include/uapi/asm-generic/unistd.h b/include/uapi/asm-generic/unistd.h
> index 8da542a..82c91bc 100644
> --- a/include/uapi/asm-generic/unistd.h
> +++ b/include/uapi/asm-generic/unistd.h
> @@ -711,9 +711,11 @@ __SYSCALL(__NR_bpf, sys_bpf)
> __SC_COMP(__NR_execveat, sys_execveat, compat_sys_execveat)
> #define __NR_membarrier 282
> __SYSCALL(__NR_membarrier, sys_membarrier)
> +#define __NR_userfaultfd 283
> +__SYSCALL(__NR_userfaultfd, sys_userfaultfd)
>
> #undef __NR_syscalls
> -#define __NR_syscalls 283
> +#define __NR_syscalls 284
>
> /*
> * All syscalls below here should go away really,
> --
> 2.5.1
>
next prev parent reply other threads:[~2015-09-22 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 10:52 [PATCH] generic syscalls: wire up userfaultfd syscall Andre Przywara
2015-09-22 15:52 ` Will Deacon [this message]
2015-09-22 16:51 ` Andre Przywara
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=20150922155251.GJ7356@arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=andre.przywara@arm.com \
--cc=arnd@arndb.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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).