From: Jiri Slaby <jirislaby@kernel.org>
To: Andrei Vagin <avagin@google.com>,
Kees Cook <keescook@chromium.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
Chen Yu <yu.c.chen@intel.com>,
avagin@gmail.com, Andy Lutomirski <luto@amacapital.net>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Peter Oskolkov <posk@google.com>,
Tycho Andersen <tycho@tycho.pizza>,
Will Drewry <wad@chromium.org>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH 6/6] perf/benchmark: add a new benchmark for seccom_unotify
Date: Tue, 17 Oct 2023 10:24:26 +0200 [thread overview]
Message-ID: <246f6f89-78f7-4b47-8260-8d2e3c9e0f0a@kernel.org> (raw)
In-Reply-To: <20230308073201.3102738-7-avagin@google.com>
On 08. 03. 23, 8:32, Andrei Vagin wrote:
> --- a/tools/arch/x86/include/uapi/asm/unistd_32.h
> +++ b/tools/arch/x86/include/uapi/asm/unistd_32.h
> @@ -23,3 +23,6 @@
> #ifndef __NR_setns
> #define __NR_setns 346
> #endif
> +#ifdef __NR_seccomp
Ouch. s/ifdef/ifndef/
bench/sched-seccomp-notify.c:46:24: error: '__NR_seccomp' undeclared
Will send a fix.
> +#define __NR_seccomp 354
> +#endif
> diff --git a/tools/arch/x86/include/uapi/asm/unistd_64.h b/tools/arch/x86/include/uapi/asm/unistd_64.h
> index a6f7fe84d4df..e0549617f9d7 100644
> --- a/tools/arch/x86/include/uapi/asm/unistd_64.h
> +++ b/tools/arch/x86/include/uapi/asm/unistd_64.h
> @@ -23,3 +23,6 @@
> #ifndef __NR_getcpu
> #define __NR_getcpu 309
> #endif
> +#ifndef __NR_seccomp
This one is good...
--
js
suse labs
next prev parent reply other threads:[~2023-10-17 8:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 7:31 [PATCH 0/6 v5 RESEND] seccomp: add the synchronous mode for seccomp_unotify Andrei Vagin
2023-03-08 7:31 ` [PATCH 1/6] seccomp: don't use semaphore and wait_queue together Andrei Vagin
2023-03-08 7:31 ` [PATCH 2/6] sched: add WF_CURRENT_CPU and externise ttwu Andrei Vagin
2023-04-08 3:20 ` Chen Yu
2023-04-10 4:56 ` Andrei Vagin
2023-04-10 17:27 ` Andy Lutomirski
2023-04-12 19:38 ` Andrei Vagin
2023-04-10 18:16 ` Chen Yu
2023-04-11 1:50 ` Chen Yu
2023-04-17 19:24 ` Andrei Vagin
2023-03-08 7:31 ` [PATCH 3/6] sched: add a few helpers to wake up tasks on the current cpu Andrei Vagin
2023-04-26 14:43 ` Bernd Schubert
2023-04-26 18:52 ` Andrei Vagin
2023-04-26 19:35 ` Bernd Schubert
2023-04-26 20:57 ` Bernd Schubert
2023-03-08 7:31 ` [PATCH 4/6] seccomp: add the synchronous mode for seccomp_unotify Andrei Vagin
2023-04-06 3:42 ` Andy Lutomirski
2023-04-10 6:59 ` Andrei Vagin
2023-04-10 20:53 ` Andy Lutomirski
2023-03-08 7:32 ` [PATCH 5/6] selftest/seccomp: add a new test for the sync mode of seccomp_user_notify Andrei Vagin
2023-03-08 7:32 ` [PATCH 6/6] perf/benchmark: add a new benchmark for seccom_unotify Andrei Vagin
2023-09-08 17:35 ` [PATCH] perf/benchmark: Fix ifdef in header file uapi/asm/unistd_32.h Vijayendra Suman
2023-09-08 17:38 ` Andrei Vagin
2023-09-08 18:18 ` Tycho Andersen
2023-10-17 8:24 ` Jiri Slaby [this message]
2023-03-21 18:19 ` [PATCH 0/6 v5 RESEND] seccomp: add the synchronous mode for seccomp_unotify Andrei Vagin
2023-03-27 10:27 ` Peter Zijlstra
2023-04-03 18:32 ` Andrei Vagin
2023-04-06 3:19 ` Kees Cook
2023-06-28 18:44 ` Andrei Vagin
2023-06-28 23:32 ` Kees Cook
-- strict thread matches above, loose matches on Subject: below --
2023-02-02 3:04 [PATCH 0/6 v5] " Andrei Vagin
2023-02-02 3:04 ` [PATCH 6/6] perf/benchmark: add a new benchmark for seccom_unotify Andrei Vagin
2023-01-24 23:41 [PATCH 0/6 v4] seccomp: add the synchronous mode for seccomp_unotify Andrei Vagin
2023-01-24 23:41 ` [PATCH 6/6] perf/benchmark: add a new benchmark for seccom_unotify Andrei Vagin
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=246f6f89-78f7-4b47-8260-8d2e3c9e0f0a@kernel.org \
--to=jirislaby@kernel.org \
--cc=avagin@gmail.com \
--cc=avagin@google.com \
--cc=brauner@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=posk@google.com \
--cc=tycho@tycho.pizza \
--cc=vincent.guittot@linaro.org \
--cc=wad@chromium.org \
--cc=yu.c.chen@intel.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).