On 06/04/19 at 03:56pm, Lendacky, Thomas wrote:
> On 6/4/19 8:49 AM, Baoquan He wrote:
> > Hi Tom,
> >
> > Lianbo reported kdump kernel can't boot well with 'nokaslr' added, and
> > have to enable KASLR in kdump kernel to make it boot successfully. This
> > blocked his work on enabling sme for kex
Currently, the get_kaslr_offset_arm64() function has the following
condition to return info->kaslr_offset, but kernel text mapping is
placed in another range on arm64 by default, so it returns 0 for
kernel text addresses.
if (vaddr >= __START_KERNEL_map &&
vaddr < __START_K
On 6/4/19 8:49 AM, Baoquan He wrote:
> Hi Tom,
>
> Lianbo reported kdump kernel can't boot well with 'nokaslr' added, and
> have to enable KASLR in kdump kernel to make it boot successfully. This
> blocked his work on enabling sme for kexec/kdump. And on some machines
> SME kernel can't boot in 1s
Hi Tom,
Lianbo reported kdump kernel can't boot well with 'nokaslr' added, and
have to enable KASLR in kdump kernel to make it boot successfully. This
blocked his work on enabling sme for kexec/kdump. And on some machines
SME kernel can't boot in 1st kernel.
I checked code of SME implementation,
On Fri, May 31, 2019 at 05:38:25PM +0800, Kairui Song wrote:
> On Fri, May 31, 2019 at 5:29 PM Simon Horman wrote:
> >
> > On Fri, Nov 23, 2018 at 05:28:01PM +0800, Kairui Song wrote:
> > > Some device (eg. hyperv_fb) will mimic EFI (or VESA) VGA on first boot
> > > up, but after the real driver i
