[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091017234250.GC10344@nowhere>
Date: Sun, 18 Oct 2009 01:42:53 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Paul Mundt <lethal@...ux-sh.org>
Cc: "K.Prasad" <prasad@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...e.hu>,
Alan Stern <stern@...land.harvard.edu>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH -tip] x86: hw-breakpoints: Actually flush thread
breakpoints in flush_thread().
On Fri, Oct 09, 2009 at 12:40:04PM +0900, Paul Mundt wrote:
> On Mon, Oct 05, 2009 at 04:19:55PM +0530, K.Prasad wrote:
> > On Mon, Oct 05, 2009 at 07:23:06PM +0900, Paul Mundt wrote:
> > > [ I noticed this whilst hacking up SH support, applies to the current
> > > tracing/hw-breakpoints topic branch. ]
> > >
> > > flush_thread() tries to do a TIF_DEBUG check before calling in to
> > > flush_thread_hw_breakpoint() (which subsequently clears the thread flag),
> > > but for some reason, the x86 code is manually clearing TIF_DEBUG
> > > immediately before the test, so this path will never be taken.
> > >
> > > This kills off the erroneous clear_tsk_thread_flag() and lets
> > > flush_thread_hw_breakpoint() actually get invoked.
> > >
> >
> > Yes, this is wrong and we missed it. Thanks for fixing!
> >
> > > Presumably folks were getting lucky with testing and the
> > > free_thread_info() -> free_thread_xstate() path was taking care of the
> > > flush there.
> > >
> > > Signed-off-by: Paul Mundt <lethal@...ux-sh.org>
> >
> > Acked-by: K.Prasad <prasad@...ux.vnet.ibm.com>
> >
> >
> Ingo, are you planning on picking this up? Or is there a hw-breakpoints
> tree somewhere outside of -tip that I'm unaware of?
I'm picking it.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists