Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: lgustavo@codesourcery.com
Cc: emachado@linux.vnet.ibm.com (Edjunior Barbosa Machado),
	       gdb-patches@sourceware.org,
	Ulrich.Weigand@de.ibm.com (Ulrich Weigand)
Subject: Re: [PATCH] Enable hw watchpoint with longer ranges using DAWR on Power
Date: Tue, 02 Jul 2013 18:04:00 -0000	[thread overview]
Message-ID: <201307021804.r62I4WBg017601@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <51D31512.7020005@codesourcery.com> from "Luis Machado" at Jul 02, 2013 02:59:46 PM

Luis Machado wrote:
> On 07/02/2013 02:39 PM, Edjunior Barbosa Machado wrote:
> > gdb/ChangeLog
> > 2013-07-02  Edjunior Barbosa Machado  <emachado@linux.vnet.ibm.com>
> >
> > 	* ppc-linux-nat.c (PPC_DEBUG_FEATURE_DATA_BP_DAWR): New define.
> > 	(ppc_linux_region_ok_for_hw_watchpoint): Add checking to use the new
> > 	DAWR interface for longer ranges hardware watchpoint (up to 512 bytes).

This looks good to me too, but we should indeed probably sort out
the booke renaming first :-)

> > +#ifndef PPC_DEBUG_FEATURE_DATA_BP_DAWR
> > +#define PPC_DEBUG_FEATURE_DATA_BP_DAWR	0x10
> > +#endif /* PPC_DEBUG_FEATURE_DATA_BP_DAWR */
> >
> 
> Are older kernels/libraries that don't define these constants going to 
> be used with these POWER processors in the future? If not, maybe they 
> can be dropped instead of forcing their definitions here.

In general, we usually always provide such defines.  There should be
no harm in doing so, since this is kernel ABI that will never change,
so it is fine to just use the well-known binary value ...

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2013-07-02 18:04 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 [this message]
2013-07-02 20:03 ` Eli Zaretskii
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=201307021804.r62I4WBg017601@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=emachado@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.com \
    /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