mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Benjamin Herrenschmidt <benh@au1.ibm.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Maneesh Soni <maneesh@in.ibm.com>,
	Roland McGrath <roland@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: [Patch 00/11] Hardware Breakpoint Interfaces - v5
Date: Fri, 20 Mar 2009 05:17:34 +0530	[thread overview]
Message-ID: <20090319234734.GA10517@in.ibm.com> (raw)

Hi Ingo,
	Please find the new set of patches that implement Hardware
breakpoint interfaces for kernel- and user-space, an ftrace plugin using these
interfaces to trace memory accesses over kernel symbols and a demonstrative
example.

While a previous version of these patches was posted
here: http://lkml.org/lkml/2009/3/7/23 and generated substantial amount of
discussions over LKML, a summary of proposed changes to the patchset was posted
here: http://lkml.org/lkml/2009/3/13/381.

In short, the infrastructure has been changed to provide interfaces to use
Hardware Breakpoint (or Watchpoint) registers on a first-come first-serve basis
(without over-committing resources). The serviced-requests are maintained in an
array of pointers to the register's datastructure. Requests from kernel-space
will be serviced in decreasing order of register numbers (starting from
HB_NUM - 1).

The ksym_tracer ftrace plugin now also contains a startup self-test and support
for showing aggregate counters (through ftrace's histogram infrastructure).

Kindly let me know if the new patchset addresses the concerns of the community
and is deemed fit for inclusion in -tip tree. The patchset is based on commit
62f84ea922bd60803e446153ea99ce5d7245d6f9 of -tip tree.

Thanks,
K.Prasad


                 reply	other threads:[~2009-03-19 23:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090319234734.GA10517@in.ibm.com \
    --to=prasad@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=benh@au1.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.com \
    --cc=mingo@elte.hu \
    --cc=roland@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=stern@rowland.harvard.edu \
    /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®