linux-kernel - Re: [PATCH V8 2/3] irq: Track the interrupt timings

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.DEB.2.20.1703232216230.3723@nanos>
Date:   Thu, 23 Mar 2017 22:17:24 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Nicolas Pitre <nicolas.pitre@...aro.org>
cc:     Daniel Lezcano <daniel.lezcano@...aro.org>,
        linux-kernel@...r.kernel.org, peterz@...radead.org,
        rafael@...nel.org, vincent.guittot@...aro.org
Subject: Re: [PATCH V8 2/3] irq: Track the interrupt timings

On Thu, 23 Mar 2017, Nicolas Pitre wrote:
> Is there a need for 64 bits of relative time stamps?
> And 32 bits of IRQ number?

No.

> I'd say that 48 bit time stamp and 16 bit IRQ number is way sufficient.
> Who cares if we mispredict an IRQ after 78 hours of idle time?
> 
> Hence:
> 
> 	u64 value = (ts << 16) | irq;

Excellent!