public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/2064] Support pagepoint probes
Date: Tue, 14 Apr 2009 18:58:00 -0000	[thread overview]
Message-ID: <20090414185804.21066.qmail@sourceware.org> (raw)
In-Reply-To: <20051216211044.2064.jkenisto@us.ibm.com>


------- Additional Comments From jkenisto at us dot ibm dot com  2009-04-14 18:58 -------
Subject: Re:  Support pagepoint probes

On Tue, 2009-04-14 at 17:17 +0000, fche at redhat dot com wrote:
> ------- Additional Comments From fche at redhat dot com  2009-04-14 17:17 -------
> Is this duplicated by bug #6883 (kmmio hooks)?
> 
> 

kmmio hooks is #6983, not #6883.  And I think that the two PRs address
substantially different things (memory-mapped I/O versus hardware
breakpoints) -- although the kmmio mechanism might be useful in
implementing #2064.

Jim



-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=2064

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2009-04-14 18:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-17  6:03 [Bug kprobes/2064] New: " jkenisto at us dot ibm dot com
2005-12-17 23:22 ` [Bug kprobes/2064] " marcelo dot tosatti at cyclades dot com
2005-12-18  1:36 ` [Bug kprobes/2064] New: " Marcelo Tosatti
2005-12-18 17:34 ` Andi Kleen
2005-12-19 19:05 ` [Bug kprobes/2064] " jkenisto at us dot ibm dot com
2009-04-14 17:18 ` fche at redhat dot com
2009-04-14 18:54 ` mhiramat at redhat dot com
2009-04-14 18:58 ` jkenisto at us dot ibm dot com [this message]
     [not found] <bug-2064-6586@http.sourceware.org/bugzilla/>
2016-05-24 18:21 ` fche at redhat dot com

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=20090414185804.21066.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sources.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).