All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Ajeet Yadav <ajeet.yadav.77@gmail.com>
Cc: John Stultz <john.stultz@linaro.org>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Not able to use HIGH_RES_TIMERS on ARM
Date: Fri, 23 Mar 2012 10:28:16 -0400	[thread overview]
Message-ID: <1332512896.23924.66.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <CAB4K4y4DvUb+908P4NJoyJbDa35R2jP5cHqnoNWr9HRZJYyj4w@mail.gmail.com>

On Fri, 2012-03-23 at 14:40 +0530, Ajeet Yadav wrote:

> linux-3.0.20/kernel/trace/Kconfig
> linux-3.0.20-dirty/kernel/trace/Kconfig
> --- linux-3.0.20/kernel/trace/Kconfig   2012-02-06 23:01:45.000000000 +0530
> +++ linux-3.0.20-dirty/kernel/trace/Kconfig     2012-03-19
> 18:21:41.000000000 +0530
> @@ -173,7 +173,6 @@ config IRQSOFF_TRACER
>        bool "Interrupts-off Latency Tracer"
>        default n
>        depends on TRACE_IRQFLAGS_SUPPORT
> -       depends on !ARCH_USES_GETTIMEOFFSET
>        select TRACE_IRQFLAGS
>        select GENERIC_TRACER
>        select TRACER_MAX_TRACE
> @@ -195,7 +194,6 @@ config IRQSOFF_TRACER
>  config PREEMPT_TRACER
>        bool "Preemption-off Latency Tracer"
>        default n
> -       depends on !ARCH_USES_GETTIMEOFFSET
>        depends on PREEMPT
>        select GENERIC_TRACER
>        select TRACER_MAX_TRACE

A little history here.

When I converted the irqsoff/preemptoff latency tracers from the
original -rt patch (written by Ingo), these options originally had
"depends on GENERIC_TIME". I just checked, and this goes at least back
to 2.6.22.1-rt9 (long before ftrace).

When I ported these to ftrace, I kept the dependencies. They probably
are not needed and are only there for historical reasons.

If this patch works fine for you, and that you are my only test case for
this patch. I'd just say:

Acked-by: Steven Rostedt <rostedt@goodmis.org>

-- Steve



  reply	other threads:[~2012-03-23 14:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 13:01 Not able to use HIGH_RES_TIMERS on ARM Ajeet Yadav
2012-03-19 13:04 ` Russell King - ARM Linux
2012-03-19 13:19   ` Ajeet Yadav
2012-03-19 13:26     ` Russell King - ARM Linux
2012-03-21  4:58       ` John Stultz
2012-03-21 10:16         ` Ajeet Yadav
2012-03-22  9:16           ` Ajeet Yadav
2012-03-22 10:02             ` Russell King - ARM Linux
2012-03-22 10:25               ` Ajeet Yadav
2012-03-23  3:23                 ` John Stultz
2012-03-23  4:59                   ` Ajeet Yadav
2012-03-23  9:10                   ` Ajeet Yadav
2012-03-23 14:28                     ` Steven Rostedt [this message]
2012-03-24  7:06                       ` Ajeet Yadav
2012-03-26 16:47                         ` Steven Rostedt
2012-03-23  3:28                 ` John Stultz
2012-03-23  5:52                   ` Ajeet Yadav
2012-03-23  6:17                     ` Rabin Vincent
2012-03-23  8:58                       ` Ajeet Yadav
2012-03-23 16:14                     ` Greg KH
2012-03-24  7:05                       ` Ajeet Yadav

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=1332512896.23924.66.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=ajeet.yadav.77@gmail.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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.