From: Alan Jenkins <aj504@student.cs.york.ac.uk>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Frédéric Weisbecker" <fweisbec@gmail.com>,
"Arjan van de Ven" <arjan@infradead.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/6] Tracing/fastboot: Enable boot tracing only during initcalls
Date: Fri, 10 Oct 2008 13:55:13 +0100 [thread overview]
Message-ID: <48EF50B1.8070705@tuffmail.co.uk> (raw)
In-Reply-To: <20081010110445.GA12519@elte.hu>
Ingo Molnar wrote:
> * Frédéric Weisbecker <fweisbec@gmail.com> wrote:
>
>> 2008/10/10 Ingo Molnar <mingo@elte.hu>:
>>> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
>>>
>>>> We used to disable the initcall tracing at a specified time (IE: end
>>>> of builtin initcalls). But we don\'t need it anymore. It will be
>>>> stopped when initcalls are finished. However we want two things:
>>>>
>>>> _Start this tracing only after pre-smp initcalls are finished. _Since
>>>> we are planning to trace sched_switches at the same time, we want to
>>>> enable them only during the initcall execution. For this purpose, this
>>>> patch introduce two functions to enable/disable the sched_switch
>>>> tracing during boot.
>>>>
>>>> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
>>> applied to tip/tracing/fastboot, thanks Frederic!
>>>
>>> Ingo
>>>
>> Oops, sorry Ingo there are some backslashes that taint this patch.
>> I will resend a V2....
>
> dont worry, i fixed them already when i applied your patch (and that's
> all in latest tip/master).
>
> See the commit below - i sanitize most commit entries to make subject
> lines more consistent (note the capitalization difference between your
> submission and the end result), to improve paragraphing and general
> structure.
You missed the one backslash though...
> -/* Should be started after do_pre_smp_initcalls() in init/main.c */
> +/* Tells the boot tracer that the pre_smp_initcalls are finished.
> + * So we are ready .
> + * It doesn\'t enable sched events tracing however.
> + * You have to call enable_boot_trace to do so.
> + */
Alan
next prev parent reply other threads:[~2008-10-10 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 12:36 [PATCH 1/6] Tracing/fastboot: Enable boot tracing only during initcalls Frederic Weisbecker
2008-10-10 10:58 ` Ingo Molnar
2008-10-10 11:02 ` Frédéric Weisbecker
2008-10-10 11:04 ` Ingo Molnar
2008-10-10 11:09 ` Frédéric Weisbecker
2008-10-10 12:55 ` Alan Jenkins [this message]
2008-10-10 14:15 ` 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=48EF50B1.8070705@tuffmail.co.uk \
--to=aj504@student.cs.york.ac.uk \
--cc=arjan@infradead.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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