summaryrefslogtreecommitdiff
path: root/security/smack/Kconfig
diff options
context:
space:
mode:
authorOssama Othman <ossama.othman@intel.com>2010-03-15 23:23:56 (GMT)
committerGreg Kroah-Hartman <gregkh@suse.de>2010-05-11 18:35:33 (GMT)
commitff13209b00dd4f67f676dd8567a9e95f13f4388c (patch)
tree381ae33e482157b3bfe68c50c67bf12c5c78932f /security/smack/Kconfig
parent3504e0c87892c272d9784e12918910d74077da0d (diff)
downloadlinux-fsl-qoriq-ff13209b00dd4f67f676dd8567a9e95f13f4388c.tar.xz
staging: Intel Restricted Access Region Handler
The Intel Restricted Access Region Handler provides a buffer allocation mechanism to RAR users. Since the intended usage model is to lock out CPU access to RAR (the CPU will not be able to access RAR memory), this driver does not access RAR memory, and merely keeps track of what areas of RAR memory are in use. It has it's own simple allocator that does not rely on existing kernel allocators (SLAB, etc) since those allocators are too tightly coupled with the paging mechanism, which isn't needed for the intended RAR use cases. An mmap() implementation is provided for debugging purposes to simplify RAR memory access from the user space. However, it will effectively be a no-op when RAR access control is enabled since the CPU will not be able to access RAR. This driver should not be confused with the rar_register driver. That driver exposes an interface to access RAR registers on the Moorestown platform. The RAR handler driver relies on the rar_register driver for low level RAR register reads and writes. This patch was generated and built against the latest linux-2.6 master branch. Signed-off-by: Ossama Othman <ossama.othman@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'security/smack/Kconfig')
0 files changed, 0 insertions, 0 deletions