From: "S. P. Prasanna" <prasanna@in.ibm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Roland McGrath <roland@redhat.com>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Kwatch: kernel watchpoints using CPU debug registers
Date: Thu, 22 Feb 2007 17:13:26 +0530 [thread overview]
Message-ID: <20070222114326.GA14910@in.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0702211458250.3435-100000@iolanthe.rowland.org>
On Wed, Feb 21, 2007 at 03:35:13PM -0500, Alan Stern wrote:
> Going back to something you mentioned earlier...
>
[...]
> On Fri, 9 Feb 2007, Roland McGrath wrote:
> There are two things I am uncertain about: vm86 mode and kprobes. I don't
> know anything about how either of them works. Judging from the current
> code, nothing much should be needed -- debug traps in vm86 mode are
> handled by calling handle_vm86_trap(), and kprobes puts itself at the
> start of the notify_die() chain so it can handle single-step traps.
> Eventually it will be necessary to check with someone who really
> understands the issues.
Yes, Kprobes needs to get notified first to handle single-step traps. So kwatch
getting notified secound should be fine.
Thanks
Prasanna
--
Prasanna S.P.
Linux Technology Center
India Software Labs, IBM Bangalore
Email: prasanna@in.ibm.com
Ph: 91-80-41776329
next prev parent reply other threads:[~2007-02-22 11:42 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070207025008.1B11118005D@magilla.sf.frob.com>
2007-02-07 19:22 ` [PATCH] Kwatch: kernel watchpoints using CPU debug registers Alan Stern
2007-02-07 22:08 ` Bob Copeland
2007-02-09 10:21 ` Roland McGrath
2007-02-09 15:54 ` Alan Stern
2007-02-09 23:31 ` Roland McGrath
2007-02-10 4:32 ` Alan Stern
2007-02-18 3:03 ` Roland McGrath
2007-02-21 20:35 ` Alan Stern
2007-02-22 11:43 ` S. P. Prasanna [this message]
2007-02-23 2:19 ` Roland McGrath
2007-02-23 16:55 ` Alan Stern
2007-02-24 0:08 ` Roland McGrath
2007-03-02 17:19 ` [RFC] hwbkpt: Hardware breakpoints (was Kwatch) Alan Stern
2007-03-05 7:01 ` Roland McGrath
2007-03-05 13:36 ` Christoph Hellwig
2007-03-05 16:16 ` Alan Stern
2007-03-05 16:49 ` Christoph Hellwig
2007-03-05 22:04 ` Roland McGrath
2007-03-05 17:25 ` Alan Stern
2007-03-06 3:13 ` Roland McGrath
2007-03-06 15:23 ` Alan Stern
2007-03-07 3:49 ` Roland McGrath
2007-03-07 19:11 ` Alan Stern
2007-03-09 6:52 ` Roland McGrath
2007-03-09 18:40 ` Alan Stern
2007-03-13 8:00 ` Roland McGrath
2007-03-13 13:07 ` Alan Cox
2007-03-13 18:56 ` Alan Stern
2007-03-14 3:00 ` Roland McGrath
2007-03-14 19:11 ` Alan Stern
2007-03-28 21:39 ` Roland McGrath
2007-03-29 21:35 ` Alan Stern
2007-04-13 21:09 ` Alan Stern
2007-05-11 15:25 ` Alan Stern
2007-05-13 10:39 ` Roland McGrath
2007-05-14 15:42 ` Alan Stern
2007-05-14 21:25 ` Roland McGrath
2007-05-16 19:03 ` Alan Stern
2007-05-23 8:47 ` Roland McGrath
2007-06-01 19:39 ` Alan Stern
2007-06-14 6:48 ` Roland McGrath
2007-06-19 20:35 ` Alan Stern
2007-06-25 10:52 ` Roland McGrath
2007-06-25 15:36 ` Alan Stern
2007-06-26 20:49 ` Roland McGrath
2007-06-27 3:26 ` Alan Stern
2007-06-27 21:04 ` Roland McGrath
2007-06-29 3:00 ` Alan Stern
2007-07-11 6:59 ` Roland McGrath
2007-06-28 3:02 ` Roland McGrath
2007-06-25 11:32 ` Roland McGrath
2007-06-25 15:37 ` Alan Stern
2007-06-25 20:51 ` Alan Stern
2007-06-26 18:17 ` Roland McGrath
2007-06-27 2:43 ` Alan Stern
2007-05-17 20:39 ` Alan Stern
2007-03-16 21:07 ` Alan Stern
2007-03-22 19:44 ` Alan Stern
[not found] <20070206042153.66AB418005D@magilla.sf.frob.com>
2007-02-06 19:58 ` [PATCH] Kwatch: kernel watchpoints using CPU debug registers Alan Stern
2007-02-07 2:56 ` Roland McGrath
2007-01-16 16:55 Alan Stern
2007-01-16 23:35 ` Christoph Hellwig
2007-01-17 16:33 ` Alan Stern
2007-01-17 9:44 ` Ingo Molnar
2007-01-17 16:17 ` Alan Stern
2007-01-18 0:12 ` Christoph Hellwig
2007-01-18 7:31 ` Ingo Molnar
2007-01-18 15:37 ` Alan Stern
2007-01-18 22:33 ` Christoph Hellwig
2007-02-06 4:25 ` Roland McGrath
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=20070222114326.GA14910@in.ibm.com \
--to=prasanna@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=stern@rowland.harvard.edu \
/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.