public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] mach-integrator: modernize clock event registration
Date: Thu, 8 Sep 2011 11:34:59 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1109081133530.2723@ionos> (raw)
In-Reply-To: <CACRpkdZ0HgvhgFU9-4f7QtWT3aJuZhY8QQB+oEW0mEy+Uzuh=Q@mail.gmail.com>

On Thu, 8 Sep 2011, Linus Walleij wrote:

> On Thu, Sep 8, 2011 at 10:55 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> >> Acked-by: Thomas Gleixner <tglx@linutronix.de>
> 
> > My understanding is that periodic timers are not setup by the generic
> > clock event code, and so we do need to keep the 'timer_reload' stuff
> > around.
> 
> Aha. Yes maybe I've not tested that mode well enough, I'll
> have a closer look.
> 
> An alteranative is to retire the periodic mode and only
> support oneshot, like the plat-nomadik/timer.c currently
> does. My impression is that oneshot will always work fine,
> and doing this leaves all details up to the timekeeping
> core so we don't need to deal with it, but I may be wrong.
> Ideas?

It does, but for a pure periodic setup (nohz=off, highres=off) you add
the overhead of reprogramming the device for each tick.

Thanks,

	tglx

  reply	other threads:[~2011-09-08  9:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07  8:31 [PATCH 3/4] mach-integrator: modernize clock event registration Linus Walleij
2011-09-07 10:02 ` Thomas Gleixner
2011-09-08  8:55   ` Russell King - ARM Linux
2011-09-08  9:23     ` Linus Walleij
2011-09-08  9:34       ` Thomas Gleixner [this message]
2011-09-08  9:33     ` Thomas Gleixner
2011-09-08 20:18     ` Linus Walleij

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=alpine.LFD.2.02.1109081133530.2723@ionos \
    --to=tglx@linutronix.de \
    --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