From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Pekka Paalanen <pq@iki.fi>,
Frederic Weisbecker <fweisbec@gmail.com>,
Martin Bligh <mbligh@google.com>,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: [PATCH 1/2] ring_buffer: remove raw from local_irq_save
Date: Wed, 1 Oct 2008 08:14:04 +0200 [thread overview]
Message-ID: <20081001061404.GA13682@elte.hu> (raw)
In-Reply-To: <20081001060809.GA6646@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> > * Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > > The raw_local_irq_save causes issues with lockdep. We don't need it
> > > so replace them with local_irq_save.
>
> the same warning still occurs with your latest fixes - see the log
> below. Config attached. You should be able to reproduce it, it happens
> on every bootup with this config.
ignore me, my bad ... i messed up the test. The warning is indeed fixed.
Ingo
next prev parent reply other threads:[~2008-10-01 6:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 4:29 [PATCH 0/2] ring_buffer: updates for linux-tip Steven Rostedt
2008-10-01 4:29 ` [PATCH 1/2] ring_buffer: remove raw from local_irq_save Steven Rostedt
2008-10-01 5:52 ` Ingo Molnar
2008-10-01 6:08 ` Ingo Molnar
2008-10-01 6:14 ` Ingo Molnar [this message]
2008-10-01 4:29 ` [PATCH 2/2] ring_buffer: implement new locking Steven Rostedt
2008-10-01 6:01 ` Ingo Molnar
2008-10-01 7:20 ` [PATCH 0/2] ring_buffer: updates for linux-tip Frédéric Weisbecker
2008-10-01 7:23 ` Ingo Molnar
2008-10-01 12:32 ` Frédéric Weisbecker
2008-10-01 17:08 ` Frédéric Weisbecker
2008-10-01 17:14 ` [PATCH] ftrace: preempt disable over interrupt disable Steven Rostedt
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=20081001061404.GA13682@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=peterz@infradead.org \
--cc=pq@iki.fi \
--cc=rostedt@goodmis.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 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.