From: Thomas Gleixner <tglx@linutronix.de>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Colin Cross <ccross@google.com>,
Rabin VINCENT <rabin.vincent@stericsson.com>
Subject: Re: [PATCH] RFC: nomadik: expand timesource to 63 bits
Date: Thu, 11 Nov 2010 20:00:26 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1011111958460.2900@localhost6.localdomain6> (raw)
In-Reply-To: <alpine.LFD.2.00.1011111330170.13911@xanadu.home>
On Thu, 11 Nov 2010, Nicolas Pitre wrote:
> On Thu, 11 Nov 2010, Thomas Gleixner wrote:
> > Well, you don't need the keepwarm() timer, if you just call
> > sched_clock() in the idle wakeup path, so the magic in the NOHZ code
> > will ensure that you reread the thing timely.
>
> You still have to make sure you get out of idle before 16 secs has
> passed.
No, I meant to put it into the idle loop, right after mach_idle() or
whatever is called to put the CPU into deep power sleep. The
clockevents core code makes sure that you get interrupted in time.
Thanks,
tglx
next prev parent reply other threads:[~2010-11-11 19:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 9:05 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 [this message]
2010-11-11 19:19 ` Nicolas Pitre
2010-11-11 21:33 ` john stultz
2010-11-12 9:43 ` Linus Walleij
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=alpine.LFD.2.00.1011111958460.2900@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=ccross@google.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=rabin.vincent@stericsson.com \
/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®