mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Sat, 12 Dec 2009 14:52:16 +0100	[thread overview]
Message-ID: <20091212135216.GA18597@elte.hu> (raw)
In-Reply-To: <20091212132428.GB22389@elte.hu>


* 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

  reply	other threads:[~2009-12-13  2:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-11 17:19 Jason Wessel
2009-12-12 13:24 ` Ingo Molnar
2009-12-12 13:52   ` Ingo Molnar [this message]
2009-12-12 21:01     ` Jason Wessel
2009-12-30 16:39       ` Frederic Weisbecker
2009-12-30 16:53         ` [RFC] Fix 2.6.33 x86 regression to kgdb hw breakpoints - dueto " Jason Wessel
2009-12-30 18:01           ` Frederic Weisbecker
2010-01-18 20:13             ` [RFC] Fix 2.6.33 x86 regression to kgdb hw breakpoints - duetoperf " Jason Wessel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091212135216.GA18597@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=fweisbec@gmail.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=prasad@linux.vnet.ibm.com \
    --cc=stern@rowland.harvard.edu \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome