mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, fweisbec@gmail.com, mingo@elte.hu
Subject: Re: [PATCHv2] trace: adding unstable sched clock note to the warning
Date: Mon, 7 Mar 2011 11:45:13 +0100	[thread overview]
Message-ID: <20110307104513.GB3661@jolsa.redhat.com> (raw)
In-Reply-To: <20110218145219.GD2604@jolsa.brq.redhat.com>

hi,
any feedback?

thanks,
jirka

On Fri, Feb 18, 2011 at 03:52:19PM +0100, Jiri Olsa wrote:
> hi,
> 
> warning "Delta way too big" warning might appear on a system with
> unstable shed clock right after the system is resumed and tracing
> was enabled during the suspend.
> 
> Since it's not realy bug, and the unstable sched clock is working
> fast and reliable otherwise, Steven suggested to keep using the
> sched clock in any case and just to make note in the warning itself.
> 
> v2 changes:
> - added CONFIG_HAVE_UNSTABLE_SCHED_CLOCK dependency
> 
> wbr,
> jirka
> 
> 
> Signed-off-by: Jiri Olsa <jolsa@redhat.com>
> ---
>  kernel/trace/ring_buffer.c |   12 ++++++++++--
>  1 files changed, 10 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index bd1c35a..37c4d3e 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -2162,11 +2162,19 @@ rb_reserve_next_event(struct ring_buffer *buffer,
>  	if (likely(ts >= cpu_buffer->write_stamp)) {
>  		delta = diff;
>  		if (unlikely(test_time_stamp(delta))) {
> +			int local_clock_stable = 1;
> +#ifdef CONFIG_HAVE_UNSTABLE_SCHED_CLOCK
> +			local_clock_stable = sched_clock_stable;
> +#endif
>  			WARN_ONCE(delta > (1ULL << 59),
> -				  KERN_WARNING "Delta way too big! %llu ts=%llu write stamp = %llu\n",
> +				  KERN_WARNING "Delta way too big! %llu ts=%llu write stamp = %llu\n%s",
>  				  (unsigned long long)delta,
>  				  (unsigned long long)ts,
> -				  (unsigned long long)cpu_buffer->write_stamp);
> +				  (unsigned long long)cpu_buffer->write_stamp,
> +				  local_clock_stable ? "" :
> +				  "If you just came from a suspend/resume,\n"
> +				  "please switch to the trace global clock:\n"
> +				  "  echo global > /sys/kernel/debug/tracing/trace_clock\n");
>  			add_timestamp = 1;
>  		}
>  	}
> -- 
> 1.7.1
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2011-03-07 10:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 12:28 [PATCH] " Jiri Olsa
2011-02-17 15:00 ` [tip:perf/core] tracing: Add " tip-bot for Jiri Olsa
2011-02-17 15:39   ` Steven Rostedt
2011-02-17 17:18     ` Ingo Molnar
2011-02-17 17:58       ` Steven Rostedt
2011-02-18 14:52 ` [PATCHv2] trace: adding " Jiri Olsa
2011-03-07 10:45   ` Jiri Olsa [this message]
2011-03-08  2:06     ` Steven Rostedt
2011-03-11  9:51   ` [tip:perf/core] tracing: Explain about unstable clock on resume with ring buffer warning tip-bot for Jiri Olsa

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=20110307104513.GB3661@jolsa.redhat.com \
    --to=jolsa@redhat.com \
    --cc=fweisbec@gmail.com \
    --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®