From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9356 invoked by alias); 22 May 2012 17:34:25 -0000 Received: (qmail 9080 invoked by uid 22791); 22 May 2012 17:34:23 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO glazunov.sibelius.xs4all.nl) (83.163.83.176) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 22 May 2012 17:34:09 +0000 Received: from glazunov.sibelius.xs4all.nl (kettenis@localhost [127.0.0.1]) by glazunov.sibelius.xs4all.nl (8.14.5/8.14.3) with ESMTP id q4MHY2Pk032046; Tue, 22 May 2012 19:34:02 +0200 (CEST) Received: (from kettenis@localhost) by glazunov.sibelius.xs4all.nl (8.14.5/8.14.3/Submit) id q4MHY0FQ014975; Tue, 22 May 2012 19:34:00 +0200 (CEST) Date: Tue, 22 May 2012 17:34:00 -0000 Message-Id: <201205221734.q4MHY0FQ014975@glazunov.sibelius.xs4all.nl> From: Mark Kettenis To: emachado@linux.vnet.ibm.com CC: gdb-patches@sourceware.org, emachado@linux.vnet.ibm.com In-reply-to: <1337700251-9366-1-git-send-email-emachado@linux.vnet.ibm.com> (message from Edjunior Barbosa Machado on Tue, 22 May 2012 12:24:11 -0300) Subject: Re: [PATCH] disable ptrace BookE interface for PowerPC server processors References: <1337700251-9366-1-git-send-email-emachado@linux.vnet.ibm.com> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-05/txt/msg00838.txt.bz2 > From: Edjunior Barbosa Machado > Date: Tue, 22 May 2012 12:24:11 -0300 > > Hi, > > the ptrace BookE interface originally implemented only for embedded systems > should be available for Power servers processors as well shortly [1]. > However, while this is not usable in upstream kernel, gdb should enforce > the usage of the old ptrace mechanism (using PTRACE_SET_DEBUGREG) on > servers, even if BookE debug registers are reported as available. But how are you going to handle this when that functionality does become available?