Vivek Goyal wrote:
memsz will contain the memory required to load the kernel image. And
probably should also include the memory used by kernel in initial boot
up code which is unaccounted and unbounded.
Right, so that's a major project to produce.
One modification that would be highly desirable is to be able to put
initrd/initramfs in highmem, since people keep adding options which
break the highmem/lowmem boundary without consideration for the
implications; the latest one being vmalloc=.
I suspect we need at least one more piece of data, which is the required
alignment of a relocated kernel.
Now with the introduction of config option CONFIG_PHYSICAL_ALIGN, it
should be easy to get.
Yes, that should be easy.
Either which way, it seems clear that
there is some re-engineering that needs to be done, and I think we need
to better understand *why* the proposed patch failed.
Can this failure be reproduced in a simulator?
I will try to reproduce in a simulator. May be qemu? Any suggestions?
I find Bochs easier to debug under, although it's substantially slower.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]