From: Tony Lindgren <tony@atomide.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Pavel Machek <pavel@suse.cz>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Arjan van de Ven <arjan@infradead.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Andrea Arcangeli <andrea@suse.de>,
George Anzinger <george@mvista.com>,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>,
Lee Revell <rlrevell@joe-job.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Dynamic tick, version 050127-1
Date: Fri, 4 Feb 2005 09:42:55 -0800 [thread overview]
Message-ID: <20050204174254.GG22444@atomide.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0502041028460.2194@montezuma.fsmlabs.com>
* Zwane Mwaikambo <zwane@arm.linux.org.uk> [050204 09:31]:
> On Fri, 4 Feb 2005, Tony Lindgren wrote:
>
> > Yes, it's safer to keep the timer periodic, although it's
> > used for oneshot purposes for the skips. If the timer interrupt
> > got missed for some reason, the system would be able to recover when
> > it's in periodic mode.
> >
> > And with some timers, we can do the reprogramming faster, as we just
> > need to load the new value.
> >
> > I could not figure out how to disable the interrupts for PIT
> > when local APIC is used and the ticks to skip is longer than PIT
> > would allow. So I just changed the mode temporarily to disable it.
> >
> > Does anybody know if there's a way to stop PIT interrupts while
> > keeping it in the periodic mode?
>
> disable_irq(0) ?
Then the problem is that the CPU does not stay in sleep but wakes to
the first PIT interrupt AFAIK.
Tony
next prev parent reply other threads:[~2005-02-04 17:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 21:29 [PATCH] Dynamic tick, version 050127-1 Tony Lindgren
2005-01-27 21:50 ` Tony Lindgren
2005-02-01 11:00 ` Pavel Machek
2005-02-01 20:40 ` Tony Lindgren
2005-02-01 21:25 ` Pavel Machek
2005-02-01 23:03 ` Tony Lindgren
2005-02-02 13:50 ` Pavel Machek
2005-02-02 13:50 ` Pavel Machek
2005-02-02 13:56 ` Pavel Machek
2005-02-02 14:11 ` Pavel Machek
2005-02-03 3:04 ` Tony Lindgren
2005-02-03 10:56 ` Pavel Machek
2005-02-03 16:43 ` Tony Lindgren
2005-02-04 5:19 ` Tony Lindgren
2005-02-04 6:33 ` Zwane Mwaikambo
2005-02-04 17:18 ` Tony Lindgren
2005-02-04 17:31 ` Zwane Mwaikambo
2005-02-04 17:42 ` Tony Lindgren [this message]
2005-02-04 17:54 ` Zwane Mwaikambo
2005-02-04 18:58 ` Tony Lindgren
2005-02-04 19:24 ` Tony Lindgren
2005-02-05 23:00 ` Pavel Machek
2005-02-06 2:33 ` Tony Lindgren
2005-02-06 3:54 ` Tony Lindgren
2005-02-06 8:41 ` Pavel Machek
2005-02-06 8:50 ` Pavel Machek
2005-02-06 17:07 ` Tony Lindgren
2005-02-06 12:15 ` Pavel Machek
2005-02-06 17:08 ` Tony Lindgren
2005-02-06 8:11 ` Pavel Machek
2005-02-06 8:53 ` Lee Revell
2005-02-06 10:25 ` Pavel Machek
2005-02-07 22:08 ` George Anzinger
2005-02-06 17:10 ` Tony Lindgren
2005-02-06 18:34 ` Pavel Machek
2005-02-01 20:20 ` Lee Revell
2005-02-01 23:42 ` Tony Lindgren
2005-02-02 1:06 ` Eric St-Laurent
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=20050204174254.GG22444@atomide.com \
--to=tony@atomide.com \
--cc=andrea@suse.de \
--cc=arjan@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rlrevell@joe-job.com \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=zwane@arm.linux.org.uk \
/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