From: Peter Zijlstra <peterz@infradead.org>
To: Joel Fernandes <joelaf@google.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@android.com,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v7 2/2] tracing: Add support for preempt and irq enable/disable events
Date: Wed, 4 Oct 2017 18:04:34 +0200 [thread overview]
Message-ID: <20171004160434.hfd7rbefqvi3lz22@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20170929212245.24168-2-joelaf@google.com>
On Fri, Sep 29, 2017 at 02:22:45PM -0700, Joel Fernandes wrote:
> +++ b/kernel/trace/trace_irqsoff.c
> EXPORT_SYMBOL(trace_hardirqs_on);
> EXPORT_SYMBOL(trace_hardirqs_off);
> EXPORT_SYMBOL(trace_hardirqs_on_caller);
> EXPORT_SYMBOL(trace_hardirqs_off_caller);
Steve, how does this compiler with lockdep enabled? Because:
kernel/locking/lockdep.c:EXPORT_SYMBOL(trace_hardirqs_on_caller);
kernel/locking/lockdep.c:EXPORT_SYMBOL(trace_hardirqs_on);
kernel/locking/lockdep.c:EXPORT_SYMBOL(trace_hardirqs_off_caller);
kernel/locking/lockdep.c:EXPORT_SYMBOL(trace_hardirqs_off);
next prev parent reply other threads:[~2017-10-04 16:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 21:22 [PATCH v7 1/2] tracing: Prepare to add preempt and irq trace events Joel Fernandes
2017-09-29 21:22 ` [PATCH v7 2/2] tracing: Add support for preempt and irq enable/disable events Joel Fernandes
2017-10-04 16:01 ` Peter Zijlstra
2017-10-04 16:43 ` Joel Fernandes
2017-10-06 8:59 ` Joel Fernandes
2017-10-05 23:28 ` Joel Fernandes
2017-10-05 23:29 ` Joel Fernandes
2017-10-06 7:07 ` Peter Zijlstra
2017-10-06 7:28 ` Joel Fernandes
2017-10-06 13:38 ` Steven Rostedt
2017-10-06 17:27 ` Joel Fernandes
2017-10-04 16:04 ` Peter Zijlstra [this message]
2017-10-04 16:31 ` Joel Fernandes
2017-10-04 16:44 ` Steven Rostedt
2017-10-04 16:56 ` Joel Fernandes
2017-10-04 17:03 ` Steven Rostedt
2017-10-04 20:13 ` Joel Fernandes
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=20171004160434.hfd7rbefqvi3lz22@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=joelaf@google.com \
--cc=kernel-team@android.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.