summaryrefslogtreecommitdiffstats
path: root/security/dummy.c
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2005-06-25 14:58:01 -0700
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-06-25 16:24:50 -0700
commit1bc3b91aeed71a904e431d12ca90e9b6bcb42c91 (patch)
tree58e139e6a348dfe06fb62bf9cd5b40cd6a6f8bad /security/dummy.c
parent63d30298efc387c72557d11e2a7b467554c05a64 (diff)
downloadop-kernel-dev-1bc3b91aeed71a904e431d12ca90e9b6bcb42c91.zip
op-kernel-dev-1bc3b91aeed71a904e431d12ca90e9b6bcb42c91.tar.gz
[PATCH] crashdump: x86 crashkernel option
This is the x86 implementation of the crashkernel option. It reserves a window of memory very early in the bootup process, so we never use it for anything but the kernel to switch to when the running kernel panics. In addition to reserving this memory a resource structure is registered so looking at /proc/iomem it is clear what happened to that memory. ISSUES: Is it possible to implement this in a architecture generic way? What should be done with architectures that always use an iommu and thus don't report their RAM memory resources in /proc/iomem? Signed-off-by: Eric Biederman <ebiederm@xmission.com> Signed-off-by: Vivek Goyal <vgoyal@in.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'security/dummy.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud