kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: vikram186@gmail.com (Vikram Narayanan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Enabling tickless kernel feature in ARM
Date: Wed, 27 Apr 2011 08:34:25 +0530	[thread overview]
Message-ID: <BANLkTi=3XAERAUm5V+2jROuix6BJR3PCTg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikzPzGRCy8G-X69Wk9uk6BUc_tO7w@mail.gmail.com>

Dear Haojian,

On Tue, Apr 26, 2011 at 10:04 PM, Haojian Zhuang
<haojian.zhuang@gmail.com> wrote:
>
> On Tue, Apr 26, 2011 at 9:55 PM, Vikram Narayanan <vikram186@gmail.com> wrote:
> > Hi,
> >
> > I want to enable the dynamic tick aka tickless kernel feature for the
> > BSP which I am developing. What are all the architecture dependent
> > changes that needs to be done for implementing it.
> > There was one struct by the name dyn_tick_timer, which is located
> > under linux/include/asm-arm/mach/time.h file. (which is removed from v
> > 2.6.27)
> > Now my question is that, are all the dyn_tick_timer functionalities
> > are moved to a generic interface somewhere?
> CONFIG_NO_HZ is used instead.

I am aware of the CONFIG_NO_HZ option. I am asking about the
implementation of it. To put in a more clear way.
There was a structure in the kernel source
linux/include/asm-arm/mach/time.h before 2.6.27

struct dyn_tick_timer {
          spinlock_t      lock;
          unsigned int    state;                  /* Current state */
          int             (*enable)(void);        /* Enables dynamic tick */
          int             (*disable)(void);       /* Disables dynamic tick */
          void            (*reprogram)(unsigned long); /* Reprograms
the timer */
          int             (*handler)(int, void *);
  };

To enable dynamic tick timer, one should implement functions for
enable, disable and reprogram. But this structure is no more used in
the new kernel source. In 2007 linux symposium, 3 authors talked about
implementing the tickless feature using HPET timers. Now my question
where does the implementation lies in the ARM architecture.

Vikram
>
> > Are the clock source and clockevent device timers enough to take care
> > of the tickless feature?
> There's no relationship between NOHZ and clocksource/clockevent.
> >
> > -
> > Vikram
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >

  reply	other threads:[~2011-04-27  3:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26 13:55 Enabling tickless kernel feature in ARM Vikram Narayanan
2011-04-26 16:34 ` Haojian Zhuang
2011-04-27  3:04   ` Vikram Narayanan [this message]
2011-04-27  6:29     ` Haojian Zhuang
2011-04-26 16:35 ` Mulyadi Santosa
2011-04-27  3:09   ` Vikram Narayanan
2011-04-27  4:29     ` Mulyadi Santosa
2011-04-27 13:49       ` Vikram Narayanan
2011-04-27 15:37         ` Mulyadi Santosa
2011-04-28 13:18           ` Vikram Narayanan
2011-04-28 15:08             ` Mulyadi Santosa
2011-04-28 16:20               ` Vikram Narayanan

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='BANLkTi=3XAERAUm5V+2jROuix6BJR3PCTg@mail.gmail.com' \
    --to=vikram186@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).