"H. Peter Anvin" <[email protected]> writes:
> This is directly analogous to how we treat identity information in IDE, or PCI
> configuration space -- some fields are pre-digested, but the entire raw
> information is also available.
Add to that a totally unchanged value can just be easier to get correct.
Still the kexec code as much as it can should not look there, as we may
get the same basic information in a couple of different ways.
EFI memmap vs. e820 for example. If/when that is the case /sbin/kexec
should get the information and spit it out into whatever format makes
sense for the destination kernel. My sense is just passing through
values is brittleness where we don't want it.
However I think being able to get at the raw boot information overall
sounds useful. I just don't know if it is generally useful or just
useful when debugging bootloaders though.
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
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]
