mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Will Deacon <will.deacon@arm.com>,
	Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>,
	"K . Prasad" <prasad@linux.vnet.ibm.com>,
	Paul Mundt <lethal@linux-sh.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>
Subject: [RFC PATCH 0/2] hw-breakpoints allocation constraints updates
Date: Tue, 13 Apr 2010 01:01:18 +0200	[thread overview]
Message-ID: <1271113280-10521-1-git-send-regression-fweisbec@gmail.com> (raw)


Hi,

These patches tend to extend the breakpoint allocation constraints to
be more non-x86 friendly.

It can separate the data and instruction breakpoint space and
handle address ranges or other kind of tricky things that makes
a breakpoint use more than one address register.

There is still one kind of constraint it can't handle, something
I've found on ARMv7 implementation: linking an breakpoint to a
watchpoint. But if this needs arises, I will be glad to add that
support.

Beware, it's only compile-tested for now.

Tell me what you think.

Thanks.


Frederic Weisbecker (2):
  hw-breakpoints: Separate constraint space for data and instruction
    breakpoints
  hw-breakpoints: Handle breakpoint weight in allocation constraints

 arch/Kconfig                  |   11 ++++
 arch/x86/Kconfig              |    1 +
 include/linux/hw_breakpoint.h |    9 ++-
 kernel/hw_breakpoint.c        |  129 ++++++++++++++++++++++++++++++-----------
 4 files changed, 112 insertions(+), 38 deletions(-)


             reply	other threads:[~2010-04-12 23:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 23:01 Frederic Weisbecker [this message]
2010-04-12 23:01 ` [RFC PATCH 1/2] hw-breakpoints: Separate constraint space for data and instruction breakpoints Frederic Weisbecker
2010-04-16 14:35   ` Will Deacon
2010-04-16 14:56     ` Frederic Weisbecker
2010-04-12 23:01 ` [RFC PATCH 2/2] hw-breakpoints: Handle breakpoint weight in allocation constraints Frederic Weisbecker

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=1271113280-10521-1-git-send-regression-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahesh@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=prasad@linux.vnet.ibm.com \
    --cc=will.deacon@arm.com \
    /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

all inboxes | Powered by JetHome®