From: Will Deacon <will@kernel.org>
To: linux-trace-devel@vger.kernel.org,
Francis Laniel <flaniel@linux.microsoft.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Peter Collingbourne <pcc@google.com>,
Mark Brown <broonie@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Kees Cook <keescook@chromium.org>,
Daniel Kiss <daniel.kiss@arm.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
James Morse <james.morse@arm.com>,
Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [PATCH v2 0/1] Remove forget_syscall() from start_thread_common()
Date: Fri, 1 Jul 2022 16:41:28 +0100 [thread overview]
Message-ID: <165667517849.792239.13818767623596011011.b4-ty@kernel.org> (raw)
In-Reply-To: <20220608162447.666494-1-flaniel@linux.microsoft.com>
On Wed, 8 Jun 2022 17:24:45 +0100, Francis Laniel wrote:
> First, I hope you are fine and the same for your relatives.
>
> With this contribution, I enabled using syscalls:sys_exit_execve and
> syscalls:sys_exit_execveat as tracepoints on arm64.
> Indeed, before this contribution, the above tracepoint would not print their
> information as syscall number was set to -1 by calling forget_syscall().
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64: Do not forget syscall when starting a new thread.
https://git.kernel.org/arm64/c/de6921856f99
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: linux-trace-devel@vger.kernel.org,
Francis Laniel <flaniel@linux.microsoft.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Peter Collingbourne <pcc@google.com>,
Mark Brown <broonie@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Kees Cook <keescook@chromium.org>,
Daniel Kiss <daniel.kiss@arm.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
James Morse <james.morse@arm.com>,
Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [PATCH v2 0/1] Remove forget_syscall() from start_thread_common()
Date: Fri, 1 Jul 2022 16:41:28 +0100 [thread overview]
Message-ID: <165667517849.792239.13818767623596011011.b4-ty@kernel.org> (raw)
In-Reply-To: <20220608162447.666494-1-flaniel@linux.microsoft.com>
On Wed, 8 Jun 2022 17:24:45 +0100, Francis Laniel wrote:
> First, I hope you are fine and the same for your relatives.
>
> With this contribution, I enabled using syscalls:sys_exit_execve and
> syscalls:sys_exit_execveat as tracepoints on arm64.
> Indeed, before this contribution, the above tracepoint would not print their
> information as syscall number was set to -1 by calling forget_syscall().
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64: Do not forget syscall when starting a new thread.
https://git.kernel.org/arm64/c/de6921856f99
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: linux-trace-devel@vger.kernel.org,
Francis Laniel <flaniel@linux.microsoft.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Peter Collingbourne <pcc@google.com>,
Mark Brown <broonie@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Kees Cook <keescook@chromium.org>,
Daniel Kiss <daniel.kiss@arm.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
James Morse <james.morse@arm.com>,
Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [PATCH v2 0/1] Remove forget_syscall() from start_thread_common()
Date: Fri, 1 Jul 2022 16:41:28 +0100 [thread overview]
Message-ID: <165667517849.792239.13818767623596011011.b4-ty@kernel.org> (raw)
In-Reply-To: <20220608162447.666494-1-flaniel@linux.microsoft.com>
On Wed, 8 Jun 2022 17:24:45 +0100, Francis Laniel wrote:
> First, I hope you are fine and the same for your relatives.
>
> With this contribution, I enabled using syscalls:sys_exit_execve and
> syscalls:sys_exit_execveat as tracepoints on arm64.
> Indeed, before this contribution, the above tracepoint would not print their
> information as syscall number was set to -1 by calling forget_syscall().
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64: Do not forget syscall when starting a new thread.
https://git.kernel.org/arm64/c/de6921856f99
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-01 15:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 16:24 [PATCH v2 0/1] Remove forget_syscall() from start_thread_common() Francis Laniel
2022-06-08 16:24 ` Francis Laniel
2022-06-08 16:24 ` Francis Laniel
2022-06-08 16:24 ` [PATCH v2 1/1] arm64: Do not forget syscall when starting a new thread Francis Laniel
2022-06-08 16:24 ` Francis Laniel
2022-06-28 13:58 ` Will Deacon
2022-06-28 13:58 ` Will Deacon
2022-06-28 19:26 ` Francis Laniel
2022-06-28 19:26 ` Francis Laniel
2022-06-30 17:16 ` Francis Laniel
2022-06-30 17:16 ` Francis Laniel
2022-07-01 11:36 ` Will Deacon
2022-07-01 11:36 ` Will Deacon
2022-07-01 12:10 ` Francis Laniel
2022-07-01 12:10 ` Francis Laniel
2022-06-23 14:09 ` [PATCH v2 0/1] Remove forget_syscall() from start_thread_common() Francis Laniel
2022-06-23 14:09 ` Francis Laniel
2022-06-23 14:09 ` Francis Laniel
2022-07-01 15:41 ` Will Deacon [this message]
2022-07-01 15:41 ` Will Deacon
2022-07-01 15:41 ` Will Deacon
2022-07-04 8:55 ` Francis Laniel
2022-07-04 8:55 ` Francis Laniel
2022-07-04 8:55 ` Francis Laniel
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=165667517849.792239.13818767623596011011.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=daniel.kiss@arm.com \
--cc=flaniel@linux.microsoft.com \
--cc=james.morse@arm.com \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pcc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.