All of lore.kernel.org
 help / color / mirror / Atom feed
From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Roland McGrath <roland@redhat.com>,
	akpm@linux-foundation.org, mingo@elte.hu,
	richardj_moore@uk.ibm.com
Subject: Re: [RFC Patch 0/9] Hardware Breakpoint interfaces - v2
Date: Fri, 5 Dec 2008 00:47:58 +0530	[thread overview]
Message-ID: <20081204191758.GJ20563@in.ibm.com> (raw)
In-Reply-To: <20081204190804.GA15134@in.ibm.com>

On Fri, Dec 05, 2008 at 12:38:05AM +0530, K.Prasad wrote:
> Hi All,
> 	Please find the latest set of patches that introduce kernel
> interfaces to use Hardware Breakpoint registers and an implementation
> for x86 (and x86_64) architecture.
> 
> The patches have undergone changes to incorporate the suggestions for
> the previous patchset - including removal of support for instruction
> breakpoint, and are based off 2.6.28-rc7. The patches have been tested
> on x86 architecture along with kprobes, however they're posted as RFC
> owing to the many pending tasks (refer
> http://lkml.org/lkml/2008/10/7/127 for details).
> 
> Thanks,
> K.Prasad
>
Oops...the title should have read: [RFC Patch 0/9] Hardware Breakpoint
interfaces - v3
 

  parent reply	other threads:[~2008-12-04 19:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 19:08 [RFC Patch 0/9] Hardware Breakpoint interfaces - v2 K.Prasad
2008-12-04 19:11 ` [RFC Patch 1/9] Introducing generic hardware breakpoint handler interfaces K.Prasad
2008-12-04 19:38   ` David Daney
2008-12-17  3:47     ` K.Prasad
2008-12-04 19:11 ` [RFC Patch 2/9] x86 architecture implementation of Hardware Breakpoint interfaces K.Prasad
2008-12-04 19:12 ` [RFC Patch 3/9] Modifying generic debug exception to use virtual debug registers K.Prasad
2008-12-04 19:13 ` [RFC Patch 4/9] Modify kprobe exception handler to recognise single-stepping by HW Breakpoint handler K.Prasad
2008-12-04 19:13 ` [RFC Patch 5/9] Use wrapper routines around debug registers in processor related functions K.Prasad
2008-12-04 19:13 ` [RFC Patch 6/9] Use virtual debug registers in process/thread handling code K.Prasad
2008-12-04 19:14 ` [RFC Patch 7/9] Modify signal handling code to refrain from re-enabling HW Breakpoints K.Prasad
2008-12-04 19:16 ` [RFC Patch 8/9] Modify Ptrace routines to access breakpoint registers K.Prasad
2008-12-04 19:17 ` [RFC Patch 9/9] Cleanup HW Breakpoint registers before kexec K.Prasad
2008-12-04 19:17 ` K.Prasad [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-08 19:20 [RFC Patch 0/9] Hardware Breakpoint interfaces - v2 K.Prasad

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=20081204191758.GJ20563@in.ibm.com \
    --to=prasad@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=richardj_moore@uk.ibm.com \
    --cc=roland@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.