[Regression Risk]
The EFI changes are in architecture independent code where they add a new table and an API for adding regions to that table. However, this API is only used by the gic-v3-its driver, which is ARM-specific. On other architectures, this will be an empty table. It's possible that there is a bug bug in the table creation code that could cause regressions on other architectures, which would likely be seen in the form of a boot time error message (Failed to install memreserve config table).
[Impact]
kdump support isn't usable on HiSilicon D05 systems. This previously worked in bionic.
[Test Case] LINUX_DEFAULT= "$GRUB_ CMDLINE_ LINUX_DEFAULT crashkernel=512M"' | \ grub.d/ kdump-tools. cfg kernel/ sysrq
sudo apt install linux-crashdump
echo 'GRUB_CMDLINE_
sudo tee /etc/default/
sudo update-grub
sudo reboot
echo 1 | sudo tee /proc/sys/
echo c | sudo tee /proc/sysrq-trigger
[Fix] /msg10328. html /lkml.org/ lkml/2018/ 9/21/1066 /www.spinics. net/lists/ arm-kernel/ msg685751. html
2 upstream patch series are required to fix this:
https://<email address hidden>
Which provides an EFI facility consumed by:
https:/
There were also some follow-on fixes to deal with ARM-specific problems associated with this usage:
https:/
[Regression Risk]
The EFI changes are in architecture independent code where they add a new table and an API for adding regions to that table. However, this API is only used by the gic-v3-its driver, which is ARM-specific. On other architectures, this will be an empty table. It's possible that there is a bug bug in the table creation code that could cause regressions on other architectures, which would likely be seen in the form of a boot time error message (Failed to install memreserve config table).