Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix hardware watchpoints on PowerPC servers
Date: Fri, 17 May 2013 23:09:00 -0000	[thread overview]
Message-ID: <5196B8B3.8090607@linux.vnet.ibm.com> (raw)
In-Reply-To: <5190F5D8.3050108@linux.vnet.ibm.com>

On 05/13/2013 11:16 AM, Edjunior Barbosa Machado wrote:
> On 05/13/2013 10:19 AM, Ulrich Weigand wrote:
>> So the kernel now reports it supports PPC_DEBUG_FEATURE_DATA_BP_RANGE,
>> but then rejects any attempt to set a range BP of more than 8 bytes?
>> And there's no way to check for this ahead of time except for checking
>> the BookE hwcaps bits?   That seems unfortunate ...
>>
>> But I guess if that's the way the kernel interface is now, we'll have to
>> add that check.
> 
> Yes, unfortunately this is the info we have from the kernel interface.
> booke_debug_info.data_bp_alignment informs the alignment, which, in the
> case of current bookS processors, is also the max length for the
> watchpoint (8 bytes).
> 
>>
>>> 	* ppc-linux-nat.c (ppc_linux_region_ok_for_hw_watchpoint): Check if the
>>> 	region is ok for a hardware watchpoint using the new ptrace interface
>>> 	on Power servers.
>>
>> This is OK.
>>
>> As noted by Luis, it would be good to rename the "booke" terminology,
>> maybe using something like "have_ptrace_hwdebug" instead of
>> have_ptrace_booke_interface.  But that should be a separate patch.
> 
> I'll work on a patch following these suggestions you and Luis mentioned.
> 
> Thanks for the feedback, Ulrich.
> 

Checked in: http://sourceware.org/ml/gdb-cvs/2013-05/msg00146.html

Thanks.
-- 
Edjunior


      reply	other threads:[~2013-05-17 23:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13  6:29 Edjunior Barbosa Machado
2013-05-13  7:08 ` Luis Machado
2013-05-13 14:16   ` Edjunior Barbosa Machado
2013-05-13 13:19 ` Ulrich Weigand
2013-05-13 14:17   ` Edjunior Barbosa Machado
2013-05-17 23:09     ` Edjunior Barbosa Machado [this message]

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=5196B8B3.8090607@linux.vnet.ibm.com \
    --to=emachado@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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