public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linus.walleij@stericsson.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] RFC: nomadik: expand timesource to 63 bits
Date: Fri, 12 Nov 2010 10:43:25 +0100	[thread overview]
Message-ID: <4CDD0C3D.5070309@stericsson.com> (raw)
In-Reply-To: <AANLkTi=ysONhPQBTbVNRgTOx5PGEM=STaUYY6RnUpfES@mail.gmail.com>

john stultz wrote:

> I would advise against expanding the hardware counter to 63bits via
> software at the clocksource layer. This breaks the
> CLOCK_SOURCE_IS_CONTINUOUS flag rule (since the hardware will wrap
> below the mask value if not updated in the software layer). And as
> Thomas said, this will cause problems in the nohz idle limiting code
> (which makes sure we wake up before the clocksource wraps).

Hm, yeah that's probably the wisest thing to do right now..

Then the Tegra code is not quite sound. It will probably experience
bad stuff like shaky clocksource when idling too long.

> Instead, I'd use this extension at the sched_clock level, where it
> seems reasonable that it will be called frequently enough to not brake
> the cnt32_to_63 magic.

Yeah we will do it like the Orion does.

Thanks!
Linus Walleij

  reply	other threads:[~2010-11-12  9:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11  9:05 [PATCH] RFC: nomadik: expand timesource to 63 bits Linus Walleij
2010-11-11 10:16 ` Thomas Gleixner
2010-11-11 10:31   ` Linus Walleij
2010-11-11 11:05     ` Thomas Gleixner
2010-11-11 18:31       ` Nicolas Pitre
2010-11-11 19:00         ` Thomas Gleixner
2010-11-11 19:19           ` Nicolas Pitre
2010-11-11 21:33 ` john stultz
2010-11-12  9:43   ` Linus Walleij [this message]
2010-11-12  9:57   ` Uwe Kleine-König
2010-11-12 10:08     ` Linus Walleij
2010-11-12 10:31       ` Thomas Gleixner
2010-11-12 10:37         ` Linus Walleij
2010-11-12 11:08           ` Thomas Gleixner
2010-11-12 19:18           ` Nicolas Pitre
2010-11-12 20:22           ` john stultz
2010-11-12 19:15     ` Nicolas Pitre

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=4CDD0C3D.5070309@stericsson.com \
    --to=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.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