From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: emachado@linux.vnet.ibm.com
Cc: gdb-patches@sourceware.org, mark.kettenis@xs4all.nl,
prasad@linux.vnet.ibm.com
Subject: Re: [PATCH] disable ptrace BookE interface for PowerPC server processors
Date: Tue, 29 May 2012 18:54:00 -0000 [thread overview]
Message-ID: <201205291854.q4TIsH0i008399@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <4FBF0153.4060108@linux.vnet.ibm.com> (message from Edjunior Barbosa Machado on Fri, 25 May 2012 00:49:39 -0300)
> 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 ;)
> gdb/
> 2012-25-05 Edjunior Machado <emachado@linux.vnet.ibm.com>
>
> * ppc-linux-nat.c (have_ptrace_booke_interface): disable ptrace booke
> interface for powerpc server processors if not available in kernel.
>
> diff --git a/gdb/ppc-linux-nat.c b/gdb/ppc-linux-nat.c
> index 34c40b4..9ffcf88 100644
> --- a/gdb/ppc-linux-nat.c
> +++ b/gdb/ppc-linux-nat.c
> @@ -1421,17 +1421,18 @@ have_ptrace_booke_interface (void)
> /* Check for kernel support for BOOKE debug registers. */
> if (ptrace (PPC_PTRACE_GETHWDBGINFO, tid, 0, &booke_debug_info) >= 0)
> {
> - have_ptrace_booke_interface = 1;
> - max_slots_number = booke_debug_info.num_instruction_bps
> - + booke_debug_info.num_data_bps
> - + booke_debug_info.num_condition_regs;
> - }
> - else
> - {
> - /* Old school interface and no BOOKE debug registers support. */
> - have_ptrace_booke_interface = 0;
> - memset (&booke_debug_info, 0, sizeof (struct ppc_debug_info));
> + if (booke_debug_info.features)
> + {
> + have_ptrace_booke_interface = 1;
> + max_slots_number = booke_debug_info.num_instruction_bps
> + + booke_debug_info.num_data_bps
> + + booke_debug_info.num_condition_regs;
> + return have_ptrace_booke_interface;
> + }
> }
> + /* Old school interface and no BOOKE debug registers support. */
> + have_ptrace_booke_interface = 0;
> + memset (&booke_debug_info, 0, sizeof (struct ppc_debug_info));
> }
>
> return have_ptrace_booke_interface;
>
>
next prev parent reply other threads:[~2012-05-29 18:54 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 [this message]
2012-05-30 4:17 ` Edjunior Barbosa Machado
2012-05-30 15:31 ` Mark Kettenis
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=201205291854.q4TIsH0i008399@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