From: Oleg Nesterov <oleg@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Project Archer <archer@sourceware.org>
Subject: Re: hw_breakpoint userland interface
Date: Thu, 10 Feb 2011 21:03:00 -0000 [thread overview]
Message-ID: <20110210205543.GA4590@redhat.com> (raw)
In-Reply-To: <20110208231846.EC8BA1814AA@magilla.sf.frob.com>
On 02/08, Roland McGrath wrote:
>
> There are indeed many things to be figured out about a userland interface
> for hw_breakpoint. It's certainly quite possible that something entirely
> separate from ptrace is the right approach for that. I haven't given it
> any thought, really.
The same. And yes, perhaps it should be more perf_event oriented. Afaics, it
is already possible to create the bp via sys_perf_open(PERF_TYPE_BREAKPOINT),
but I didn't verify this.
> It should be worked out with Jan and other GDB folks
Yes. Firstly we need to know what would be more convenient for those
who will actually use the new interface.
But there is one thing which is even less clear to me. From you
previous email,
> > Those can be defined with
> > the inheritance and process-wide sharing issues in mind,
(to remind, you were talking about watchpoints/PTRACE_O_INHERIT problems).
Do you have any plans to introduce something like per-process
breakpoints, or (apart from inheriting) everything continues to
be per-thread?
Oleg.
next prev parent reply other threads:[~2011-02-10 21:03 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 22:39 ptrace improvement ideas Roland McGrath
2011-02-04 18:56 ` Oleg Nesterov
2011-02-04 18:58 ` Roland McGrath
2011-02-07 21:11 ` Jan Kratochvil
2011-02-08 1:58 ` Roland McGrath
2011-02-08 20:41 ` Jan Kratochvil
2011-02-09 2:48 ` Roland McGrath
2011-02-08 21:07 ` Oleg Nesterov
2011-02-08 23:18 ` hw_breakpoint userland interface Roland McGrath
2011-02-10 21:03 ` Oleg Nesterov [this message]
2011-02-10 21:14 ` Roland McGrath
2011-02-11 20:17 ` Oleg Nesterov
2011-02-10 20:00 ` ptrace improvement: PTRACE_O_INHERIT Oleg Nesterov
2011-02-11 19:24 ` Roland McGrath
2011-02-11 20:46 ` Oleg Nesterov
2011-02-12 0:59 ` Roland McGrath
2011-02-12 19:11 ` Oleg Nesterov
2011-02-14 19:31 ` Roland McGrath
2011-02-14 19:46 ` Oleg Nesterov
2011-02-15 0:36 ` Roland McGrath
2011-02-15 13:16 ` Oleg Nesterov
2011-02-15 21:43 ` Jan Kratochvil
2011-02-15 21:56 ` Roland McGrath
2011-02-16 19:42 ` Oleg Nesterov
2011-02-16 19:45 ` Roland McGrath
2011-02-16 20:09 ` Oleg Nesterov
2011-02-16 20:16 ` Roland McGrath
2011-02-19 19:48 ` Jan Kratochvil
2011-02-19 20:37 ` Oleg Nesterov
2011-02-20 8:18 ` Jan Kratochvil
2011-02-20 21:05 ` Oleg Nesterov
2011-02-21 19:54 ` Roland McGrath
2011-02-22 19:39 ` Oleg Nesterov
2011-02-22 20:49 ` Roland McGrath
2011-02-22 21:10 ` Oleg Nesterov
2011-02-22 22:16 ` Roland McGrath
2011-02-21 19:44 ` Roland McGrath
2011-02-15 22:02 ` Roland McGrath
2011-02-16 16:02 ` Jan Kratochvil
2011-02-16 18:28 ` Roland McGrath
2011-02-16 20:00 ` Oleg Nesterov
2011-02-16 20:07 ` Roland McGrath
2011-02-16 20:32 ` Oleg Nesterov
2011-02-16 19:48 ` Oleg Nesterov
2011-02-16 20:02 ` Roland McGrath
2011-02-16 20:15 ` Oleg Nesterov
2011-02-16 20:31 ` Roland McGrath
2011-02-16 21:04 ` Oleg Nesterov
2011-02-16 21:51 ` Roland McGrath
2011-02-16 19:38 ` Oleg Nesterov
2011-02-16 19:40 ` Roland McGrath
2011-02-15 22:17 ` Roland McGrath
2011-02-16 20:48 ` Oleg Nesterov
2011-02-16 11:31 ` ptrace improvement ideas (QPassSignals) Jan Kratochvil
2011-02-16 18:36 ` Roland McGrath
2011-02-16 20:21 ` Oleg Nesterov
2011-02-18 20:24 ` Oleg Nesterov
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=20110210205543.GA4590@redhat.com \
--to=oleg@redhat.com \
--cc=archer@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=roland@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).