itimer oddness in 2.6.12

[Tom Marshall <tmarshall@real.com>]

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

The patch to fix "setitimer timer expires too early" is causing issues for
the Helix server.  We have a timer processs that updates the server's
timestamp on an itimer and it expects the signal to be delivered at roughly
the interval retrieved from getitimer.  This is very consistent on every
platform, including Linux up to 2.6.11, but breaks on 2.6.12.  On 2.6.12,
setting the itimer to 10ms and retrieving the actual interval from getitimer
reports 10.998ms, but the timer interrupts are consistently delivered at
roughly 11.998ms.  This behavior was pointed out as problematic in the patch
submission:

  http://www.kernel.org/hg/linux-2.6/?cmd=changeset;node=36e9195dc9f43467671344332f4c342f183647f7

Would it be possible to resolve this discrepancy for 2.6.13?

Please cc: me on replies, I am not subscribed.

-- 
I stayed up all night playing poker with tarot cards.  I got a full
house and four people died.
        -- Steven Wright

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]