diff options
author | Dave Gerlach <d-gerlach@ti.com> | 2017-01-12 14:52:19 -0600 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-01-25 11:48:03 +0100 |
commit | 728bbe75c82fdc6bdf157652a4351856ed08afc4 (patch) | |
tree | 0a6ad639deba6651c33f161dffe9a88a20241926 /drivers/misc/fsa9480.c | |
parent | cdd1737cba7a6453c9453c55c4537a15cc1f49b2 (diff) | |
download | linux-728bbe75c82fdc6bdf157652a4351856ed08afc4.tar.gz linux-728bbe75c82fdc6bdf157652a4351856ed08afc4.tar.bz2 linux-728bbe75c82fdc6bdf157652a4351856ed08afc4.zip |
misc: sram: Introduce support code for protect-exec sram type
Some platforms, like many ARM SoCs, require the ability to run code from
on-chip memory like SRAM for tasks like reconfiguring the SDRAM
controller or entering low-power sleep modes. In order to do this we
must be able to allocate memory that the code can be copied to but then
change the mapping to be read-only and executable so that no memory is
both writable and executable at the same time to avoid opening any
unneccesary security holes.
By using the existing "pool" partition type that the SRAM driver allows
we can create a memory space that will already be exposed by the
genalloc framework to allow for allocating memory but we must extend
this to meet the executable requirements. By making use of various
set_memory_* APIs we can change the attributes of pages to make them
writable for code upload but then read-only and executable when we want
to actually run code. Because SRAM is a shared resource we need a
centralized manager of these set memory calls. Because the SRAM driver
itself is responsible for allocating the memory we can introduce a
sram_copy_exec API for the driver that works like memcpy but also
manages the page attributes and locking to allow multiple users of the
same SRAM space to all copy their code over independent of other each
before starting execution.
It is maintained in a separate file from the core SRAM driver to allow
it to be selectively built depending on whether or not a platform has
the appropriate set_memory_* APIs. A future patch will integrate it with
the core SRAM driver.
Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
Acked-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/misc/fsa9480.c')
0 files changed, 0 insertions, 0 deletions