* Ingo Molnar <[email protected]> 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
