From: Frederic Weisbecker <fweisbec@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Alan Stern <stern@rowland.harvard.edu>,
"K.Prasad" <prasad@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hw_breakpoint: remove sample code from hw_breakpoint.h
Date: Tue, 7 Jul 2009 23:04:12 +0200 [thread overview]
Message-ID: <20090707210410.GG6184@nowhere> (raw)
In-Reply-To: <4A52DFBB.7040800@cn.fujitsu.com>
On Tue, Jul 07, 2009 at 01:40:11PM +0800, Li Zefan wrote:
> The sample code is a bit out-dated, and there's already a
> sample in sample/hw_breakpoint/.
IMHO these bits of comments are useful and don't overlap the role
of the samples in sample/
They only stand there as a quick summup.
No?
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
> include/asm-generic/hw_breakpoint.h | 41 +---------------------------------
> 1 files changed, 2 insertions(+), 39 deletions(-)
>
> diff --git a/include/asm-generic/hw_breakpoint.h b/include/asm-generic/hw_breakpoint.h
> index 9bf2d12..30ab37c 100644
> --- a/include/asm-generic/hw_breakpoint.h
> +++ b/include/asm-generic/hw_breakpoint.h
> @@ -60,45 +60,8 @@
> * Breakpoints are disabled during execution @triggered, to avoid
> * recursive traps and allow unhindered access to breakpointed memory.
> *
> - * This sample code sets a breakpoint on pid_max and registers a callback
> - * function for writes to that variable. Note that it is not portable
> - * as written, because not all architectures support HW_BREAKPOINT_LEN_4.
> - *
> - * ----------------------------------------------------------------------
> - *
> - * #include <asm/hw_breakpoint.h>
> - *
> - * struct hw_breakpoint my_bp;
> - *
> - * static void my_triggered(struct hw_breakpoint *bp, struct pt_regs *regs)
> - * {
> - * printk(KERN_DEBUG "Inside triggered routine of breakpoint exception\n");
> - * dump_stack();
> - * .......<more debugging output>........
> - * }
> - *
> - * static struct hw_breakpoint my_bp;
> - *
> - * static int init_module(void)
> - * {
> - * ..........<do anything>............
> - * my_bp.info.type = HW_BREAKPOINT_WRITE;
> - * my_bp.info.len = HW_BREAKPOINT_LEN_4;
> - *
> - * my_bp.installed = (void *)my_bp_installed;
> - *
> - * rc = register_kernel_hw_breakpoint(&my_bp);
> - * ..........<do anything>............
> - * }
> - *
> - * static void cleanup_module(void)
> - * {
> - * ..........<do anything>............
> - * unregister_kernel_hw_breakpoint(&my_bp);
> - * ..........<do anything>............
> - * }
> - *
> - * ----------------------------------------------------------------------
> + * See sample/hw_breakpoint/ for a sample that sets a breakpoint on
> + * a specified kernel symbol.
> */
> struct hw_breakpoint {
> void (*triggered)(struct hw_breakpoint *, struct pt_regs *);
> --
> 1.5.4.rc3
next prev parent reply other threads:[~2009-07-07 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 5:40 [PATCH] hw_breakpoint: remove sample code from hw_breakpoint.h Li Zefan
2009-07-07 21:04 ` Frederic Weisbecker [this message]
2009-07-13 5:28 ` Li Zefan
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=20090707210410.GG6184@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=prasad@linux.vnet.ibm.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.