From: Steven Rostedt <rostedt@goodmis.org>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: hwlat: update old comment
Date: Tue, 14 Feb 2017 15:05:12 -0500 [thread overview]
Message-ID: <20170214150512.2f0b376e@gandalf.local.home> (raw)
In-Reply-To: <20170213122517.6e211955@redhat.com>
On Mon, 13 Feb 2017 12:25:17 -0500
Luiz Capitulino <lcapitulino@redhat.com> wrote:
> The ftrace hwlat does support a cpumask.
>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Thanks! Applied.
-- Steve
> ---
> kernel/trace/trace_hwlat.c | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/kernel/trace/trace_hwlat.c b/kernel/trace/trace_hwlat.c
> index af344a1b..1199fe1 100644
> --- a/kernel/trace/trace_hwlat.c
> +++ b/kernel/trace/trace_hwlat.c
> @@ -322,10 +322,7 @@ static void move_to_next_cpu(bool initmask)
> * need to ensure nothing else might be running (and thus preempting).
> * Obviously this should never be used in production environments.
> *
> - * Currently this runs on which ever CPU it was scheduled on, but most
> - * real-world hardware latency situations occur across several CPUs,
> - * but we might later generalize this if we find there are any actualy
> - * systems with alternate SMI delivery or other hardware latencies.
> + * Executes one loop interaction on each CPU in tracing_cpumask sysfs file.
> */
> static int kthread_fn(void *data)
> {
prev parent reply other threads:[~2017-02-14 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 17:25 Luiz Capitulino
2017-02-14 20:05 ` Steven Rostedt [this message]
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=20170214150512.2f0b376e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.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®