All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ajeet Yadav <ajeet.yadav.77@gmail.com>
To: John Stultz <john.stultz@linaro.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Not able to use HIGH_RES_TIMERS on ARM
Date: Fri, 23 Mar 2012 10:29:33 +0530	[thread overview]
Message-ID: <CAB4K4y7zGex+1u-_PBVwVzHu6OYGQfL=Cv9aFfEG2_Q0-S-evA@mail.gmail.com> (raw)
In-Reply-To: <4F6BECA7.7030007@linaro.org>

On Fri, Mar 23, 2012 at 8:53 AM, John Stultz <john.stultz@linaro.org> wrote:
> On 03/22/2012 03:25 AM, Ajeet Yadav wrote:
>>
>> I understand your point,
>> Our target (2.6) always had ARCH_USES_GETTIMEOFFSET=y , but still we
>> were able to use the TRACER in past until the patch "kill
>> GENERIC_TIMER" published, anyone will ask me remove this patch and use
>> TRACER, becaue it was working before. :)
>
>
> Ajeet,
>    Sorry, by TRACER, do you mean PREEMPT_TRACER or something else? And what
> specific 2.6.X kernel were you using?
IRQSOFF_TRACER and PREEMPT_TRACER, our old kernel was 2.6.35.
>
> Steven, I'm seeing:
>
> config PREEMPT_TRACER
>        bool "Preemption-off Latency Tracer"
>        default n
>        depends on !ARCH_USES_GETTIMEOFFSET
>
> Do you have any context as to why is !ARCH_USES_GETTIMEOFFSET flagged here?
>
> thanks
> -john
>

  reply	other threads:[~2012-03-23  4:59 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 [this message]
2012-03-23  9:10                   ` Ajeet Yadav
2012-03-23 14:28                     ` Steven Rostedt
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='CAB4K4y7zGex+1u-_PBVwVzHu6OYGQfL=Cv9aFfEG2_Q0-S-evA@mail.gmail.com' \
    --to=ajeet.yadav.77@gmail.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --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.