From: Randy Dunlap <rdunlap@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Sep 7 (kernel/trace/trace_hwlat.c)
Date: Wed, 7 Sep 2016 11:34:24 -0700 [thread overview]
Message-ID: <2c4a12e1-7970-f272-8883-db7c6ae36825@infradead.org> (raw)
In-Reply-To: <20160907124422.70216727@gandalf.local.home>
On 09/07/16 09:44, Steven Rostedt wrote:
> Thanks!
>
> Below is the fix. I'll have to add it.
>
> -- Steve
>
>
> diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
> index 72c07c2ffd79..d9000a81960e 100644
> --- a/kernel/trace/Kconfig
> +++ b/kernel/trace/Kconfig
> @@ -224,6 +224,7 @@ config SCHED_TRACER
> config HWLAT_TRACER
> bool "Tracer to detect hardware latencies (like SMIs)"
> select GENERIC_TRACER
> + select TRACER_MAX_TRACE
> help
> This tracer, when enabled will create one or more kernel threads,
> depening on what the cpumask file is set to, which each thread
>
Hm, now I get:
../kernel/trace/trace.c: In function 'tracing_set_tracer':
../kernel/trace/trace.c:4850:3: error: implicit declaration of function 'free_snapshot' [-Werror=implicit-function-declaration]
free_snapshot(tr);
^
../kernel/trace/trace.c:4856:3: error: implicit declaration of function 'alloc_snapshot' [-Werror=implicit-function-declaration]
ret = alloc_snapshot(tr);
^
--
~Randy
next prev parent reply other threads:[~2016-09-07 18:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 7:52 linux-next: Tree for Sep 7 Stephen Rothwell
2016-09-07 16:37 ` linux-next: Tree for Sep 7 (kernel/trace/trace_hwlat.c) Randy Dunlap
2016-09-07 16:44 ` Steven Rostedt
2016-09-07 18:34 ` Randy Dunlap [this message]
2016-09-07 18:48 ` Steven Rostedt
2016-09-07 19:38 ` Steven Rostedt
2016-09-07 20:55 ` Randy Dunlap
2016-09-08 2:58 ` Steven Rostedt
2016-09-08 5:38 ` Randy Dunlap
2016-09-07 21:42 ` Stephen Rothwell
2016-09-08 2:59 ` 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=2c4a12e1-7970-f272-8883-db7c6ae36825@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).