Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263943AbUDVLUJ (ORCPT ); Thu, 22 Apr 2004 07:20:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263953AbUDVLUJ (ORCPT ); Thu, 22 Apr 2004 07:20:09 -0400 Received: from mtagate5.de.ibm.com ([195.212.29.154]:20125 "EHLO mtagate5.de.ibm.com") by vger.kernel.org with ESMTP id S263943AbUDVLUG (ORCPT ); Thu, 22 Apr 2004 07:20:06 -0400 Subject: Re: [PATCH] s390 (9/9): no timer interrupts in idle. To: arjanv@redhat.com Cc: akpm@osdl.org, linux-kernel@vger.kernel.org X-Mailer: Lotus Notes Release 5.0.11 July 24, 2002 Message-ID: From: Martin Schwidefsky Date: Thu, 22 Apr 2004 10:48:11 +0200 X-MIMETrack: Serialize by Router on D12ML062/12/M/IBM(Release 6.0.2CF2|July 23, 2003) at 22/04/2004 10:48:13 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 763 Lines: 22 > 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 ... blue skies, Martin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/