lkml.org 
[lkml]   [2015]   [Feb]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v3 1/1] x86: Add Isolated Memory Regions for Quark X1000
On 23/02/15 22:18, Pavel Machek wrote:
> On Mon 2015-01-26 14:15:27, Bryan O'Donoghue wrote:

>
> Do the applications normally need to manipulate IMRs?


Applications could in theory manipulate IMRs - you might want to place
an IMR around an EFI capsule in memory for example - before calling a
capsule update.

This code will place an IMR around the kernel .text - .rodata which
ensures that no unwarranted DMA access can rewrite write-only kernel
addresses - something the MMU would not fault on - on non-IMR enabled
processors.

> Would it be
> possible to do all IMR manipulations in the bootloader?
>

Possible yes - in practical terms for Galileo or the SMARC+Quark from
Kontron for example - you'd be forcing a bootloader change - which most
users will not pick up.


Considering IMRs can reset the system if they aren't sanitized, it's
good practice for the kernel to go and make sure that every unlocked IMR
is torn-down and reset.


\
 
 \ /
  Last update: 2015-02-25 00:21    [W:0.453 / U:0.028 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site