From: Jiri Olsa <jolsa@redhat.com>
To: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
rostedt@goodmis.org, tglx@linutronix.de, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] Revert "tracing: Add unstable sched clock note to the warning"
Date: Fri, 18 Feb 2011 13:50:12 +0100 [thread overview]
Message-ID: <20110218125012.GA2604@jolsa.brq.redhat.com> (raw)
In-Reply-To: <tip-e9345aab675382176740bc8a2c6d3caf1510e46d@git.kernel.org>
oops, overlooked this one... will send new patch shortly, sorry
jirka
On Fri, Feb 18, 2011 at 10:39:12AM +0000, tip-bot for Ingo Molnar wrote:
> Commit-ID: e9345aab675382176740bc8a2c6d3caf1510e46d
> Gitweb: http://git.kernel.org/tip/e9345aab675382176740bc8a2c6d3caf1510e46d
> Author: Ingo Molnar <mingo@elte.hu>
> AuthorDate: Fri, 18 Feb 2011 08:09:49 +0100
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Fri, 18 Feb 2011 08:09:49 +0100
>
> Revert "tracing: Add unstable sched clock note to the warning"
>
> This reverts commit 5e38ca8f3ea423442eaafe1b7e206084aa38120a.
>
> Breaks the build of several !CONFIG_HAVE_UNSTABLE_SCHED_CLOCK
> architectures.
>
> Cc: Jiri Olsa <jolsa@redhat.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Message-ID: <20110217171823.GB17058@elte.hu>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
> kernel/trace/ring_buffer.c | 8 ++------
> 1 files changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
> index 7739893..bd1c35a 100644
> --- a/kernel/trace/ring_buffer.c
> +++ b/kernel/trace/ring_buffer.c
> @@ -2163,14 +2163,10 @@ rb_reserve_next_event(struct ring_buffer *buffer,
> delta = diff;
> if (unlikely(test_time_stamp(delta))) {
> WARN_ONCE(delta > (1ULL << 59),
> - KERN_WARNING "Delta way too big! %llu ts=%llu write stamp = %llu\n%s",
> + KERN_WARNING "Delta way too big! %llu ts=%llu write stamp = %llu\n",
> (unsigned long long)delta,
> (unsigned long long)ts,
> - (unsigned long long)cpu_buffer->write_stamp,
> - sched_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");
> + (unsigned long long)cpu_buffer->write_stamp);
> add_timestamp = 1;
> }
> }
parent reply other threads:[~2011-02-18 12:50 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tip-e9345aab675382176740bc8a2c6d3caf1510e46d@git.kernel.org>]
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=20110218125012.GA2604@jolsa.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®