linux-kernel - Re: [PATCH 2.6.21-rt2] PowerPC: decrementer clockevent driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <9095839480a9686d9c40aa6143edb804@kernel.crashing.org>
Date:	Thu, 17 May 2007 21:50:52 +0200
From:	Segher Boessenkool <segher@...nel.crashing.org>
To:	Sergei Shtylyov <sshtylyov@...mvista.com>
Cc:	linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org,
	tglx@...utronix.de, mingo@...e.hu
Subject: Re: [PATCH 2.6.21-rt2] PowerPC: decrementer clockevent driver

>>> +     * We must write a positive value to the decrementer to clear
>>> +     * the interrupt on the IBM 970 CPU series.  In periodic mode,
>>> +     * this happens when the decrementer gets reloaded later, but
>>> +     * in one-shot mode, we have to do it here since an event 
>>> handler
>>> +     * may skip loading the new value...
>
>> Nothing special about 970 here -- on *every* PowerPC,
>> a decrementer exception exists as long as the high
>> bit of the decrementer equals 1.  BookE is different
>> of course.  Some other CPUs might deviate from the
>> architecture as well.
>
>    Quoting "PowerPC Operating Environment Architecture":

<snip>

> Otherwise, when the contents of DEC0 change, the exception effects of 
> the Decrementer become consistent with the new contents of the 
> Decrementer reasonably soon after the change.

And that is guaranteed on all PowerPC as far as I can see.
The main thing is that a decrementer exception won't go
away until the high bit becomes 0.


Segher

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/