linux-kernel - Re: [RFC PATCH v2 10/14] m68k: mac: Convert to clocksource API

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: <CACRpkdYOyU_43ExoB0bm2MB+kP4nAPik27Mw4oMDiUTZeODMgw@mail.gmail.com>
Date:   Tue, 20 Nov 2018 10:59:05 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     fthain@...egraphics.com.au
Cc:     Geert Uytterhoeven <geert@...ux-m68k.org>, funaho@...ai.org,
        schwab@...ux-m68k.org, Arnd Bergmann <arnd@...db.de>,
        schivers@....com.au, Thomas Gleixner <tglx@...utronix.de>,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        schmitzmic@...il.com, John Stultz <john.stultz@...aro.org>,
        linux-m68k@...ts.linux-m68k.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v2 10/14] m68k: mac: Convert to clocksource API

On Tue, Nov 20, 2018 at 10:00 AM Finn Thain <fthain@...egraphics.com.au> wrote:

> If you use one timer as a clock event device and the other as a
> clocksource, there are no timers left to run the existing
> timer_interrupt() handler. So this arrangement would require
> GENERIC_CLOCKEVENTS=y, right?

I think so, yes.

> Then, wouldn't all relevant platforms have to support
> GENERIC_CLOCKEVENTS=y, if a single binary was to support all of those
> platforms?

Good point. I wonder of there is a path forward where we
could have peaceful GENERIC_CLOCKEVENTS and
!GENERIC_CLOCKEVENTS co-existence.

Yours,
Linus Walleij