From: Frederic Weisbecker <fweisbec@gmail.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: kill some magic numbers
Date: Fri, 27 Mar 2009 13:21:14 +0100 [thread overview]
Message-ID: <20090327122113.GD5976@nowhere> (raw)
In-Reply-To: <49CC7870.9000309@cn.fujitsu.com>
On Fri, Mar 27, 2009 at 02:55:44PM +0800, Li Zefan wrote:
> Impact: cleanup
>
> Use USEC_PER_SEC and NSEC_PER_SEC instead of 1000000 and 1000000000.
>
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
> kernel/trace/trace_boot.c | 5 +++--
> kernel/trace/trace_mmiotrace.c | 6 ++++--
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/trace/trace_boot.c b/kernel/trace/trace_boot.c
> index 7a30fc4..a29ef23 100644
> --- a/kernel/trace/trace_boot.c
> +++ b/kernel/trace/trace_boot.c
> @@ -9,6 +9,7 @@
> #include <linux/debugfs.h>
> #include <linux/ftrace.h>
> #include <linux/kallsyms.h>
> +#include <linux/time.h>
>
> #include "trace.h"
> #include "trace_output.h"
> @@ -67,7 +68,7 @@ initcall_call_print_line(struct trace_iterator *iter)
> trace_assign_type(field, entry);
> call = &field->boot_call;
> ts = iter->ts;
> - nsec_rem = do_div(ts, 1000000000);
> + nsec_rem = do_div(ts, NSEC_PER_SEC);
>
> ret = trace_seq_printf(s, "[%5ld.%09ld] calling %s @ %i\n",
> (unsigned long)ts, nsec_rem, call->func, call->caller);
> @@ -92,7 +93,7 @@ initcall_ret_print_line(struct trace_iterator *iter)
> trace_assign_type(field, entry);
> init_ret = &field->boot_ret;
> ts = iter->ts;
> - nsec_rem = do_div(ts, 1000000000);
> + nsec_rem = do_div(ts, NSEC_PER_SEC);
>
> ret = trace_seq_printf(s, "[%5ld.%09ld] initcall %s "
> "returned %d after %llu msecs\n",
> diff --git a/kernel/trace/trace_mmiotrace.c b/kernel/trace/trace_mmiotrace.c
> index 8e37fcd..d53b45e 100644
> --- a/kernel/trace/trace_mmiotrace.c
> +++ b/kernel/trace/trace_mmiotrace.c
> @@ -9,6 +9,8 @@
> #include <linux/kernel.h>
> #include <linux/mmiotrace.h>
> #include <linux/pci.h>
> +#include <linux/time.h>
> +
> #include <asm/atomic.h>
>
> #include "trace.h"
> @@ -174,7 +176,7 @@ static enum print_line_t mmio_print_rw(struct trace_iterator *iter)
> struct mmiotrace_rw *rw;
> struct trace_seq *s = &iter->seq;
> unsigned long long t = ns2usecs(iter->ts);
> - unsigned long usec_rem = do_div(t, 1000000ULL);
> + unsigned long usec_rem = do_div(t, USEC_PER_SEC);
> unsigned secs = (unsigned long)t;
> int ret = 1;
>
> @@ -221,7 +223,7 @@ static enum print_line_t mmio_print_map(struct trace_iterator *iter)
> struct mmiotrace_map *m;
> struct trace_seq *s = &iter->seq;
> unsigned long long t = ns2usecs(iter->ts);
> - unsigned long usec_rem = do_div(t, 1000000ULL);
> + unsigned long usec_rem = do_div(t, USEC_PER_SEC);
> unsigned secs = (unsigned long)t;
> int ret;
>
> --
> 1.5.4.rc3
Thanks!
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
next prev parent reply other threads:[~2009-03-27 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 6:55 [PATCH] tracing: kill some magic numbers Li Zefan
2009-03-27 12:21 ` Frederic Weisbecker [this message]
2009-03-27 12:46 ` Steven Rostedt
2009-04-03 16:10 ` Steven Rostedt
2009-04-08 6:54 ` [tip:tracing/core] tracing: use macros to denote usec and nsec per second Li Zefan
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=20090327122113.GD5976@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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 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.