From: Arjan van de Ven <arjanv@redhat.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390 (9/9): no timer interrupts in idle.
Date: Thu, 22 Apr 2004 10:52:18 +0200 [thread overview]
Message-ID: <20040422085217.GA30328@devserv.devel.redhat.com> (raw)
In-Reply-To: <OF83E740E9.CE27150D-ONC1256E7E.002EED0D-C1256E7E.00305B60@de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
On Thu, Apr 22, 2004 at 10:48:11AM +0200, Martin Schwidefsky wrote:
>
>
>
>
> > is this generally useful, eg can all architectures use the
> > infrastructure you propose ? I seriously hope so; s390 isn't the only
> > one who would benefit, I'd love to see a generic thing for this.
>
> It is. All you have to do is to rework the timer functions for the
> architecture you want to support. This can be quite complicated
> though. There are some subtle races if you want to switch of the
> 100 HZ timer for a cpu. We had some problem with cpus that didn't
> want to wake up anymore ...
well my worry is the API; should it be "turn the timer off" or should it be
"the next tick is THIS many from now". The later allows one to use the hw in
one-shot mode (PC's can do this) where the scheduler timeslice expiry ends
up being a timer as well.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-22 8:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 8:48 [PATCH] s390 (9/9): no timer interrupts in idle Martin Schwidefsky
2004-04-22 8:52 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 8:24 Martin Schwidefsky
2004-04-29 12:06 ` Dipankar Sarma
2004-04-29 7:43 Martin Schwidefsky
2004-04-29 8:16 ` Dipankar Sarma
2004-04-23 8:48 Martin Schwidefsky
2004-04-22 14:56 Martin Schwidefsky
2004-04-28 19:07 ` Dipankar Sarma
2004-04-22 12:44 Martin Schwidefsky
2004-04-22 13:11 ` Arjan van de Ven
2004-04-23 3:32 ` George Anzinger
2004-04-22 12:14 Martin Schwidefsky
2004-04-22 12:25 ` Arjan van de Ven
2004-04-22 11:09 Martin Schwidefsky
2004-04-22 11:14 ` Arjan van de Ven
2004-04-22 10:53 Martin Schwidefsky
2004-04-22 10:56 ` Arjan van de Ven
2004-04-22 8:55 Martin Schwidefsky
[not found] <1Nt5d-84u-3@gated-at.bofh.it>
[not found] ` <1NwPD-2RW-37@gated-at.bofh.it>
[not found] ` <1NwPE-2RW-39@gated-at.bofh.it>
[not found] ` <1Nx8Y-3ev-15@gated-at.bofh.it>
2004-04-21 22:38 ` Andi Kleen
2004-04-21 18:52 Martin Schwidefsky
2004-04-21 21:58 ` Dipankar Sarma
2004-04-21 16:37 Martin Schwidefsky
2004-04-21 20:43 ` Dipankar Sarma
2004-04-21 20:46 ` Christoph Hellwig
2004-04-21 21:01 ` Dipankar Sarma
2004-04-21 16:31 Martin Schwidefsky
2004-04-21 16:32 ` Christoph Hellwig
2004-04-21 14:49 Martin Schwidefsky
2004-04-21 15:31 ` Christoph Hellwig
2004-04-22 8:02 ` Arjan van de Ven
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=20040422085217.GA30328@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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