From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sivasakthi7@outlook.com>
Received: from sam.nabble.com (sam.nabble.com [216.139.236.26])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ozlabs.org (Postfix) with ESMTPS id 21AB81400AF
 for <linuxppc-dev@ozlabs.org>; Mon, 19 May 2014 09:38:13 +1000 (EST)
Received: from tom.nabble.com ([192.168.236.105])
 by sam.nabble.com with esmtp (Exim 4.72)
 (envelope-from <sivasakthi7@outlook.com>) id 1WmAeh-00071z-Ck
 for linuxppc-dev@ozlabs.org; Sun, 18 May 2014 16:38:11 -0700
Date: Sun, 18 May 2014 16:38:11 -0700 (PDT)
From: shiva7 <sivasakthi7@outlook.com>
To: linuxppc-dev@ozlabs.org
Message-ID: <1400456291193-82408.post@n7.nabble.com>
In-Reply-To: <1398206224.1694.254.camel@snotra.buserror.net>
References: <5167457E.1050205@genband.com>
 <1398170592855-81732.post@n7.nabble.com>
 <1398205896.1694.252.camel@snotra.buserror.net>
 <1398206224.1694.254.camel@snotra.buserror.net>
Subject: Re: questions on CONFIG_PPC_ADV_DEBUG_REGS, DBCR0_BRT, and
 DBCR0_ACTIVE_EVENTS
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
List-Id: Linux on PowerPC Developers Mail List <linuxppc-dev.lists.ozlabs.org>
List-Unsubscribe: <https://lists.ozlabs.org/options/linuxppc-dev>,
 <mailto:linuxppc-dev-request@lists.ozlabs.org?subject=unsubscribe>
List-Archive: <http://lists.ozlabs.org/pipermail/linuxppc-dev/>
List-Post: <mailto:linuxppc-dev@lists.ozlabs.org>
List-Help: <mailto:linuxppc-dev-request@lists.ozlabs.org?subject=help>
List-Subscribe: <https://lists.ozlabs.org/listinfo/linuxppc-dev>,
 <mailto:linuxppc-dev-request@lists.ozlabs.org?subject=subscribe>

Thanks Scott.

Apologize for not quoting the old email reference. I assumed the old archive
content always will be in the trail.

Any idea whether the DBCR0 BRT bit actually works(??), if I add  DBCR0 under
sys_debug context call? because this code seems like direct porting and
wondering why on first place not included under debug_context call. 

And also, anything special required for "server" family application code
porting here ?? as because in server family the trace exception used to viz
NORMAL exception proglog and uses SRR0 and SRR1 but in this ISA/embedded
case have dedicated DEBUG_DEBUG prolog and dedicated registers DSRR0 and
DSRR1.

I can see the debug handler already have HACK to simulate the branch taken
case and SIGTRAP to user space.

Thanks in Advance.



--
View this message in context: http://linuxppc.10917.n7.nabble.com/questions-on-CONFIG-PPC-ADV-DEBUG-REGS-DBCR0-BRT-and-DBCR0-ACTIVE-EVENTS-tp70147p82408.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.