linux-kernel - Re: [PATCH 08/25] hrtimer: Reduce conditional code (expires_next, next

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: <20170926121039.ov3i2k7dvg5iihfj@hirez.programming.kicks-ass.net>
Date:   Tue, 26 Sep 2017 14:10:39 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Anna-Maria Gleixner <anna-maria@...utronix.de>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...hat.com>,
        Christoph Hellwig <hch@....org>, keescook@...omium.org,
        John Stultz <john.stultz@...aro.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 08/25] hrtimer: Reduce conditional code (expires_next,
 next_timer)

On Thu, Aug 31, 2017 at 12:23:37PM -0000, Anna-Maria Gleixner wrote:
> The hrtimer_cpu_base struct member expires_next and next_timer are
> conditional members (CONFIG_HIGH_RES_TIMERS). This makes the hrtimer code
> more complex and harder to understand than it actually is.
> 
> Reduce the conditionals related to those two struct members.

So this grows the data structure for !HIGH_RES for easier code? We no
longer care about archs that don't support HIGH_RES?