From: Peter Zijlstra <peterz@infradead.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Will Deacon <will@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Matt Morehouse <mascasa@google.com>
Subject: Re: Process-wide watchpoints
Date: Wed, 3 Feb 2021 13:29:50 +0100 [thread overview]
Message-ID: <YBqXPmbpXf4hnlj3@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CACT4Y+YeRtOTsMQ8xxZg-=nbv+yuJvYYhBErT46M8jtSHmiw6g@mail.gmail.com>
On Mon, Feb 01, 2021 at 09:50:20AM +0100, Dmitry Vyukov wrote:
> Or, alternatively would it be reasonable for perf to generate SIGTRAP
> directly on watchpoint hit (like ptrace does)? That's what I am
> ultimately trying to do by attaching a bpf program.
Perf should be able to generate signals, The perf_event_open manpage
lists two ways of trigering signals. The second way doesn't work for
you, due to it not working on inherited counters, but would the first
work?
That is, set attr::wakeup_events and fcntl(F_SETSIG).
next prev parent reply other threads:[~2021-02-03 12:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 7:46 Process-wide watchpoints Dmitry Vyukov
2020-11-12 10:31 ` Peter Zijlstra
2020-11-12 10:43 ` Dmitry Vyukov
[not found] ` <CACT4Y+bW1gpv8bz0vswaVUt-OB07oJ3NBeTi+vchAe8TTWK+mg@mail.gmail.com>
[not found] ` <CACT4Y+ZsKXfAxrzJGQc5mJ+QiP5sAw7zKWtciS+07qZzSf33mw@mail.gmail.com>
2021-02-01 8:50 ` Dmitry Vyukov
2021-02-03 12:29 ` Peter Zijlstra [this message]
2021-02-03 12:49 ` Dmitry Vyukov
2021-02-03 12:50 ` Dmitry Vyukov
2021-02-03 13:37 ` Peter Zijlstra
2021-02-04 8:10 ` Dmitry Vyukov
2021-02-04 9:38 ` Peter Zijlstra
2021-02-04 9:54 ` Dmitry Vyukov
2021-02-04 12:09 ` Peter Zijlstra
2021-02-04 12:53 ` Dmitry Vyukov
2021-02-04 13:10 ` Peter Zijlstra
2021-02-04 13:35 ` Dmitry Vyukov
2021-02-04 13:45 ` Peter Zijlstra
2021-02-04 14:59 ` Peter Zijlstra
2021-02-04 13:33 ` Peter Zijlstra
2021-02-04 13:37 ` Dmitry Vyukov
2021-02-04 13:06 ` Peter Zijlstra
2021-02-03 5:38 ` Namhyung Kim
2021-02-04 8:10 ` Dmitry Vyukov
2021-02-03 12:22 ` 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=YBqXPmbpXf4hnlj3@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=dvyukov@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mascasa@google.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=will@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