kboot: Implement data_from_kernel to read kernel variables

Since the linux kernel doesn't expose enough of the EFI details to
userland via /sys/firmware/efi, write a routine to extract data from the

kboot: Implement data_from_kernel to read kernel variables

Since the linux kernel doesn't expose enough of the EFI details to
userland via /sys/firmware/efi, write a routine to extract data from the
kernel directly by parsing /proc/kproc and /proc/kallsyms.

Sponsored by: Netflix
Reviewed by: kevans, jhibbits
Differential Revision: https://reviews.freebsd.org/D49868

show more ...

kboot: Move common EFI stuff from aarch64 to libkboot

Move efi_read_from_pa, efi_set_systbl and efi_bi_loadsmap into efi.c
Move prototype for populate_avail_from_efi as well, though that arrived
pre

kboot: Move common EFI stuff from aarch64 to libkboot

Move efi_read_from_pa, efi_set_systbl and efi_bi_loadsmap into efi.c
Move prototype for populate_avail_from_efi as well, though that arrived
previously.

Move efi memory map variables into efi.c.

Add efi_read_from_sysfs, but if 0 it out. We'll want to use it if we can
get the proposed /sys/firmware/efi/memmap data published in the same
format and the code works, it's just that the current
/sys/firmware/efi/runtime-memmap isn't complete enough to use.

Sponsored by: Netflix
Reviewed by: kevans, jhibbits
Differential Revision: https://reviews.freebsd.org/D49863

show more ...

kboot: Method to populate the avail array from EFI map

If we can get an efi memory map, populate_avail_from_efi will create an
avail array. We only use the regiions marked as 'free' to find a place

kboot: Method to populate the avail array from EFI map

If we can get an efi memory map, populate_avail_from_efi will create an
avail array. We only use the regiions marked as 'free' to find a place
for the kernel to land. The other regions are also eligible, but usually
too small to materially affect where we'd put the kernel (not to worry,
the kernel will use that memory).

Sponsored by: Netflix
Reviewed by: kevans, jhibbits
Differential Revision: https://reviews.freebsd.org/D49862

show more ...

kboot: Add option to parse 32-bit quantity

The type that's exposed from sysfs' memory map is 32-bit and so is the
data-type of memory description.

Sponsored by: Netflix
Reviewed by: kevans, andre

kboot: Add option to parse 32-bit quantity

The type that's exposed from sysfs' memory map is 32-bit and so is the
data-type of memory description.

Sponsored by: Netflix
Reviewed by: kevans, andrew, jhibbits
Differential Revision: https://reviews.freebsd.org/D49856

show more ...

kboot: Start to move efi common routines to libkboot

Start to move the common efi routines into libkboot by moving the efi
memory map walking and implementing a printing routine around it.

Sponsore

kboot: Start to move efi common routines to libkboot

Start to move the common efi routines into libkboot by moving the efi
memory map walking and implementing a printing routine around it.

Sponsored by: Netflix

show more ...

kboot: Move str* util routines to libkboot

These are needed for the next round of EFI support for amd64 (partially
shared with aarch64, but only partially because the Linux host interfaces
are diffe

kboot: Move str* util routines to libkboot

These are needed for the next round of EFI support for amd64 (partially
shared with aarch64, but only partially because the Linux host interfaces
are different to get the same info).

Sponsored by: Netflix

show more ...

kboot: Move seg code into libkboot

This code is really generic segment processing and should live here. It
also interfaces primarily with Linux APIs, so it's also appropriate for
this if we have a v

kboot: Move seg code into libkboot

This code is really generic segment processing and should live here. It
also interfaces primarily with Linux APIs, so it's also appropriate for
this if we have a version of that runs as a FreeBSD binary using FreeBSD
system calls and APIs, though that's in the future somehow...

Sponsored by: Netflix

show more ...