From: Frederic Weisbecker <fweisbec@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Joshua Pincus <joshua.pincus@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
"K.Prasad" <prasad@linux.vnet.ibm.com>,
peterz@infradead.org, paulus@samba.org, acme@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: HW breakpoints perf_events request
Date: Tue, 19 Jan 2010 15:50:29 +0100 [thread overview]
Message-ID: <20100119145027.GB8061@nowhere> (raw)
In-Reply-To: <y0maawbid91.fsf@fche.csb>
On Mon, Jan 18, 2010 at 11:33:46AM -0500, Frank Ch. Eigler wrote:
> Frederic Weisbecker <fweisbec@gmail.com> writes:
>
> > [...]
> > What about extending ptrace to support a new type of
> > breakpoint debugging interface?
>
> This is the sort of reason why the utrace-gdbstub prototype was
> constructed. It should allow in-kernel implementation of the
> multithreaded gdb extensions. (By the way, it can already use uprobes
> rather than userspace-managed breakpoints.)
Can utrace somehow meet Joshua's needs? I'm not sure what kind
of interface it can offer for that. The fact is I don't know
very well utrace :) Do you plan a resubmission soon?
Thanks.
next prev parent reply other threads:[~2010-01-19 14:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 1:45 HW breakpoints perf_events request Joshua Pincus
2010-01-14 2:15 ` Andi Kleen
2010-01-14 2:21 ` Joshua Pincus
2010-01-14 9:23 ` Andi Kleen
2010-01-14 18:03 ` Joshua Pincus
2010-01-18 11:04 ` Frederic Weisbecker
2010-01-18 11:35 ` Andi Kleen
2010-01-19 14:40 ` Frederic Weisbecker
2010-01-18 16:33 ` Frank Ch. Eigler
2010-01-19 14:50 ` Frederic Weisbecker [this message]
2010-01-19 15:12 ` Frank Ch. Eigler
2010-01-19 16:21 ` Frederic Weisbecker
2010-01-19 16:26 ` Peter Zijlstra
2010-01-19 17:44 ` Frank Ch. Eigler
2010-01-14 5:10 ` Frederic Weisbecker
2010-01-14 8:44 ` Peter Zijlstra
2010-01-14 18:02 ` Joshua Pincus
2010-01-18 17:45 ` K.Prasad
2010-01-19 14:53 ` Frederic Weisbecker
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=20100119145027.GB8061@nowhere \
--to=fweisbec@gmail.com \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=fche@redhat.com \
--cc=joshua.pincus@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=prasad@linux.vnet.ibm.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