Re: [PATCH v2] kaslr: get ACPI SRAT table to avoid movable memory

[Dou Liyang]

Hi Baoquan,

At 09/04/2017 04:39 PM, Baoquan He wrote:
> On 09/04/17 at 04:17pm, Dou Liyang wrote:
> > With "movable_node=1024M" option in cmdline, KASLR will can't access
> > the node3 memory.
>
> So you have extended the movable_node option from no value specified to
> adding a limit value, then why don't you go one step further to extend
> it as movable_node=xxx@start. With this, you can eat the cake you have.

Haha, extending it as movable_node=xxx@start is my last choice. I
don't want this option to be as complex as memmap is.

> My personal opinion, could that other peopel have better idea. But dig
> into acpi tables to grab the srat table, that is really not a good idea.

I agree with you. That is why I send method 2.

> Chao has spent time to know the srat table, maybe he can try to make a
> patch with the "movable_node=xxx@start" handling in kaslr.c, let's see
> what it looks like.

OK, go ahead, Chao.

Thanks,
	dou.


> Thanks
> Baoquan
>
> > I am looking for the solution of this. Not find a good way.
> >
> > Sometimes, I will remember that proverb:
> >
> >   You cannot have your cake and eat it too. :-)
> >
> > Thanks,
> > 	dou.
> > > touch ACPI tables with so many lines of code.
> > >
> > > Thanks
> > > Baoquan