From: David Daney <ddaney@avtrex.com>
To: linux-mips@linux-mips.org
Cc: linux-kernel@vger.kernel.org
Subject: [Patch 1/6] MIPS: Add HARDWARE_WATCHPOINTS configure option.
Date: Wed, 10 Sep 2008 22:37:42 -0700 [thread overview]
Message-ID: <48C8AEA6.6060901@avtrex.com> (raw)
In-Reply-To: <48C8ADEF.9020305@avtrex.com>
Add HARDWARE_WATCHPOINTS configure option.
This is automatically set for all MIPS32 and MIPS64 processors.
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 49896a2..7c724ea 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -1272,6 +1272,13 @@ config CPU_SUPPORTS_32BIT_KERNEL
config CPU_SUPPORTS_64BIT_KERNEL
bool
+#
+# Set to y for ptrace access to watch registers.
+#
+config HARDWARE_WATCHPOINTS
+ bool
+ default y if CPU_MIPS32 || CPU_MIPS64
+
menu "Kernel type"
choice
--
1.5.5.1
next prev parent reply other threads:[~2008-09-11 5:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 5:34 [Patch 0/6] MIPS: Hardware watch register support for gdb (version 4) David Daney
2008-09-11 5:37 ` David Daney [this message]
2008-09-11 5:55 ` [Patch 2/6] MIPS: Add HARDWARE_WATCHPOINTS definitions and support code David Daney
2008-09-11 7:27 ` Geert Uytterhoeven
2008-09-11 15:05 ` David Daney
2008-09-11 5:57 ` [Patch 3/6] MIPS: Probe watch registers and report configuration David Daney
2008-09-11 5:59 ` [Patch 4/6] MIPS: Watch exception handling for HARDWARE_WATCHPOINTS David Daney
2008-09-11 6:01 ` [Patch 5/6] MIPS: Scheduler support " David Daney
2008-09-11 6:04 ` [Patch 6/6] MIPS: Ptrace " David Daney
-- strict thread matches above, loose matches on Subject: below --
2008-09-23 7:02 Patch 0/6] MIPS: Hardware watch register support for gdb (version 5) David Daney
2008-09-23 7:04 ` [Patch 1/6] MIPS: 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=48C8AEA6.6060901@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.