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]
Date:	Sat, 19 May 2012 14:59:51 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] irq_domain: Standardise legacy/linear domain selection

On Sat, May 19, 2012 at 2:54 PM, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:
> On Sat, May 19, 2012 at 02:22:58PM -0600, Grant Likely wrote:
>
>> I'm looking at killing the legacy mapping entirely which will push
>> changing all the users anyway.  I'm going to hold off on applying this
>> one for a day or so until I'm sure of what it will look like.
>
> I take it you're going to replace the legacy mapping with an equivalent
> thing, though, so the interface is preserved for boards?  In which case
> it'd be more like replacing the linear mapping with a new mapping type
> that can also be used by legacy users I guess?

It will actually be like all legacy users switched to creating an
linear mapping, and then either associating already allocated
irq_descs with that domain or telling the domain to pre-map a specific
range of irq_descs (and manage allocations).  Those two use cases will
be separate APIs.  I don't think they should be combined (at least
from my current thinking) because it depends on whether or not the
irq_descs are already allocated.

g.



-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ