linux-kernel - recommended use of request_any_context

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-next>] [day] [month] [year] [list]

Message-ID: <CADRPPNS9q=WSF+=7neVMmsEwcOhKJE=ruO4ZrCwHDmNz8wX1eA@mail.gmail.com>
Date:   Wed, 21 Sep 2016 16:14:38 -0500
From:   Leo Li <pku.leo@...il.com>
To:     Marc Zyngier <maz@...terjones.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        lkml <linux-kernel@...r.kernel.org>,
        Marc Zyngier <marc.zyngier@....com>
Subject: recommended use of request_any_context_irq()

Hi Marc and Thomas,

With the introduction of request_any_context_irq() routine, driver can
deal with interrupt controllers using either threaded irq or normal
irq.  But I don't see many drivers that have been changed to use this
function to request interrupt.  For on-board devices, the driver
normally don't know which kind of interrupt controller they are
connected to.  Why don't we make the request_any_context_irq()
mandatory or recommended for all drivers?  Is there any drawback for
changing all the request_irq() to the request_any_context_irq()?

Regards,
Leo