[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YBvxc1U/UFhrj0NW@hirez.programming.kicks-ass.net>
Date: Thu, 4 Feb 2021 14:06:59 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Will Deacon <will@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Matt Morehouse <mascasa@...gle.com>
Subject: Re: Process-wide watchpoints
On Thu, Feb 04, 2021 at 01:09:13PM +0100, Peter Zijlstra wrote:
> And I need to dig into that fcntl() crud again, see if that's capable of
> doing a SIGTRAP and if it's possible to target that to the task raising
> it, instead of doing a process wide signal delivery.
Hmm, so it might be possible to extend SETOWN_EX to allow
{F_OWNER_TID,0} to mean any current thread.
And I think SETSIG can be used to set SIGTRAP, although I don't see it
setting the fields you wanted, not entirely sure that's fixable.
Powered by blists - more mailing lists