From: "Frédéric Weisbecker" <fweisbec@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Arjan van de Ven" <arjan@infradead.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 6/6] tracing/fastboot: Print ktime of sched events when boot tracing
Date: Sat, 11 Oct 2008 22:03:18 +0200 [thread overview]
Message-ID: <c62985530810111303h2ac6e02ewf54765717895c949@mail.gmail.com> (raw)
In-Reply-To: <20081010194530.GA31401@elte.hu>
2008/10/10 Ingo Molnar <mingo@elte.hu>:
> hm, there's a new build failure:
>
> kernel/built-in.o: In function `boot_trace_init':
> trace_boot.c:(.text+0x5ee38): undefined reference to `sched_switch_trace'
> kernel/built-in.o: In function `disable_boot_trace':
> (.text+0x5eee1): undefined reference to `tracing_stop_cmdline_record'
> kernel/built-in.o: In function `enable_boot_trace':
> (.text+0x5ef11): undefined reference to `tracing_start_cmdline_record'
>
> this revert solves the problem:
>
> commit b80bebdc1718c02947468df227b7f4414d8dcce8
> Author: Ingo Molnar <mingo@elte.hu>
> Date: Fri Oct 10 21:44:24 2008 +0200
>
> Revert "tracing/fastboot: use sched switch tracer from boot tracer"
>
> This reverts commit 124cecce4145c590ae391fe12962653be8a05658.
>
> Config attached.
>
> Ingo
>
....I guess that could happen when the boot tracer is configured
whithout the sched_switch tracer.
I will send a patch to add this dependance on the Kconfig...
Thanks.
next prev parent reply other threads:[~2008-10-11 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 14:34 Frederic Weisbecker
2008-10-10 13:02 ` Frédéric Weisbecker
2008-10-10 14:05 ` Ingo Molnar
2008-10-10 14:47 ` Frédéric Weisbecker
2008-10-10 14:49 ` Ingo Molnar
2008-10-10 19:45 ` Ingo Molnar
2008-10-11 20:03 ` Frédéric Weisbecker [this message]
2008-10-11 20:04 ` Frédéric Weisbecker
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=c62985530810111303h2ac6e02ewf54765717895c949@mail.gmail.com \
--to=fweisbec@gmail.com \
--cc=arjan@infradead.org \
--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
all inboxes | Powered by JetHome®