From: Ingo Molnar <mingo@elte.hu>
To: prasad@linux.vnet.ibm.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Roland McGrath <roland@redhat.com>
Subject: Re: [patch 00/11] Hardware Breakpoint interfaces
Date: Tue, 10 Mar 2009 14:46:55 +0100 [thread overview]
Message-ID: <20090310134655.GA3850@elte.hu> (raw)
In-Reply-To: <20090305043726.GA17747@in.ibm.com>
* prasad@linux.vnet.ibm.com <prasad@linux.vnet.ibm.com> wrote:
> Hi Ingo,
> Please find the revised set of patches that implement
> Hardware Breakpoint (or watchpoint) registers and an
> arch-specific implementation for x86/x86_64.
General structure looks good, with a good deal of details
that need to be addressed.
Firstly, as far as i can see this should work on 32-bit too,
correct?
Secondly, what about other architectures - will they build just
fine without any arch level glue code? kernel/hw_breakpoint.o
get build unconditionally - without any benefit to non-x86 code.
Perhaps an ARCH_HAS_HW_BREAKPOINTS Kconfig method would be
useful to add.
There's also a number of (small) style issues.
kernel/hw_breakpoint.c and other new .c files dont comply to the
customary comment style of:
/*
* Comment .....
* ...... goes here:
*/
also, the #include files section style should match that of
arch/x86/mm/fault.c - it's a conflict-avoidance style.
also, things like this:
static struct notifier_block hw_breakpoint_exceptions_nb = {
.notifier_call = hw_breakpoint_exceptions_notify,
.priority = 0x7fffffff /* we need to be notified first */
};
should be:
static struct notifier_block hw_breakpoint_exceptions_nb = {
.notifier_call = hw_breakpoint_exceptions_notify,
/* We need to be notified first: */
.priority = 0x7fffffff,
};
Ingo
next prev parent reply other threads:[~2009-03-10 13:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 4:37 [patch 00/11] Hardware Breakpoint interfaces prasad
2009-03-10 13:46 ` Ingo Molnar [this message]
2009-03-11 12:11 ` K.Prasad
2009-03-11 16:34 ` Alan Stern
2009-03-11 17:25 ` K.Prasad
2009-03-11 17:30 ` Ingo Molnar
2009-03-10 13:51 ` Ingo Molnar
2009-03-10 14:24 ` Alan Stern
2009-03-10 14:54 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-03-07 5:04 [Patch 00/11] Hardware Breakpoint Interfaces prasad
2009-03-24 15:24 [Patch 00/11] Hardware Breakpoint interfaces K.Prasad
2009-03-25 19:48 ` Alan Stern
2009-03-27 22:06 ` K.Prasad
2009-04-01 16:16 ` Alan Stern
2009-04-07 8:22 ` K.Prasad
2009-04-09 20:50 ` Alan Stern
2009-03-28 8:46 ` K.Prasad
2009-04-01 16:22 ` Alan Stern
2009-04-07 8:22 ` K.Prasad
2009-04-07 6:34 K.Prasad
2009-04-16 21:19 ` Alan Stern
2009-04-17 3:12 ` K.Prasad
2009-04-17 14:37 ` Alan Stern
2009-04-24 5:56 ` K.Prasad
2009-04-24 14:16 ` Alan Stern
2009-04-24 15:57 ` K.Prasad
2009-04-24 16:16 ` Alan Stern
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=20090310134655.GA3850@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prasad@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox