public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maneesh Soni <maneesh@in.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH][GIT PULL] tracing/wakeup: move access to wakeup_cpu into spinlock
Date: Fri, 27 Mar 2009 23:11:43 +0530	[thread overview]
Message-ID: <20090327174143.GA24940@in.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0903270904260.1917@gandalf.stny.rr.com>

On Fri, Mar 27, 2009 at 09:15:29AM -0400, Steven Rostedt wrote:
...

> Do you have CONFIG_FRAME_POINTER set?
>

Yes, CONFIG_FRAME_POINTER=y
 
> Is this running in a virtual box or bare metal? (probably should not matter)
> 

Bare metal.


> What version of gcc do you have?
> 
gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44)


Thanks
Maneesh

-- 

Maneesh Soni
Linux Technology Center
IBM India Systems and Technology Lab,
Bangalore, India.

  parent reply	other threads:[~2009-03-27 17:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 12:28 [-tip] ftrace: oops at probe_wakeup_sched_switch+0xd1/0x1ae Maneesh Soni
2009-03-26 13:27 ` Frederic Weisbecker
2009-03-26 13:49   ` Steven Rostedt
2009-03-26 13:59     ` Steven Rostedt
2009-03-26 14:40     ` [PATCH][GIT PULL] tracing/wakeup: move access to wakeup_cpu into spinlock Steven Rostedt
2009-03-27  8:41       ` Maneesh Soni
2009-03-27 12:45         ` Maneesh Soni
2009-03-27 13:15           ` Steven Rostedt
2009-03-27 13:41             ` Frederic Weisbecker
2009-03-27 14:28               ` Steven Rostedt
2009-03-27 17:41             ` Maneesh Soni [this message]
2009-04-01 23:42           ` Steven Rostedt
2009-04-02  6:02             ` Maneesh Soni
2009-04-02 13:18               ` Steven Rostedt
2009-04-07 10:02                 ` Maneesh Soni

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=20090327174143.GA24940@in.ibm.com \
    --to=maneesh@in.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    /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