![]() The specific case I am encountering is kdump under Xen with a 64 bit hypervisor and 32 bit kernel/userspace. The dump created is 64 bit due to the hypervisor but the dump kernel is 32 bit for maximum compatibility. It's possibly less likely to be useful in a purely native scenario but I see no reason to disallow it. [akpm@linux-foundation.org: build fix] Signed-off-by: Ian Campbell <ian.campbell@xensource.com> Signed-off-by: Andi Kleen <ak@suse.de> Acked-by: Vivek Goyal <vgoyal@in.ibm.com> Cc: Horms <horms@verge.net.au> Cc: Magnus Damm <magnus.damm@gmail.com> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Cc: Andi Kleen <ak@suse.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> |
||
---|---|---|
.. | ||
array.c | ||
base.c | ||
generic.c | ||
inode-alloc.txt | ||
inode.c | ||
internal.h | ||
kcore.c | ||
kmsg.c | ||
Makefile | ||
mmu.c | ||
nommu.c | ||
proc_devtree.c | ||
proc_misc.c | ||
proc_sysctl.c | ||
proc_tty.c | ||
root.c | ||
task_mmu.c | ||
task_nommu.c | ||
vmcore.c |