Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: emachado@linux.vnet.ibm.com
Cc: mark.kettenis@xs4all.nl, gdb-patches@sourceware.org,
	       prasad@linux.vnet.ibm.com
Subject: Re: [PATCH] disable ptrace BookE interface for PowerPC server processors
Date: Wed, 30 May 2012 15:31:00 -0000	[thread overview]
Message-ID: <201205301531.q4UFVC2D030735@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <4FC59F24.1060907@linux.vnet.ibm.com> (message from Edjunior	Barbosa Machado on Wed, 30 May 2012 01:16:36 -0300)

> Date: Wed, 30 May 2012 01:16:36 -0300
> From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
> CC: gdb-patches@sourceware.org, prasad@linux.vnet.ibm.com
> X-Content-Scanned: Fidelis XPS MAILER
> x-cbid: 12053004-2362-0000-0000-00000750AC06
> X-XS4ALL-DNSBL-Checked: mxdrop221.xs4all.nl checked 32.104.18.26 against DNS blacklists
> X-CNFS-Analysis: v=2.0 cv=ZbOqwLpA c=1 sm=0 a=nuFXaNQDUkPZN5VKAd7j+w==:17
> 	a=kUSHYda-BbMA:10 a=sYXyRZcBhIwA:10 a=-oxz3-EH24EA:10
> 	a=8nJEP1OIZ-IA:10 a=9tSwX7uLV1UA:10 a=VnNF1IyMAAAA:8
> 	a=d0wQilHS6ga4fH6NGAsA:9 a=wPNLvfGTeEIA:10
> 	a=nuFXaNQDUkPZN5VKAd7j+w==:117
> X-Virus-Scanned: by XS4ALL Virus Scanner
> X-XS4ALL-Spam-Score: 0.0 () none
> X-XS4ALL-Spam: NO
> Envelope-To: mark.kettenis@xs4all.nl
> 
> On 05/29/2012 03:54 PM, Mark Kettenis wrote:
> 
> >> Date: Fri, 25 May 2012 00:49:39 -0300
> >> From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
> >>
> >> On 05/22/2012 02:34 PM, Mark Kettenis wrote:
> >>
> >>> But how are you going to handle this when that functionality does
> >>> become available?  
> >>
> >>
> >> Thanks for the feedback and sorry for the late reply. I was discussing
> >> with the kernel developer responsible for the next version of the ptrace
> >> booke interface and he proposed that the 'features' field from the
> >> struct ppc_debug_info returned by ptrace PPC_PTRACE_GETHWDBGINFO call
> >> could be used to check if its availability. According to him, this field
> >> is currently 0 for servers, but once the new ptrace interface becomes
> >> functional, it will return the flag PPC_DEBUG_FEATURE_DATA_BP_RANGE
> >> enabled. Moreover, this change will not affect the behavior on embedded
> >> processors (which already has PPC_DEBUG_FEATURE_DATA_BP_RANGE and
> >> PPC_DEBUG_FEATURE_DATA_BP_MASK enabled).
> >>
> >> Please consider the new version of the patch below.
> > 
> > Certainly makes more sense to me ;)
> 
> 
> which means this is ok to apply? :)

Fine with me, but I've never (knowingly) used Linux on
POWER/PowerPC/PowerISA ;).


  reply	other threads:[~2012-05-30 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 15:24 Edjunior Barbosa Machado
2012-05-22 17:34 ` Mark Kettenis
2012-05-25  3:50   ` Edjunior Barbosa Machado
2012-05-29 18:54     ` Mark Kettenis
2012-05-30  4:17       ` Edjunior Barbosa Machado
2012-05-30 15:31         ` Mark Kettenis [this message]
2012-05-31 20:56     ` Sergio Durigan Junior
2012-05-31 22:09       ` Edjunior Barbosa Machado

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=201205301531.q4UFVC2D030735@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=emachado@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=prasad@linux.vnet.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