From: Andi Kleen <andi@firstfloor.org>
To: Joshua Pincus <joshua.pincus@gmail.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
"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: Thu, 14 Jan 2010 03:15:33 +0100 [thread overview]
Message-ID: <87ljg1fn3u.fsf@basil.nowhere.org> (raw)
In-Reply-To: <bc915a051001131745m6fb70dcbx29b9d35f6fd7106c@mail.gmail.com> (Joshua Pincus's message of "Wed, 13 Jan 2010 17:45:55 -0800")
Joshua Pincus <joshua.pincus@gmail.com> writes:
> I have a request for an additional feature to be included
> in the recent hardware breakpoints work soon to be delivered
> in kernel 2.6.33.
Sounds to me like the existing ptrace based interface
can practically all you want
(except that the "parent signal" would be wait and for
fork/exec you have to explicitely attach)
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-01-14 2:15 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 [this message]
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
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=87ljg1fn3u.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.