From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Alan Stern <stern@rowland.harvard.edu>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: [Patch 0/3] [Patch 0/3] HW-BKPT: Introduce new features to the hw-breakpoint infrastructure - ver II
Date: Sat, 29 Aug 2009 00:48:01 +0530 [thread overview]
Message-ID: <20090828191801.GA11063@in.ibm.com> (raw)
Hi All,
Please find a set of patches that implement the features listed
below, the previous version of which was posted here:
http://lkml.org/lkml/2009/8/26/477
Patch 1/2: Allow per-cpu kernel-space Hardware Breakpoint requests
Patch 2/2: Allow kernel breakpoints to be modified through a new API
Patch 3/3: Allow breakpoints to be enabled/disabled without yielding the
breakpoint request through a new API - enable_hw_breakpoint().
Changelog ver II
-----------------
- Fixed a potential race between updation of per-cpu kernel-space breakpoint
structures and a concurrent breakpoint exception by disabling breakpoints
in remove_each_cpu_kernel_hbp() through a new function
arch_disable_hw_breakpoint().
- Change the data-type of 'enabled' member in 'struct hw_breakpoint' to 'bool'.
- Split the enable_hw_breakpoint() interface to bring a counterpart in
disable_hw_breakpoint().
- Modify stale/incorrect comments.
- Code updated to commit 1468c4ea3af77ac75de7aae80a44522ff5d0d6c5 of
-tip tree.
Thanks,
K.Prasad
reply other threads:[~2009-08-28 19:18 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=20090828191801.GA11063@in.ibm.com \
--to=prasad@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ananth@in.ibm.com \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--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®