This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Enable hw watchpoint with longer ranges using DAWR on Power
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Edjunior Barbosa Machado <emachado at linux dot vnet dot ibm dot com>
- Cc: gdb-patches at sourceware dot org, emachado at linux dot vnet dot ibm dot com, Ulrich dot Weigand at de dot ibm dot com
- Date: Tue, 02 Jul 2013 23:03:00 +0300
- Subject: Re: [PATCH] Enable hw watchpoint with longer ranges using DAWR on Power
- References: <1372786761-29726-1-git-send-email-emachado at linux dot vnet dot ibm dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
> Cc: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>, Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
> Date: Tue, 2 Jul 2013 14:39:21 -0300
>
> The new DAWR interface provided by the next generation of Power processors
> (Power ISA Version 2.07) included in the kernel this year allows gdb to use
> hardware watchpoint with longer ranges (up to 512 bytes wide), which can't cross
> a 512 byte boundary [1]. The patch below enables the usage of this new feature,
> currently exported to the userspace as PPC_DEBUG_FEATURE_DATA_BP_DAWR via struct
> ppc_debug_info [2]. Ok?
Is only one watchpoint of this kind possible at any given time? If
more than one such watchpoint can be used at the same time, I don't
see why we should expose the 512-byte limitation to users. Just use
more than one such watchpoint to cover the range of addresses
requested by the user command.