From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing/branch-tracer: include missing irqflags.h
Date: Sat, 29 Nov 2008 10:16:47 +0100 [thread overview]
Message-ID: <20081129091647.GA25109@elte.hu> (raw)
In-Reply-To: <4930B32E.6060403@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Impact: fix build error on branch tracer
>
> This should fix a build error reported on alpha in linux-next:
>
> CC kernel/trace/trace_branch.o
> kernel/trace/trace_branch.c: In function 'probe_likely_condition':
> kernel/trace/trace_branch.c:44: error: implicit declaration of function 'raw_local_irq_save'
> kernel/trace/trace_branch.c:76: error: implicit declaration of function 'raw_local_irq_restore'
applied to tip/tracing
> Unfortunately, I can't test it since I don't have any Alpha build
> environment.
it does not trigger with an Alpha defconfig - we do test that.
And the thing is, lockdep (which introduced irqflags tracing) has been
introduced upstream two years ago - and Alpha still does not have it
implemented. The architecture should be marked CONFIG_BROKEN if it
continues to cause problems like this.
Alexey, you seem to be using and relying on the Alpha architecture, could
you please have a shot at this and implement the missing irqflags
infrastructure? Thanks,
Ingo
next prev parent reply other threads:[~2008-11-29 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-29 3:12 [PATCH] tracing/branch-tracer: include missing irqflags.h Frederic Weisbecker
2008-11-29 9:16 ` Ingo Molnar [this message]
2008-11-30 12:50 ` Alexey Dobriyan
2008-11-30 16:24 ` Ingo Molnar
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=20081129091647.GA25109@elte.hu \
--to=mingo@elte.hu \
--cc=adobriyan@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.