From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16066 invoked by alias); 21 Apr 2008 22:38:54 -0000 Received: (qmail 16057 invoked by uid 22791); 21 Apr 2008 22:38:53 -0000 X-Spam-Check-By: sourceware.org Received: from smtp1.dnsmadeeasy.com (HELO smtp1.dnsmadeeasy.com) (205.234.170.144) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 21 Apr 2008 22:38:33 +0000 Received: from smtp1.dnsmadeeasy.com (localhost [127.0.0.1]) by smtp1.dnsmadeeasy.com (Postfix) with ESMTP id 3163F318DA1; Mon, 21 Apr 2008 22:40:10 +0000 (UTC) X-Authenticated-Name: js.dnsmadeeasy X-Transit-System: In case of SPAM please contact abuse@dnsmadeeasy.com Received: from avtrex.com (unknown [67.116.42.147]) by smtp1.dnsmadeeasy.com (Postfix) with ESMTP; Mon, 21 Apr 2008 22:40:10 +0000 (UTC) Received: from dl2.hq2.avtrex.com ([192.168.7.26]) by avtrex.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 21 Apr 2008 15:38:29 -0700 Message-ID: <480D1763.10601@avtrex.com> Date: Tue, 22 Apr 2008 03:25:00 -0000 From: David Daney User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: "Maciej W. Rozycki" Cc: gdb-patches@sourceware.org Subject: Re: RFC: Hardware watchpoint register support for mips-linux. References: <480CEC37.9060202@avtrex.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: 2008-04/txt/msg00459.txt.bz2 Maciej W. Rozycki wrote: > > Well done! -- something I have meant to do for years, but never come to. > Out of curiousity -- does your kernel side support MIPS architecture style > watchpoints only or does it work with the R4000-style watch registers as > well? I recall having a discussion with Daniel about how to support both > in a reasonably abstract way long ago. Either way thanks a lot, and I > have an R4k machine handy, so I can see if I find some time to give it a > shot. > Currently it only handles mips32 style watch registers. I have no documentation on the R4000 style registers. I do however have an SGI Indy w/ R4400 which /proc/cpuinfo reports as having watch registers, but since there is a lack of documentation, I could not try it. My plan for supporting different watch register formats is to have a format identifier that is read by GDB via PTRACE_GET_WATCH_REGS. The rest of the information is a union of the known formats. Currently it reports the number of registers and the active mask bits. But if R4000 does not fit with the mips32 register layout, its registers would be layed out in a different union member. I hope that makes sense. David Daney