linux-kernel - Re: [patch 29/32] genirq: Remove irq_reserve

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: <alpine.DEB.2.02.1405081453560.6261@ionos.tec.linutronix.de>
Date:	Thu, 8 May 2014 14:54:52 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Grant Likely <grant.likely@...retlab.ca>
cc:	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Peter Anvin <hpa@...or.com>, Tony Luck <tony.luck@...el.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [patch 29/32] genirq: Remove irq_reserve_irq[s]

On Thu, 8 May 2014, Grant Likely wrote:

> On Wed, 07 May 2014 15:44:21 -0000, Thomas Gleixner <tglx@...utronix.de> wrote:
> > No more users. And it's not going to come back. If you need
> > hotplugable irq chips, use irq domains.
> > 
> > Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
> 
> Acked-by: Grant Likely <grant.likely@...retlab.ca>
> 
> The ironic thing is that irq_domain may end up bringing this function
> back in some form as an optimization for irq_domains that need a
> contiguous range, but don't want to allocate all the irq_descs
> immediately. But if that happens it will be a very private API and it
> doesn't nullify removing the function now.

Right. We can deal with it when the need arises, but that's a
completely core internal issue then which is not going to be usable
outside of kernel/irq.

Thanks,

	tglx
--
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/