From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Mike Galbraith <efault@gmx.de>,
Peter Zijlstra <peterz@infradead.org>,
Marco Elver <elver@google.com>,
linux-rt-users@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Juri Lelli <juri.lelli@redhat.com>,
Clark Williams <williams@redhat.com>,
Alessandro Carminati <acarmina@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Artem Savkov <asavkov@redhat.com>
Subject: Re: 'perf test sigtrap' failing on PREEMPT_RT_FULL
Date: Fri, 8 Mar 2024 18:59:07 +0100 [thread overview]
Message-ID: <20240308175907.Stc5UU3y@linutronix.de> (raw)
In-Reply-To: <20240306165443.5AKJ403t@linutronix.de>
On 2024-03-06 17:54:45 [+0100], To Arnaldo Carvalho de Melo wrote:
> Not sure what the best course of action is here but based on what I
> learned last time you reported this I think we need delayed signals…
> Let me look into this. We had it and then removed it because we had no
> users of it at some point but probably nobody took perf into account.
=> https://lore.kernel.org/20240308175810.2894694-1-bigeasy@linutronix.de
> - Arnaldo
Sebastian
prev parent reply other threads:[~2024-03-08 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 20:15 'perf test sigtrap' failing on PREEMPT_RT_FULL Arnaldo Carvalho de Melo
2023-07-26 6:10 ` Mike Galbraith
2023-07-26 15:23 ` Arnaldo Carvalho de Melo
2023-07-28 15:07 ` Sebastian Andrzej Siewior
2024-01-04 22:35 ` Arnaldo Carvalho de Melo
2024-02-21 19:26 ` Arnaldo Carvalho de Melo
2024-03-06 13:06 ` Arnaldo Carvalho de Melo
2024-03-06 16:27 ` Arnaldo Carvalho de Melo
2024-03-06 16:54 ` Sebastian Andrzej Siewior
2024-03-08 17:59 ` Sebastian Andrzej Siewior [this message]
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=20240308175907.Stc5UU3y@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=acarmina@redhat.com \
--cc=acme@kernel.org \
--cc=asavkov@redhat.com \
--cc=efault@gmx.de \
--cc=elver@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).