From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Ajeet Yadav <ajeet.yadav.77@gmail.com>
Cc: John Stultz <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Not able to use HIGH_RES_TIMERS on ARM
Date: Mon, 19 Mar 2012 13:04:45 +0000 [thread overview]
Message-ID: <20120319130445.GN15988@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAB4K4y7ticNGWv1XWtqLatBG69yM2gv31ayt5DqWSSOUWTZrGg@mail.gmail.com>
On Mon, Mar 19, 2012 at 06:31:44PM +0530, Ajeet Yadav wrote:
> Hi John, refering to you patch:
>
> ARM: remove 'select GENERIC_TIME'
> GENERIC_TIME is now enabled by default, so 'select GENERIC_TIME' is
> redundant. Remove them.
>
> The following config's are not selectable:
> config NO_HZ, config HIGH_RES_TIMERS, config IRQSOFF_TRACER, config
> PREEMPT_TRACER
>
> As far as I know, ARM now uses GENERIC_TIME via the arch_getoffset()
> infrastructure, i.e ARCH_USES_GETTIMEOFFSET=y
No. It is possible to select these options, but only if your platform
uses the clockevent and clocksource infrastructure. If you're using that,
then you must _not_ select ARCH_USES_GETTIMEOFFSET.
ARCH_USES_GETTIMEOFFSET is for compatibility with old unconverted
platforms, which are _not_ possible to use the above features.
next prev parent reply other threads:[~2012-03-19 13:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 13:01 Ajeet Yadav
2012-03-19 13:04 ` Russell King - ARM Linux [this message]
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
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=20120319130445.GN15988@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=ajeet.yadav.77@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome