mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: melwyn lobo <linux.melwyn@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: SMP timer issue
Date: Wed, 07 Jan 2009 15:20:51 +0100	[thread overview]
Message-ID: <1231338051.11687.293.camel@twins> (raw)
In-Reply-To: <121039230901062108s7312343cwaf81feebfcf8d734@mail.gmail.com>

On Wed, 2009-01-07 at 10:38 +0530, melwyn lobo wrote:
> Hello All,
> Following reply from Russell on the ARM mailing list, I have posted my
> question on this list.
> 
> We have ported the arm kernel 2.6.24 to ARM Cortex dual core
> processor. My question is regarding timer optimization.
> At present we have three timers for the two cores as follows;
> 1. MTU which provides the system tick and in the absence of local
> timers provides IPI_TIMER messages to other processors.
> 2. Localtimer for CPU0
> 3. Localtimer for CPU1
> 
> So presently (when local timers are enabled) there are 3 interrupts
> for every tick. I want to optimize the logic performed by MTU into the
> local timer of CPU0 so that this one serves as the system tick. Thus
> there would be no need for MTU interrupts and it would serve only as a
> clock source.
> 
> My question in particular:
> 1. Is there some platform which has already done this ?
> 2. Is this possible without modifying existing kernel framework?
> 3. How to update jiffies during boot when localtimer has not yet been setup?
> 
> Eagerly awaiting for some advice/comments.

There is plenty code in the hrtimer stuff to make the cpu local timers
(which I presume are used to implement hrtimer clockevents) do the
jiffie tick.

I've no idea how to hook all that up, but added some folks who might
know to the CC.

      reply	other threads:[~2009-01-07 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07  5:08 melwyn lobo
2009-01-07 14:20 ` Peter Zijlstra [this message]

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=1231338051.11687.293.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.melwyn@gmail.com \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®