Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761139AbXEKPZZ (ORCPT ); Fri, 11 May 2007 11:25:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756662AbXEKPZR (ORCPT ); Fri, 11 May 2007 11:25:17 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:54424 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1755653AbXEKPZQ (ORCPT ); Fri, 11 May 2007 11:25:16 -0400 Date: Fri, 11 May 2007 11:25:14 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Roland McGrath cc: Prasanna S Panchamukhi , Kernel development list Subject: Re: [RFC] hwbkpt: Hardware breakpoints (was Kwatch) In-Reply-To: <20070328213951.BCD5B1801C4@magilla.sf.frob.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 868 Lines: 22 On Wed, 28 Mar 2007, Roland McGrath wrote: > Sorry I've been slow in responding to your most recent version. > I fell into a large hole and couldn't get out until I fixed some bugs. Has the same thing happened again? There hasn't been any feedback on the most recent version of hw_breakpoint emailed on April 13: http://marc.info/?l=linux-kernel&m=117661223820357&w=2 I think there are probably still a few small things wrong with it. For instance, the RF setting isn't right; I misunderstood the Intel manual. It should get set only when the latest debug interrupt was for an instruction breakpoint. Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/