From: Eli Zaretskii <eliz@gnu.org>
To: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org, emachado@linux.vnet.ibm.com,
Ulrich.Weigand@de.ibm.com
Subject: Re: [PATCH] Enable hw watchpoint with longer ranges using DAWR on Power
Date: Tue, 02 Jul 2013 20:03:00 -0000 [thread overview]
Message-ID: <83ip0sbuh7.fsf@gnu.org> (raw)
In-Reply-To: <1372786761-29726-1-git-send-email-emachado@linux.vnet.ibm.com>
> 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.
next prev parent reply other threads:[~2013-07-02 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 17:40 Edjunior Barbosa Machado
2013-07-02 17:59 ` Luis Machado
2013-07-02 18:04 ` Ulrich Weigand
2013-07-02 20:03 ` Eli Zaretskii [this message]
2013-07-02 21:02 ` Edjunior Barbosa Machado
2013-07-16 14:13 ` Edjunior Barbosa Machado
2013-07-22 13:19 ` Ulrich Weigand
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=83ip0sbuh7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox