Date: Sat, 12 Dec 2009 14:52:16 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, Paul Mackerras <paulus@samba.org>,
       Frederic Weisbecker <fweisbec@gmail.com>,
       lkml <linux-kernel@vger.kernel.org>,
       Alan Stern <stern@rowland.harvard.edu>,
       "K.Prasad" <prasad@linux.vnet.ibm.com>,
       Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] Fix 2.6.33 x86 regression to kgdb hw breakpoints - due to
 perf API changes
Message-ID: <20091212135216.GA18597@elte.hu>
References: <4B227F2C.7050403@windriver.com>
 <20091212132428.GB22389@elte.hu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091212132428.GB22389@elte.hu>
User-Agent: Mutt/1.5.20 (2009-08-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 845
Lines: 29


* Ingo Molnar <mingo@elte.hu> wrote:

> Hm, the kgdb hw-breakpoint changes freshly put into v2.6.33 look 
> pretty broken: [...]

Sorry - i thought for a moment that it was introduced by this recent 
change:

  7f8b7ed: kgdb: Always process the whole breakpoint list on activate or deactivate

but it's deeper than that indeed.

Basically we have two options:

 A- change kgdb to use the hw-breakpoints highlevel APIs (i'd prefer 
    that)

 B- or keep what we had so far: kgdb overrides existing GDB (and now 
    perf) breakpoints

I havent noticed that hw-breakpoints lock up under kgdb.

	Ingo
--
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/