| 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
| ||
|
Message-ID: <1419321529.5581.181.camel@freescale.com> Date: Tue, 23 Dec 2014 01:58:49 -0600 From: Scott Wood <scottwood@...escale.com> To: Jiang Liu <jiang.liu@...ux.intel.com> CC: Tudor Laurentiu <b10716@...escale.com>, Thomas Gleixner <tglx@...utronix.de>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, <linuxppc-dev@...ts.ozlabs.org> Subject: Re: Ask help about killing irqchip.irq_print_chip on PPC platforms On Tue, 2014-12-23 at 15:56 +0800, Jiang Liu wrote: > Hi Scott and Tudor, > Sorry, resend and Ccing the list. Resending reply... > We are trying to clean up some irqchip interfaces, and > irqchip.irq_print_chip is a candidate for removal. After some > changes on x86 side, arch/powerpc/sysdev/fsl_msi.c may be the > last user of irqchip.irq_print_chip. So could you please help > to advice on whether we could kill irqchip.irq_print_chip > by using "fsl-msi" instead of "fsl-msi-%d" for irqchip name? > Will it break any userspace interfaces? > Thanks! > Gerry fsl-msi-%d was introduced to allow userspace to identify the cascade interrupt belonging to a particular MSI, for the purpose of setting affinity, as this cannot be done on the MSI itself due to hardware limitations. Removing it would not exactly eliminate a lot of code or complexity... -Scott -- 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/
Powered by blists - more mailing lists