public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: Re: [PATCH][RFC] tracing: Use class->reg() for all registering of events
Date: Wed, 9 Jun 2010 09:02:24 -0300	[thread overview]
Message-ID: <20100609120224.GA8359@ghostprotocols.net> (raw)
In-Reply-To: <1276084414.2046.1335.camel@twins>

Em Wed, Jun 09, 2010 at 01:53:34PM +0200, Peter Zijlstra escreveu:
> On Wed, 2010-06-09 at 17:17 +0530, Srikar Dronamraju wrote:
> > * Peter Zijlstra <peterz@infradead.org> [2010-06-09 08:32:30]:
> > 
> > > On Wed, 2010-06-09 at 10:35 +0530, Srikar Dronamraju wrote:
> > > 
> > > > Peter, can you please point me to the fix for the floating point
> > > > exception patch?
> > > 
> > > Ingo just commited the fix, see tip commit f6ab91add6 (perf: Fix signed
> > > comparison in perf_adjust_period()).
> > 
> > Actually this fix was already checked-in but I still see the problem.
> > 
> > When ran gdb on the core, it showed me that it was dumping in
> > /usr/lib64/libnewt.so.0.52. in newtScaleSet function.
> > My newt lib was of version : newt-0.52.2-15
> > 
> > I am now able to workaround the problem by uninstalling newt-devel.
> 
> Ah, ok, then we're talking about two different issues, the patch I
> referred to solves a possible /0 in the kernel which triggers easily
> with software events because of that unsigned comparison.
> 
> I'll have to defer to Arnaldo on the newt issue.

I'm trying to reproduce this now.

  reply	other threads:[~2010-06-09 12:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 15:33 [PATCH][RFC] tracing: Use class->reg() for all registering of events Steven Rostedt
2010-06-08 15:57 ` Peter Zijlstra
2010-06-08 17:35   ` Srikar Dronamraju
2010-06-08 19:10     ` Steven Rostedt
2010-06-08 19:11       ` Steven Rostedt
2010-06-09  5:05       ` Srikar Dronamraju
2010-06-09  6:32         ` Peter Zijlstra
2010-06-09 11:47           ` Srikar Dronamraju
2010-06-09 11:53             ` Peter Zijlstra
2010-06-09 12:02               ` Arnaldo Carvalho de Melo [this message]
2010-06-09 12:23                 ` Arnaldo Carvalho de Melo
2010-06-09 12:35                   ` Arnaldo Carvalho de Melo
2010-06-10  8:27                     ` Srikar Dronamraju
2010-06-10 14:07                       ` Arnaldo Carvalho de Melo
2010-06-10 14:52         ` Steven Rostedt
2010-06-10 15:12           ` Srikar Dronamraju
2010-06-10 18:41       ` Steven Rostedt
2010-06-10 20:36         ` Peter Zijlstra
2010-06-10 20:41           ` Steven Rostedt
2010-06-08 18:36 ` Peter Zijlstra

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=20100609120224.GA8359@ghostprotocols.net \
    --to=acme@infradead.org \
    --cc=ananth@in.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.com \
    /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