linux-kernel - Re: remoteproc: Resource table for IRQs

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

Message-ID: <CAK=WgbaX7HJJkAW-rn4e7BHstgV+zvSnjzg980gGui9ZCRxMqQ@mail.gmail.com>
Date:	Tue, 20 Mar 2012 19:34:05 +0200
From:	Ohad Ben-Cohen <ohad@...ery.com>
To:	monstr@...str.eu
Cc:	LKML <linux-kernel@...r.kernel.org>,
	John Williams <john.williams@...alogix.com>,
	Arnd Bergmann <arnd@...db.de>,
	Grant Likely <grant.likely@...retlab.ca>,
	devicetree-discuss@...ts.ozlabs.org,
	"Guzman Lugo, Fernando" <fernando.lugo@...com>
Subject: Re: remoteproc: Resource table for IRQs

Hi Michal,

On Mon, Mar 19, 2012 at 3:38 PM, Michal Simek <monstr@...str.eu> wrote:
> Maybe I am trying to do things more complicated than they are but
> I still see that make sense to do it.

I agree, it definitely does.

OMAP4 is using this kind of resource allocation for a plethora of resources.

In general there are two options to do this:

- static, via remoteproc (firmware tells us about its resources
requirements via the resource table, Linux allocates them before
booting firmware)
- dynamic, via rpmsg (firmware tells us about its resources
requirements by sending a message just before the relevant use case
kicks in, Linux allocates it only at that point)

The former consumes the resource as long as the remote processor is
powered on, but it's super simple: just add a new resource type.

The latter consumes the resource on when really needed, but it
requires a "resource manager": an rpmsg driver which does this kind of
resource allocation and tracking. Fernando (cc'ed) implemented it
already, and will be posting sometimes in the near future (it's
already available in Fernando's github tree if you're interested).

> What do you think?

Go for it :)

Thanks,
Ohad.
--
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/