linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "K.Prasad" <prasad@linux.vnet.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [RFC Patch 2/2][Bugfix][x86][hw-breakpoint] Fix return-code to notifier chain in hw_breakpoint_handler
Date: Fri, 22 Jan 2010 14:51:27 +0530	[thread overview]
Message-ID: <20100122092127.GB7127@in.ibm.com> (raw)
In-Reply-To: <4B596C8E.2020600@siemens.com>

On Fri, Jan 22, 2010 at 10:14:54AM +0100, Jan Kiszka wrote:
> K.Prasad wrote:
> > On Sun, Jan 17, 2010 at 01:10:58AM +0530, K.Prasad wrote:
> >> On Mon, Jan 11, 2010 at 08:15:29PM +0100, Jan Kiszka wrote:
> >>> Frederic Weisbecker wrote:
> >>>> On Fri, Jan 01, 2010 at 12:32:17AM +0530, K.Prasad wrote:
> >>>>> On Thu, Dec 31, 2009 at 01:38:09AM +0100, Frederic Weisbecker wrote:
> >>>>>> On Sat, Dec 26, 2009 at 11:58:33PM +0530, K.Prasad wrote:
> >>>>>>> The hw-breakpoint handler will return NOTIFY_DONE for user-space breakpoints
> >>>>>>> to generate SIGTRAP signal (and not for kernel-space addresses). 
> >>>>>>>
<snipped>
> >> Such a behaviour shouldn't be affected by the above change...your
> >> confirmation would help!
> >>
> > 
> > Hi Jan,
> > 	I presume that the above explanation makes the role of this
> > patch/bugfix clear.
> > 
> > Kindly let me know if you have any further queries.
> > 
> 
> Nope. There should be really no conflicts of your optimization with kvm.
> 
> Jan
> 
> -- 

Hi Jan,
	Thanks for the confirmation.

Hi Frederic,
	Can you pull these fixes in? (LKML references:
20091226182725.GB9494@in.ibm.com and 20091226182833.GC9494@in.ibm.com).

Thanks,
K.Prasad


  reply	other threads:[~2010-01-22  9:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091226175533.149765731@linux.vnet.ibm.com>
2009-12-26 18:27 ` [RFC Patch 1/2][Bugfix][x86][hw-breakpoint] Clear reserved bits of DR6 in do_debug() K.Prasad
2009-12-30 23:45   ` Frederic Weisbecker
2009-12-31 18:49     ` K.Prasad
2010-01-10  3:22       ` Frederic Weisbecker
2009-12-26 18:28 ` [RFC Patch 2/2][Bugfix][x86][hw-breakpoint] Fix return-code to notifier chain in hw_breakpoint_handler K.Prasad
2009-12-31  0:33   ` Frederic Weisbecker
2009-12-31  0:38   ` Frederic Weisbecker
2009-12-31 19:02     ` K.Prasad
2010-01-10  3:18       ` Frederic Weisbecker
2010-01-11 19:15         ` Jan Kiszka
2010-01-16 19:41           ` K.Prasad
2010-01-20  6:01             ` K.Prasad
2010-01-22  9:14               ` Jan Kiszka
2010-01-22  9:21                 ` K.Prasad [this message]
2010-01-25 22:21                   ` Frederic Weisbecker
2010-01-27 10:29                     ` K.Prasad
2009-12-31  0:44   ` Frederic Weisbecker
2010-01-25 22:11   ` Frederic Weisbecker
2010-01-27 10:28     ` K.Prasad
2010-01-27 16:11       ` 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=20100122092127.GB7127@in.ibm.com \
    --to=prasad@linux.vnet.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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;
as well as URLs for NNTP newsgroup(s).