aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/fork.c
diff options
context:
space:
mode:
authorDavid Howells <dhowells@redhat.com>2009-01-08 12:04:48 +0000
committerDavid Howells <dhowells@redhat.com>2009-01-08 12:04:48 +0000
commitcb6ff208076b5f434db1b8c983429269d719cef5 (patch)
tree96cc88a4f97965e141eb7577beccc4e27ad2ede2 /kernel/fork.c
parentab2e83ead4eca9e045daac4cbf66eb1e7a244bb2 (diff)
downloadkernel_samsung_tuna-cb6ff208076b5f434db1b8c983429269d719cef5.zip
kernel_samsung_tuna-cb6ff208076b5f434db1b8c983429269d719cef5.tar.gz
kernel_samsung_tuna-cb6ff208076b5f434db1b8c983429269d719cef5.tar.bz2
NOMMU: Support XIP on initramfs
Support XIP on files unpacked from the initramfs image on NOMMU systems. This simply requires the length of the file to be preset so that the ramfs fs can attempt to garner sufficient contiguous storage to store the file (NOMMU mmap can only map contiguous RAM). All the other bits to do XIP on initramfs files are present: (1) ramfs's truncate attempts to allocate a contiguous run of pages when a file is truncated upwards from nothing. (2) ramfs sets BDI on its files to indicate direct mapping is possible, and that its files can be mapped for read, write and exec. (3) NOMMU mmap() will use the above bits to determine that it can do XIP. Possibly this needs better controls, because it will _always_ try and do XIP. One disadvantage of this very simplistic approach is that sufficient space will be allocated to store the whole file, and not just the bit that would be XIP'd. To deal with this, though, the initramfs unpacker would have to be able to parse the file contents. Signed-off-by: David Howells <dhowells@redhat.com> Acked-by: Paul Mundt <lethal@linux-sh.org>
Diffstat (limited to 'kernel/fork.c')
0 files changed, 0 insertions, 0 deletions