From: Jon Hunter <jonathanh@nvidia.com>
To: Marco Elver <elver@google.com>, <peterz@infradead.org>,
<alexander.shishkin@linux.intel.com>, <acme@kernel.org>,
<mingo@redhat.com>, <jolsa@redhat.com>, <mark.rutland@arm.com>,
<namhyung@kernel.org>, <tglx@linutronix.de>
Cc: <glider@google.com>, <viro@zeniv.linux.org.uk>, <arnd@arndb.de>,
<christian@brauner.io>, <dvyukov@google.com>, <jannh@google.com>,
<axboe@kernel.dk>, <mascasa@google.com>, <pcc@google.com>,
<irogers@google.com>, <oleg@redhat.com>,
<kasan-dev@googlegroups.com>, <linux-arch@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<x86@kernel.org>, <linux-kselftest@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-tegra <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v4 05/10] signal: Introduce TRAP_PERF si_code and si_perf to siginfo
Date: Wed, 21 Apr 2021 16:07:13 +0100 [thread overview]
Message-ID: <81254854-aa22-fab1-fc6f-22716b7c2732@nvidia.com> (raw)
In-Reply-To: <20210408103605.1676875-6-elver@google.com>
Hello!
On 08/04/2021 11:36, Marco Elver wrote:
> Introduces the TRAP_PERF si_code, and associated siginfo_t field
> si_perf. These will be used by the perf event subsystem to send signals
> (if requested) to the task where an event occurred.
>
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org> # m68k
> Acked-by: Arnd Bergmann <arnd@arndb.de> # asm-generic
> Signed-off-by: Marco Elver <elver@google.com>
Since next-20210420 I have noticed a boot regression on all 32-bit Tegra
that we are testing. Bisect is pointing to this commit and reverting
this patch and patch 6/10 does resolve the issue.
Interestingly there is no apparent crash, but these systems just appear
to hang silently after mounting the rootfs. If anyone has any thoughts
let me know!
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2021-04-21 15:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 10:35 [PATCH v4 00/10] Add support for synchronous signals on perf events Marco Elver
2021-04-08 10:35 ` [PATCH v4 01/10] perf: Rework perf_event_exit_event() Marco Elver
2021-04-08 10:35 ` [PATCH v4 02/10] perf: Apply PERF_EVENT_IOC_MODIFY_ATTRIBUTES to children Marco Elver
2021-04-08 10:35 ` [PATCH v4 03/10] perf: Support only inheriting events if cloned with CLONE_THREAD Marco Elver
2021-04-08 10:35 ` [PATCH v4 04/10] perf: Add support for event removal on exec Marco Elver
2021-04-08 10:36 ` [PATCH v4 05/10] signal: Introduce TRAP_PERF si_code and si_perf to siginfo Marco Elver
[not found] ` <CGME20210420212618eucas1p102b427d1af9c682217dfe093f3eac3e8@eucas1p1.samsung.com>
2021-04-20 21:26 ` Marek Szyprowski
2021-04-20 22:42 ` Marco Elver
2021-04-21 6:21 ` Marek Szyprowski
2021-04-21 7:35 ` Marek Szyprowski
2021-04-21 8:11 ` Marco Elver
2021-04-21 9:35 ` Marek Szyprowski
2021-04-21 10:57 ` Marek Szyprowski
2021-04-21 11:03 ` Marco Elver
2021-04-21 13:19 ` Marek Szyprowski
2021-04-21 15:11 ` Marco Elver
2021-04-21 16:27 ` Marco Elver
2021-04-21 18:23 ` Marco Elver
2021-04-22 6:12 ` Marek Szyprowski
2021-04-22 6:47 ` Marco Elver
2021-04-22 8:16 ` Jon Hunter
2021-04-26 7:35 ` Alexander Egorenkov
2021-04-21 15:07 ` Jon Hunter [this message]
2021-04-08 10:36 ` [PATCH v4 06/10] perf: Add support for SIGTRAP on perf events Marco Elver
2021-04-08 10:36 ` [PATCH v4 07/10] selftests/perf_events: Add kselftest for process-wide sigtrap handling Marco Elver
2021-04-08 10:36 ` [PATCH v4 08/10] selftests/perf_events: Add kselftest for remove_on_exec Marco Elver
2021-04-08 10:36 ` [PATCH v4 09/10] tools headers uapi: Sync tools/include/uapi/linux/perf_event.h Marco Elver
2021-04-08 10:36 ` [PATCH v4 10/10] perf test: Add basic stress test for sigtrap handling Marco Elver
2021-04-14 8:37 ` [PATCH v4 00/10] Add support for synchronous signals on perf events Peter Zijlstra
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=81254854-aa22-fab1-fc6f-22716b7c2732@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=christian@brauner.io \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=geert@linux-m68k.org \
--cc=glider@google.com \
--cc=irogers@google.com \
--cc=jannh@google.com \
--cc=jolsa@redhat.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mascasa@google.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=pcc@google.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@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).