From: David Daney <ddaney@avtrex.com>
To: linux-mips@linux-mips.org
Cc: linux-kernel@vger.kernel.org
Subject: [Patch 1/6] Add HARDWARE_WATCHPOINTS configure option.
Date: Mon, 21 Apr 2008 17:01:03 -0700 [thread overview]
Message-ID: <480D2ABF.5000005@avtrex.com> (raw)
In-Reply-To: <480D2151.2020701@avtrex.com>
This first patch just adds the HARDWARE_WATCHPOINTS option to the
'Kernel type' menu. If N, the watch register support is disabled.
Signed-off-by: David Daney <ddaney@avtrex.com>
---
arch/mips/Kconfig | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 8724ed3..98f46f6 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -1622,6 +1622,13 @@ config CPU_HAS_SMARTMIPS
you don't know you probably don't have SmartMIPS and should say N
here.
+config HARDWARE_WATCHPOINTS
+ bool "Debugger support for hardware watchpoints"
+ depends on (CPU_MIPS32 || CPU_MIPS64)
+ help
+ Saying yes here allows you to utilize the hardware watchpoint
+ registers. Most people should say Y here.
+
config CPU_HAS_WB
bool
--
1.5.5
next prev parent reply other threads:[~2008-04-22 0:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 23:20 [Patch 0/6] MIPS Hardware watchpoint support for gdb David Daney
2008-04-22 0:01 ` David Daney [this message]
2008-04-22 0:10 ` [Patch 2/6] Add HARDWARE_WATCHPOINTS definitions and support code David Daney
2008-04-22 0:15 ` [Patch 3/6] Probe watch registers and report configuration David Daney
2008-04-22 0:21 ` [Patch 4/6] Watch trap handling for HARDWARE_WATCHPOINTS David Daney
2008-04-22 0:33 ` [Patch 5/6] Scheduler support " David Daney
2008-04-22 0:40 ` [Patch 6/6] Ptrace " David Daney
2008-04-22 16:23 ` Daniel Jacobowitz
2008-04-22 18:26 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2008-04-29 1:21 [Patch 0/6] MIPS Hardware watchpoint support for gdb (version 2) David Daney
2008-04-29 1:29 ` [PATCH 1/6] Add HARDWARE_WATCHPOINTS configure option David Daney
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=480D2ABF.5000005@avtrex.com \
--to=ddaney@avtrex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
/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.