Date: Fri, 11 Nov 2005 09:20:04 +0100
From: Ingo Molnar <mingo@elte.hu>
To: john stultz <johnstul@us.ibm.com>
Cc: dino@in.ibm.com, linux-kernel@vger.kernel.org,
       Thomas Gleixner <tglx@linutronix.de>
Subject: Re: IO-APIC problem with 2.6.14-rt9
Message-ID: <20051111082004.GA20977@elte.hu>
References: <20051110200226.GA18780@in.ibm.com> <20051110200205.GA4696@elte.hu> <20051110203000.GB16301@in.ibm.com> <1131654575.27168.685.camel@cog.beaverton.ibm.com> <20051110210458.GA6097@elte.hu> <1131658975.27168.703.camel@cog.beaverton.ibm.com> <20051111073841.GA16009@elte.hu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051111073841.GA16009@elte.hu>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 894
Lines: 24


* Ingo Molnar <mingo@elte.hu> wrote:

> > Grumble. :( I was hoping to submit my tod code to Andrew tomorrow, but 
> > this might block that.
> 
> hm, ARCH_HAS_READ_CURRENT_TIMER is upstream already. I have not 
> measured the udelay thing upstream, but i thought it would have the 
> same issue.  Does the GTOD code impact this code?

ah, i see - you changed __delay to always be loop-based. That is quite 
incorrect.

but i think there is a generic way to solve this: just busy-poll 
->read_cycles(). I.e. move __delay into the generic code too. This means 
even more architecture-specific code would be consolidated, which is 
always good.

	Ingo
-
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/