public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: Frederic Weisbecker <fweisbec@gmail.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: Mon, 18 Jan 2010 11:33:46 -0500	[thread overview]
Message-ID: <y0maawbid91.fsf@fche.csb> (raw)
In-Reply-To: <20100118110406.GC5256@nowhere> (Frederic Weisbecker's message of "Mon, 18 Jan 2010 12:04:07 +0100")

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.)

- FChE

  parent reply	other threads:[~2010-01-18 16:34 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 [this message]
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=y0maawbid91.fsf@fche.csb \
    --to=fche@redhat.com \
    --cc=acme@redhat.com \
    --cc=andi@firstfloor.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox